> ## 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. # Upload a document for an application ## OpenAPI ````yaml openapi/partner-openapi.yaml post /v1/onboarding/partner/applications/{applicationId}/documents openapi: 3.1.0 info: description: > Partner-facing API for programmatic onboarding. Use these endpoints to create and manage onboarding applications on behalf of your customers, submit sections of data, upload supporting documents, and respond to Requests for Information (RFIs). ## Authentication All endpoints require a Bearer token obtained via the Circle key exchange. Include the token in the `Authorization: Bearer ` header. ## Idempotency All POST endpoints in this API require an `X-Idempotency-Key` header. Provide a client-generated UUID v4 with each POST request. If the same key is retried, the original response is returned without re-executing the operation. Omitting the header on a POST will result in a 400 error. This requirement covers the endpoints defined in this specification. Other partner APIs set their own idempotency rules; for example, creating a partner client (`POST /v1/partner/clients`, defined in the Customer Orchestration API) does not require the header. title: Circle Partner Onboarding API version: '2026-04-15' servers: - description: Production url: https://api.circle.com - description: Sandbox url: https://api-sandbox.circle.com security: - bearerAuth: [] paths: /v1/onboarding/partner/applications/{applicationId}/documents: post: tags: - Partner Documents summary: Upload a document for an application operationId: uploadDocument parameters: - description: Application UUID example: 550e8400-e29b-41d4-a716-446655440000 in: path name: applicationId required: true schema: type: string format: uuid - $ref: '#/components/parameters/IdempotencyKey' requestBody: content: multipart/form-data: schema: $ref: '#/components/schemas/DocumentUploadSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/DocumentUploadResponse' description: Uploaded document reference '400': description: Invalid file type, size, or name '401': description: Authentication required '403': description: Insufficient permissions '404': description: Application not found '422': description: >- Validation error: missing or invalid documentType for identity document datums, or resource limit exceeded (documents per application or per entity) components: parameters: IdempotencyKey: description: > Client-generated UUID used to safely retry POST requests. If the same key is submitted twice, the original response is returned without re-executing the operation. Must be a valid UUID v4 (e.g. `550e8400-e29b-41d4-a716-446655440099`). in: header name: X-Idempotency-Key required: true schema: type: string format: uuid schemas: DocumentUploadSchema: type: object description: Multipart form data for document upload properties: datumName: type: string description: Datum (field) name this document satisfies (e.g. passport_document) documentType: type: string description: >- Type of identity document being uploaded. Required when the schema field carries an x-documentTypes extension — check the field definition in GET /{applicationId}/schema to see which values are accepted for a given datum. Standard government ID datums accept passport, usdl, or usid; notarized government ID datums accept idNotarization. Ignored for all other datums — the service derives the type automatically from the datum name. enum: - addressDoc - amlPolicyDoc - bankStatement - businessLicense - fincenDoc - fundDoc - fundFormDExemDoc - genericDoc - idNotarization - orgDoc - orgLicense - passport - securityControlsCertification - usdl - usid fileContent: type: string format: binary description: Binary file content fileName: type: string description: Original file name including extension (e.g. passport.pdf) issuedCountry: type: string description: >- ISO 3166-1 alpha-2 country code where the document was issued (required for identity documents) refId: type: string format: uuid description: >- Reference ID of the array entity this document belongs to (required for array sections) required: - datumName - fileContent - fileName DocumentUploadResponse: type: object properties: documentId: type: string format: uuid securitySchemes: bearerAuth: bearerFormat: JWT description: Bearer token obtained via Circle key exchange scheme: bearer type: http ````