> ## 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 payment status > Returns the current status of a payment. Use this endpoint to reconcile a payment that settlement left unresolved with `errorReason: settlement_pending`. Status values are `pending`, `completed`, or `failed`. ## OpenAPI ````yaml openapi/facilitator-service.yaml get /v1/facilitator/x402/status/{paymentId} openapi: 3.0.3 info: title: Facilitator Service version: 1.0.0 description: > Facilitator Service is Circle's hosted x402 facilitator. Sellers call Facilitator Service to verify and settle x402 payments in USDC on Arc, Base, and Polygon PoS without operating their own relayer, gas wallet, or sanctions screening. Facilitator Service implements the x402 v2 `exact` scheme and settles USDC through EIP-3009 authorizations. servers: - url: https://api.circle.com description: Production - url: https://api-sandbox.circle.com description: Sandbox security: - CircleApiKey: [] - FacilitatorSellerProof: [] tags: - name: Payments description: | x402 payment verification, settlement, and status. - name: Supported payment kinds description: | x402 payment kinds and extensions Facilitator Service accepts. paths: /v1/facilitator/x402/status/{paymentId}: get: tags: - Payments summary: Get payment status description: | Returns the current status of a payment. Use this endpoint to reconcile a payment that settlement left unresolved with `errorReason: settlement_pending`. Status values are `pending`, `completed`, or `failed`. operationId: GetPaymentStatus parameters: - name: paymentId in: path required: true description: The `paymentId` returned by `/settle` on a pending response. schema: type: string format: uuid responses: '200': description: Payment status content: application/json: schema: $ref: '#/components/schemas/StatusResponse' '401': description: | Missing or invalid authentication. Returned when neither a valid Circle API key nor a valid seller proof is present, or when the seller proof's nonce has been replayed with a different digest. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: | Payment not found or not visible to the caller. Unknown IDs and out-of-scope IDs return the same response to avoid enumeration. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Unexpected internal error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - CircleApiKey: [] - FacilitatorSellerProof: [] components: schemas: StatusResponse: type: object required: - paymentId - status - network properties: paymentId: type: string format: uuid description: Facilitator Service payment identifier. example: 5b3f6c1e-9d2a-4f08-b1c7-2e9a14d0c3aa status: type: string enum: - pending - completed - failed description: Current lifecycle state of the payment. reason: type: string nullable: true enum: - outcome_unknown description: Additional detail about the payment status. example: outcome_unknown transaction: type: string nullable: true description: Transaction hash once available. example: 0x6f9e1d... network: type: string description: CAIP-2 network identifier for the payment. example: eip155:5042002 amount: type: string description: Amount in atomic USDC units. example: '1000000' payer: type: string nullable: true description: Buyer address on the settled transfer. example: null nextAction: type: string nullable: true description: > Reserved poll-hint field. Always null: `/status` does not advertise a next action. Callers choose their own reconcile cadence. example: null retryAfterMs: type: integer nullable: true description: > Reserved poll-hint field. Always null: `/status` does not advertise a retry cadence. Callers choose their own reconcile interval. The support deadline is `expiresAt`. example: null expiresAt: type: string format: date-time nullable: true description: | Support deadline for this unresolved payment. Reconciliation continues past it. Present only while `status` is `pending`. updatedAt: type: string format: date-time description: Timestamp of the most recent state transition. example: '2026-06-11T22:30:11Z' ErrorResponse: type: object required: - code - message properties: code: type: integer description: HTTP status code echoed in the body for programmatic handling. example: 403 message: type: string description: >- Human-readable summary of the error, suitable for display to end users. example: Registration required to continue settling on this address errors: type: array description: Per-issue reason codes. items: type: object required: - reason properties: reason: type: string description: | Machine-readable reason code. enum: - registration_required - authorization_expired - payment_identifier_conflict - credential_bound_elsewhere - credential_payer_conflict example: registration_required securitySchemes: CircleApiKey: type: http scheme: bearer description: | Bearer token authentication with a Circle API key. Use this for production settlement. Settling with an API key also binds the `payTo` to your Circle account, which ends the keyless trial allowance. FacilitatorSellerProof: type: apiKey in: header name: Facilitator-Seller-Proof description: | Base64url-encoded envelope carrying an EIP-712 signature that proves the caller controls the `payTo` address. Use this for the keyless trial, before you settle with a Circle API key. ````