> ## 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. # Create a tokenization advance > Requests an RWA Redemption Advance backed by a token burn on Arc and the brokerage sell orders for the underlying shares. The advance is validated when you submit it. There is no reserve step and no manual review, so a valid request returns `requested` and disburses asynchronously. List the burn's eligible orders first, then send the IDs of the orders to use. The orders' available shares must cover the burned token quantity, at one share per token. Circle counts shares from the highest-valued order first, and orders with the same value from the oldest first, until it reaches the burned token quantity. The order that reaches it counts only the shares still needed. An order that contributes no shares is not used and stays available for another advance. `amount` must not exceed the value of the counted shares, after the advance rate for the token. Each order's `advanceLimit` from the list eligible orders endpoint shows this value for that order alone. Every order with counted shares is used in full, even when only some of its shares were counted. A burn backs at most one advance. Reusing a burn returns HTTP 409. **Note:** This endpoint is only available for RWA Redemption Advance products with a provider connection. ## OpenAPI ````yaml openapi/credit.yaml post /v1/credit/tokenization/advances 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/advances: post: tags: - Credit Tokenization summary: Create a tokenization advance description: > Requests an RWA Redemption Advance backed by a token burn on Arc and the brokerage sell orders for the underlying shares. The advance is validated when you submit it. There is no reserve step and no manual review, so a valid request returns `requested` and disburses asynchronously. List the burn's eligible orders first, then send the IDs of the orders to use. The orders' available shares must cover the burned token quantity, at one share per token. Circle counts shares from the highest-valued order first, and orders with the same value from the oldest first, until it reaches the burned token quantity. The order that reaches it counts only the shares still needed. An order that contributes no shares is not used and stays available for another advance. `amount` must not exceed the value of the counted shares, after the advance rate for the token. Each order's `advanceLimit` from the list eligible orders endpoint shows this value for that order alone. Every order with counted shares is used in full, even when only some of its shares were counted. A burn backs at most one advance. Reusing a burn returns HTTP 409. **Note:** This endpoint is only available for RWA Redemption Advance products with a provider connection. operationId: createTokenizationAdvance requestBody: content: application/json: schema: $ref: '#/components/schemas/TokenizationAdvanceCreationRequest' examples: Without Destination: value: idempotencyKey: ba943ff1-ca16-49b2-ba55-1057e70ca5c7 provider: ALPACA providerAccountId: a7c1e3f0-5d2b-4c8e-9f61-2b7d4e8a1c90 transactionHash: >- 0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f orders: - orderId: e2f8a4c6-1b3d-4e5f-8a9b-0c1d2e3f4a5b - orderId: b9d7c5e3-a1f2-4d6b-8c0e-3f5a7b9d1e2c amount: amount: '15000.00' currency: USD With Blockchain Destination: value: idempotencyKey: ba943ff1-ca16-49b2-ba55-1057e70ca5c7 provider: ALPACA providerAccountId: a7c1e3f0-5d2b-4c8e-9f61-2b7d4e8a1c90 transactionHash: >- 0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f orders: - orderId: e2f8a4c6-1b3d-4e5f-8a9b-0c1d2e3f4a5b - orderId: b9d7c5e3-a1f2-4d6b-8c0e-3f5a7b9d1e2c amount: amount: '15000.00' currency: USD destination: type: verified_blockchain addressId: a1b2c3d4-e5f6-7890-abcd-ef1234567890 responses: '201': description: Successfully created a tokenization advance. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: CreateTokenizationAdvanceResponse properties: data: $ref: '#/components/schemas/TokenizationAdvance' examples: Requested: value: data: id: c4a2e6f8-3b1d-4f7a-9e2c-5d8b0a1f3e6c amount: amount: '15000.00' currency: USD status: requested accountId: '1000000' createDate: '2024-03-20T14:10:02.000Z' updateDate: '2024-03-20T14:10:02.000Z' provider: ALPACA providerAccountId: a7c1e3f0-5d2b-4c8e-9f61-2b7d4e8a1c90 transactionHash: >- 0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f symbol: AAPL burnedShareQuantity: '100' orders: - orderId: e2f8a4c6-1b3d-4e5f-8a9b-0c1d2e3f4a5b submittedAt: '2024-03-20T14:05:12.000Z' allocatedShares: '60' weightedAveragePrice: '172.45' - orderId: b9d7c5e3-a1f2-4d6b-8c0e-3f5a7b9d1e2c submittedAt: '2024-03-20T14:06:40.000Z' allocatedShares: '40' weightedAveragePrice: '172.30' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' security: - bearerAuth: [] components: schemas: TokenizationAdvanceCreationRequest: type: object description: Request body for creating a tokenization advance. required: - idempotencyKey - provider - providerAccountId - transactionHash - orders - amount properties: idempotencyKey: $ref: '#/components/schemas/IdempotencyKey' provider: description: The tokenization provider. type: string enum: - ALPACA example: ALPACA providerAccountId: description: The provider account that placed the sell orders. type: string example: a7c1e3f0-5d2b-4c8e-9f61-2b7d4e8a1c90 transactionHash: description: >- The transaction hash of the token burn on Arc (0x-prefixed 32-byte hex string). type: string pattern: ^0x[0-9a-fA-F]{64}$ example: '0x5ba3602c1ffcbac77db82bf1360fe44f2042042c782e9114ea29ecb1708c239f' orders: description: >- The sell orders to back the advance. Each order ID may appear once. Circle decides how many shares of each order to count. type: array minItems: 1 items: type: object required: - orderId properties: orderId: description: The provider's identifier for the order. type: string example: e2f8a4c6-1b3d-4e5f-8a9b-0c1d2e3f4a5b amount: $ref: '#/components/schemas/FiatMoneyUsd' description: The amount to advance. Currency must match the credit line currency. destination: $ref: '#/components/schemas/CreditTransferDestination' description: >- Optional blockchain destination for the advance. When provided, disbursed funds are sent to the specified verified blockchain address instead of the default fiat account. accountId: description: >- Optional identifier of the funding account for the advance. When omitted, falls back to the entity's default funding account. type: string example: '1000000' TokenizationAdvance: type: object description: >- An RWA Redemption Advance backed by a token burn and brokerage sell orders. required: - id - amount - status - accountId - createDate - updateDate - provider - providerAccountId - transactionHash - symbol - burnedShareQuantity - orders properties: id: description: Unique identifier of the advance. type: string format: uuid example: c4a2e6f8-3b1d-4f7a-9e2c-5d8b0a1f3e6c amount: $ref: '#/components/schemas/FiatMoneyUsd' description: The advance amount. status: description: >- Current status of the advance. Tokenization advances have no reserve step, so they never have the `funds_reserved`, `expired`, or `canceled` status. type: string enum: - requested - rejected - disbursed - paid - past_due example: disbursed outstanding: $ref: '#/components/schemas/FiatMoneyUsd' description: >- Remaining outstanding balance on the advance. Present only on the get endpoint, when status is disbursed, paid, or past_due. fees: $ref: '#/components/schemas/CreditTransferFees' description: >- Fee summary for the advance. Present only on the get endpoint, when status is disbursed, paid, or past_due. dueDate: $ref: '#/components/schemas/UtcTimestamp' description: >- ISO-8601 UTC date/time when the advance repayment is due. Present only when status is disbursed, paid, or past_due. disbursedDate: $ref: '#/components/schemas/UtcTimestamp' description: >- ISO-8601 UTC date/time when the advance was disbursed. Present only when status is disbursed, paid, or past_due. paidDate: $ref: '#/components/schemas/UtcTimestamp' description: >- ISO-8601 UTC date/time when the advance was fully repaid. Present only when status is paid. accountId: description: Unique identifier of the account the funds moved through. type: string example: '1000000' blockchainDestination: $ref: '#/components/schemas/BlockchainDestinationResponse' description: >- Blockchain destination details. Present when the advance was requested with a blockchain destination. createDate: $ref: '#/components/schemas/UtcTimestamp' description: ISO-8601 UTC date/time when the advance was created. updateDate: $ref: '#/components/schemas/UtcTimestamp' description: ISO-8601 UTC date/time when the advance was last updated. provider: description: The tokenization provider. type: string enum: - ALPACA example: ALPACA providerAccountId: description: The provider account that placed the sell orders. type: string example: a7c1e3f0-5d2b-4c8e-9f61-2b7d4e8a1c90 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 orders that back the advance, one per order with counted shares. Their `allocatedShares` add up to `burnedShareQuantity`. type: array items: $ref: '#/components/schemas/TokenizationAdvanceOrder' IdempotencyKey: type: string description: >- Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests. format: uuid example: ba943ff1-ca16-49b2-ba55-1057e70ca5c7 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 CreditTransferDestination: type: object description: >- Optional blockchain destination for the credit transfer. When provided, the disbursed funds will be sent to the specified verified blockchain address. required: - type - addressId properties: type: description: The destination type. type: string enum: - verified_blockchain example: verified_blockchain addressId: description: The identifier of the verified blockchain address to send funds to. type: string format: uuid example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 CreditTransferFees: type: object description: Fee summary for a credit transfer. required: - total - unpaid properties: total: $ref: '#/components/schemas/FiatMoneyUsd' description: Total fees accrued on the transfer. unpaid: $ref: '#/components/schemas/FiatMoneyUsd' description: Fees that have not yet been paid. UtcTimestamp: type: string description: ISO-8601 UTC date/time format. example: '2020-04-10T02:13:30.000Z' BlockchainDestinationResponse: type: object description: >- Blockchain destination details for a credit transfer. Present when the transfer was requested with a blockchain destination. required: - addressId - status properties: addressId: description: The identifier of the verified blockchain address. type: string format: uuid example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 status: description: The status of the blockchain transfer. type: string enum: - pending - initiated - complete - failed example: pending transferId: description: >- The identifier of the blockchain transfer. Present once the transfer has been initiated. type: string format: uuid example: fc988ed5-c129-4f70-a064-e5beb7eb8e32 TokenizationAdvanceOrder: type: object description: A sell order that backs a tokenization advance. required: - orderId - allocatedShares - weightedAveragePrice 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. allocatedShares: description: >- The shares of this order counted toward the burn, as a decimal string. The order that reaches the burned token quantity can count fewer shares than it holds. type: string example: '60' weightedAveragePrice: description: >- The value per share used for the advance, as a decimal string, fixed when the advance was created. type: string example: '172.45' 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 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 ````