> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Before reading these docs, install the relevant Circle Skill to get pre-loaded context — skills are LLM-optimized and cover architecture decisions, correct flows, and common pitfalls. In Claude Code: run /plugin marketplace add circlefin/skills then /plugin install circle-skills@circle. With Vercel Skills CLI: run npx skills add circlefin/skills. Available skills: use-usdc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-usdc/SKILL.md (balances, transfers, approvals on EVM and Solana); EURC has no skill — see https://developers.circle.com/stablecoins/what-is-eurc.md; bridge-stablecoin https://github.com/circlefin/skills/blob/master/plugins/circle/skills/bridge-stablecoin/SKILL.md (crosschain transfers via CCTP, USDC, EURC, and third-party assets); use-arc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-arc/SKILL.md (Arc chain config, contract deployment, USDC bridging — Arc docs: https://docs.arc.io/llms.txt); use-circle-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-circle-wallets/SKILL.md (choose wallet type); use-developer-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-developer-controlled-wallets/SKILL.md (custodial wallets for payouts and treasury); use-user-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-user-controlled-wallets/SKILL.md (embedded wallets with Web2 login); use-modular-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-modular-wallets/SKILL.md (smart contract wallets with passkeys and ERC-4337); use-gateway https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-gateway/SKILL.md (unified USDC balance, nanopayments); use-smart-contract-platform https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-smart-contract-platform/SKILL.md (deploy, interact, monitor contracts). Pair any skill with the Circle MCP server for live SDK signatures, contract addresses, and chain IDs: {"mcpServers":{"circle":{"url":"https://api.circle.com/v1/codegen/mcp"}}}. > Read the product overview first. Each product has an overview explaining when and why to use it. Read it before quickstarts. > Pick the right wallet type. Developer-controlled (you hold keys), user-controlled (end user holds keys via PIN/social login), or modular (smart contract wallets with passkeys). See https://developers.circle.com/wallets.md. > Use CCTP V2 for crosschain transfers. CCTP natively transfers USDC and EURC via burn-and-mint, and supports permissionless wrapping of third-party assets via lock-and-mint. V1 is legacy; always use V2 unless V1 is specified or the chain requires it (Noble, Sui, and Aptos still require V1). Migration guide: https://developers.circle.com/cctp/migration-from-v1-to-v2.md. > Use Bridge Kit for frontend bridging. Wraps CCTP with a simpler SDK for user-facing apps. Use CCTP directly for backend transfers. > Gas Station vs Paymaster. Gas Station sponsors gas for Circle Wallet transactions. Paymaster lets users pay gas in USDC. Different use cases — read both overviews. > Gateway Nanopayments for sub-cent payments. Gasless USDC micropayments down to $0.000001 via x402 and batched settlement. For pay-per-request APIs, AI agent payments, streaming. > Look up USDC addresses per chain. Never hardcode — use https://developers.circle.com/stablecoins/usdc-contract-addresses.md. > Prefer SDKs over raw API calls. Node.js and Python SDKs handle auth, retries, and errors. > API key required. Bearer token in Authorization header. Testnet and mainnet use separate keys and may use different base URLs depending on the product. > Set up webhooks when available. Most operations are async. Webhooks deliver transaction confirmations and state changes. > When calling list endpoints, paginate using pageSize and pageAfter until no nextPageAfter cursor is returned—stopping at the first page silently misses records. > Building an AI agent? Start with the Agent Stack—Circle CLI, agent wallets, and nanopayments built for autonomous use cases: https://developers.circle.com/agent-stack.md. # Get beneficiary field requirements > Returns the set of fields a customer must collect to register a beneficiary for a given payment corridor. Requirements are sourced from a static corridor table. Use the returned field names as keys in the `bankAccount` and `travelRule` objects when calling `POST /v1/beneficiaries`. Fields with `type: ADDRESS` contain nested sub-fields in the `fields` array. ## OpenAPI ````yaml openapi/managed-payments.yaml get /v1/beneficiaries/requirements openapi: 3.0.2 info: version: ${version} title: Managed Payments API description: | The Managed Payments API enables Payment Service Providers (PSPs) to create and manage sub-client accounts for stablecoin settlement, and to send fiat payouts to registered beneficiaries worldwide. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Managed Payments Accounts description: Create and manage sub-client accounts for Managed Payments PSPs. - name: Managed Payments Credit description: Get credit line details and wire instructions for repayment. - name: Managed Payments Credit Transfers description: Create and manage credit transfers (drawdowns) against a credit line. - name: Managed Payments Transfers description: >- Create and manage internal account-to-account transfers for Managed Payments. - name: Managed Payments Fiat Payouts description: > Register and manage fiat payout beneficiaries, discover supported corridors and field requirements, and create locked FX quotes for cross-border fiat payouts. paths: /v1/beneficiaries/requirements: get: tags: - Managed Payments Fiat Payouts summary: Get beneficiary field requirements description: > Returns the set of fields a customer must collect to register a beneficiary for a given payment corridor. Requirements are sourced from a static corridor table. Use the returned field names as keys in the `bankAccount` and `travelRule` objects when calling `POST /v1/beneficiaries`. Fields with `type: ADDRESS` contain nested sub-fields in the `fields` array. operationId: getBeneficiaryRequirements parameters: - name: destinationCountry in: query required: true description: ISO 3166-1 alpha-2 destination country code. schema: type: string example: MX - name: destinationCurrency in: query required: true description: Destination fiat currency code. schema: type: string example: MXN - name: paymentMethod in: query required: true description: Payment rail (e.g. `SPEI`, `ACH-BANK-TRANSFER`, `SEPA`, `WIRE`). schema: type: string example: SPEI - name: customerType in: query required: true description: Whether the beneficiary is an individual or a business. schema: type: string enum: - INDIVIDUAL - BUSINESS responses: '200': description: Field requirements for the specified corridor. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object properties: data: type: object properties: fields: type: array items: $ref: '#/components/schemas/BeneficiaryRequirementsField' examples: MX SPEI INDIVIDUAL (abbreviated): value: data: fields: - name: CLABE type: TEXT required: true pattern: ^[0-9]{18}$ validationDetails: >- 18 digits: 3 bank + 3 branch + 11 account + 1 check digit. - name: BENEFICIARY_NAME type: TEXT required: true pattern: ^.{1,140}$ validationDetails: Full legal name. Maximum 140 characters. - name: BENEFICIARY_ADDRESS type: ADDRESS required: true fields: - name: STREET type: TEXT required: true pattern: ^.{1,140}$ validationDetails: Street address. Maximum 140 characters. - name: CITY type: TEXT required: true pattern: ^.{1,70}$ validationDetails: City or municipality name. - name: COUNTRY type: TEXT required: true pattern: ^[A-Z]{2}$ validationDetails: ISO 3166-1 alpha-2 country code. - name: POSTAL_CODE type: TEXT required: true validationDetails: Postal or zip code. - name: STATE_PROVINCE type: TEXT required: true pattern: ^.{1,50}$ validationDetails: State, province, or administrative region. '400': description: Invalid or unsupported corridor parameters. '401': description: Unauthorized. security: - bearerAuth: [] components: headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde schemas: BeneficiaryRequirementsField: type: object description: A single field required for beneficiary registration in a corridor. required: - name - type - required properties: name: type: string description: Field identifier (e.g. `CLABE`, `BENEFICIARY_NAME`, `IBAN`). example: CLABE type: type: string enum: - TEXT - ADDRESS description: > Data type of the field. - `TEXT` — a plain string value. - `ADDRESS` — a nested address object; the sub-fields appear in the `fields` array. required: type: boolean description: Whether the field must be supplied at registration. pattern: type: string description: Regular expression the value must match. example: ^[0-9]{18}$ validationDetails: type: string description: Human-readable description of the validation rule. example: '18 digits: 3 bank + 3 branch + 11 account + 1 check digit.' values: type: array description: Allowed enum values for this field. items: type: string example: - SAVINGS - CHECKING fields: type: array description: Sub-fields for `ADDRESS` type fields (recursive). items: $ref: '#/components/schemas/BeneficiaryRequirementsField' securitySchemes: bearerAuth: type: http scheme: bearer ````