> ## 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. # List eligible orders for a burn > Returns the sell orders on the provider account that can back an advance for the given token burn, with the shares each order has available and the most you can borrow against it. The result is advisory and changes as orders fill and prices move. It does not reserve the orders. The response carries `Cache-Control: no-store`. An order is eligible when it: - Sells the stock that the burned token represents, on the given account. - Was submitted in the 2 hours before or after the burn. - Is a market or limit order sized in shares. Stop orders and open orders sized in dollars (notional) are not eligible. - Is not a short sale. - Is not already backing another advance. Each order is valued per share by its `fillStatus`. A `filled` order uses its fill price. An `open` order uses the current bid, never its limit price. A `partially_filled` order blends the fill price for the filled shares with the bid for the rest. The burn must be of a supported token, must have reached finality, and must be no more than 24 hours old. A burn that already backs an advance returns HTTP 409. **Note:** This endpoint is only available for RWA Redemption Advance products with a provider connection. ## OpenAPI ````yaml openapi/credit.yaml get /v1/credit/tokenization/providers/{provider}/orders openapi: 3.0.2 info: version: ${version} title: Credit API description: > The Circle Credit API provides access to credit facilities including Line of Credit, Settlement Advance, and RWA Redemption Advance products. **Line of Credit** enables direct drawdowns with auto-approval and asynchronous disbursement. Supports both fiat and crypto repayment. **Settlement Advance** requires a reserve-then-request flow with manual approval. Requires wire proof upload for disbursement approval. Supports fiat repayment only. **RWA Redemption Advance** advances the proceeds of a tokenized stock redemption. Requires an onchain Arc burn transaction hash. Supports both fiat and crypto repayment. Draws use one of two flows, depending on the credit line: - **Receipt flow:** a reserve-then-request flow with automated AI verification of an uploaded receipt. - **Tokenization flow:** for lines connected to a brokerage provider. A single request names the token burn and the brokerage sell orders for the underlying shares, and is validated inline with no reserve step. Use the list tokenization providers endpoint to tell which flow a line uses. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Credit description: Get credit line details. - name: Credit Transfers description: Create, reserve, and manage credit transfers (drawdowns). - name: Credit Fees description: View fees charged on credit transfers. - name: Credit Repayments description: View and initiate repayments on credit transfers. - name: Credit Tokenization description: >- Create and view RWA Redemption Advances backed by a token burn and brokerage sell orders. paths: /v1/credit/tokenization/providers/{provider}/orders: get: tags: - Credit Tokenization summary: List eligible orders for a burn description: > Returns the sell orders on the provider account that can back an advance for the given token burn, with the shares each order has available and the most you can borrow against it. The result is advisory and changes as orders fill and prices move. It does not reserve the orders. The response carries `Cache-Control: no-store`. An order is eligible when it: - Sells the stock that the burned token represents, on the given account. - Was submitted in the 2 hours before or after the burn. - Is a market or limit order sized in shares. Stop orders and open orders sized in dollars (notional) are not eligible. - Is not a short sale. - Is not already backing another advance. Each order is valued per share by its `fillStatus`. A `filled` order uses its fill price. An `open` order uses the current bid, never its limit price. A `partially_filled` order blends the fill price for the filled shares with the bid for the rest. The burn must be of a supported token, must have reached finality, and must be no more than 24 hours old. A burn that already backs an advance returns HTTP 409. **Note:** This endpoint is only available for RWA Redemption Advance products with a provider connection. operationId: listTokenizationOrders parameters: - $ref: '#/components/parameters/TokenizationProviderPath' - name: providerAccountId description: >- The provider account that placed the sell orders. Must be an active account from the list provider accounts endpoint. in: query required: true schema: type: string example: a7c1e3f0-5d2b-4c8e-9f61-2b7d4e8a1c90 - name: transactionHash description: >- The transaction hash of the token burn on Arc (0x-prefixed 32-byte hex string). in: query required: true schema: type: string pattern: ^0x[0-9a-fA-F]{64}$ example: '0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f' responses: '200': description: Successfully retrieved the eligible orders. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' Cache-Control: description: >- Always `no-store`. The result reflects live order and market data. schema: type: string enum: - no-store content: application/json: schema: title: ListTokenizationOrdersResponse properties: data: $ref: '#/components/schemas/TokenizationOrders' examples: Eligible Orders: value: data: transactionHash: >- 0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f symbol: AAPL burnedShareQuantity: '100' orders: - orderId: e2f8a4c6-1b3d-4e5f-8a9b-0c1d2e3f4a5b submittedAt: '2024-03-20T14:05:12.000Z' fillStatus: filled availableShares: '60' weightedAveragePrice: '172.45' advanceLimit: amount: '10347.00' currency: USD - orderId: b9d7c5e3-a1f2-4d6b-8c0e-3f5a7b9d1e2c submittedAt: '2024-03-20T14:06:40.000Z' fillStatus: open availableShares: '50' weightedAveragePrice: '172.30' advanceLimit: amount: '8615.00' currency: USD '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' security: - bearerAuth: [] components: parameters: TokenizationProviderPath: name: provider description: The tokenization provider, in lower case. in: path required: true schema: type: string enum: - alpaca example: alpaca 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: TokenizationOrders: type: object description: A token burn and the sell orders that can back an advance for it. required: - transactionHash - symbol - burnedShareQuantity - orders properties: transactionHash: description: The transaction hash of the token burn on Arc. type: string pattern: ^0x[0-9a-fA-F]{64}$ example: '0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f' symbol: description: The stock symbol that the burned token represents. type: string example: AAPL burnedShareQuantity: description: >- The number of tokens burned, as a decimal string. Each token represents one share of the stock. type: string example: '100' orders: description: The eligible sell orders. Empty when no order is eligible. type: array items: $ref: '#/components/schemas/TokenizationOrder' TokenizationOrder: type: object description: A sell order that can back an advance. required: - orderId - submittedAt - fillStatus - availableShares - weightedAveragePrice - advanceLimit properties: orderId: description: The provider's identifier for the order. type: string example: e2f8a4c6-1b3d-4e5f-8a9b-0c1d2e3f4a5b submittedAt: $ref: '#/components/schemas/UtcTimestamp' description: ISO-8601 UTC date/time when the order was submitted to the provider. fillStatus: description: > How much of the order has executed. `filled`: all shares executed. `partially_filled`: some shares executed and the rest are still working. `open`: no shares have executed yet. type: string enum: - filled - partially_filled - open example: filled availableShares: description: >- The shares of the order that can back an advance, as a decimal string. type: string example: '60' weightedAveragePrice: description: >- The value per share used for the advance, as a decimal string. The fill price for filled shares and the current bid for shares not yet filled. type: string example: '172.45' advanceLimit: $ref: '#/components/schemas/FiatMoneyUsd' description: >- The most you can borrow against this order alone, rounded down to the cent. UtcTimestamp: type: string description: ISO-8601 UTC date/time format. example: '2020-04-10T02:13:30.000Z' FiatMoneyUsd: type: object required: - amount - currency properties: amount: description: Magnitude of the amount, in units of the currency, with a `.`. type: string example: '3.14' currency: description: Currency code. type: string enum: - USD responses: BadRequest: description: The request cannot be processed due to a client error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: BadRequest required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 400 message: Bad request. examples: response: value: code: 400 message: Bad request. NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 401 message: Malformed authorization. examples: response: value: code: 401 message: Malformed authorization. NotFound: description: The specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotFound required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 404 message: Not found. examples: response: value: code: 404 message: Not found. Conflict: description: >- The request has not been applied because it comes in conflict with another request (such as re-using an idempotencyKey for a different request). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: Conflict required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 409 message: Conflicts with another request. examples: response: value: code: 409 message: Conflicts with another request. securitySchemes: bearerAuth: type: http scheme: bearer ````