> ## Documentation Index > Fetch the complete documentation index at: https://yieldxyz.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Preferred validators > Fetch yield.xyz's curated, pre-vetted validators for a staking yield and filter to them with the preferred flag. The Preferred Validator Network (PVN) is a registry of validators that yield.xyz curates and maintains centrally, across the networks where a staking yield supports choosing a validator. Preferred status is a property of the validator itself, set by yield.xyz; it is not something an integrator configures per project. ## 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 Call `GET /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 as `validatorAddress` (or in `validatorAddresses`). * `preferred`: `true` for validators yield.xyz flags as preferred. * `commission`: the validator's commission, as a decimal. * `status`: `active`, `jailed`, `deactivating`, `inactive`, `full`, or `not_found`. For the full validator object, see the [validators endpoint reference](/api-reference/YieldsController_getYieldValidators). ## How it fits the staking flow When a staking yield requires validator selection, fetch its validators before calling enter. Filtering to `preferred=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 Route delegations through validators you already operate instead. Deploy branded validator nodes managed by yield.xyz. Pass a validator address when entering a staking yield. Fetch validators and choose one before you enter, step by step. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.