When it applies
Preferred validators exist only for staking yields where you select a validator on enter (mechanics.requiresValidatorSelection: true on the yield object). For those yields, GET /v1/yields/{yieldId}/validators returns every validator yield.xyz indexes for that yield, each with a preferred boolean. Filter to preferred=true to return only PVN members.
PVN validators are selected on historical uptime, performance, total value staked, and slashing history, and operate under SLAs covering uptime and slashing protection.
Fetching preferred validators
CallGET /v1/yields/{yieldId}/validators?preferred=true for the yield you want to stake, for example solana-sol-native-multivalidator-staking. The endpoint also accepts name, address, provider, and status filters, plus offset and limit for pagination. There is no endpoint for browsing preferred validators across yields; query each yield’s validators individually.
The fields you need to choose a validator:
address: the value you pass asvalidatorAddress(or invalidatorAddresses).preferred:truefor validators yield.xyz flags as preferred.commission: the validator’s commission, as a decimal.status:active,jailed,deactivating,inactive,full, ornot_found.
How it fits the staking flow
When a staking yield requires validator selection, fetch its validators before calling enter. Filtering topreferred=true narrows that list to PVN members so you can default users to a vetted set instead of surfacing every indexed validator. The selected validator’s address is then passed as validatorAddress (or one address per entry in validatorAddresses for yields that support splitting a delegation) in the enter request.
Next steps
Bring your own node
Route delegations through validators you already operate instead.
Whitelabel validators
Deploy branded validator nodes managed by yield.xyz.
Actions
Pass a validator address when entering a staking yield.
Validator selection guide
Fetch validators and choose one before you enter, step by step.

