> ## 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.
# Initiate a withdrawal from xReserve as a remote blockchain
If you're a remote blockchain partner, you can submit to withdraw from xReserve
after a user burns tokens on your blockchain. This tutorial walks through the
process using Canton TestNet as the example remote blockchain and Ethereum
Sepolia as both the example source and destination blockchain. xReserve is also
deployed on Arc, which you can use as an alternative source or destination
blockchain. See
[Supported Blockchains and Domains](/xreserve/references/supported-blockchains-and-domains)
for domain IDs.
This tutorial is intended for remote blockchain partners. If you're a
developer or user, visit the remote blockchain website or contact them for
instructions on how to withdraw funds from xReserve.
## Step 1. Monitor burn events
Listen for burn events on your blockchain. Each event should include at least:
* The recipient wallet address on the destination chain.
* The
[remote domain](/xreserve/references/supported-blockchains-and-domains#remote-domains)
ID.
## Step 2. Prepare the withdrawal
Send the burn intent data to the
[`/prepare-withdrawal`](/api-reference/xreserve/all/prepare-withdrawal)
endpoint. The following example request contains data to withdraw 2500 USDC on
Ethereum:
```json json theme={null}
{
"batches": [
{
"token": "USDC",
"valueExcludingFees": "2500.00",
"remoteDomain": 10001,
"remoteDepositor": "0x000000000000000000000000c0ffee254729296a45a3885639ac7e10f9d54979",
"finalDestinationDomain": 0,
"finalDestinationRecipient": "0x000000000000000000000000aabbee11223344556677889900aabbccddeeff00",
"finalDestinationCaller": "0x00000000000000000000000000112233445566778899aabbccddeeff00112233",
"useCircleForwarding": true,
"salt": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
}
]
}
```
**Response**
The API returns a fully encoded
[burn intent](/xreserve/concepts/technical-guide#burn-intent) and the canonical
[message hash](/xreserve/concepts/technical-guide#message-hash-and-burn-intent-signature)
for you to sign, for example:
```json json theme={null}
{
"batches": [
{
"burnIntents": [
{
"maxBlockHeight": "18976543",
"maxFee": "750000",
"spec": {
"version": 1,
"sourceDomain": 0,
"destinationDomain": 0,
"sourceContract": "0x0000000000000000000000000077777d7eba4688bdef3e311b846f25870a19b9",
"destinationContract": "0x0000000000000000000000000022222abe238cc2c7bb1f21003f0a260052475b",
"sourceToken": "0x74ed63088c070c8fd5d8ad71f2a1cef868c63d00e0ac6dc2a6722d171691a422",
"destinationToken": "0x0000000000000000000000001c7d4b196cb0c7b01d743fbc6116a902379c7238",
"sourceDepositor": "0x000000000000000000000000c0ffee254729296a45a3885639ac7e10f9d54979",
"destinationRecipient": "0x000000000000000000000000aabbee11223344556677889900aabbccddeeff00",
"sourceSigner": "0x0000000000000000000000005555555555555555555555555555555555555555",
"destinationCaller": "0x00000000000000000000000000112233445566778899aabbccddeeff00112233",
"value": "2500000000",
"salt": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
"hookData": {
"remoteDomain": 10001,
"remoteDepositor": "0xc0ffee254729296a45a3885639ac7e10f9d54979",
"remoteToken": "0x74ed63088c070c8fd5d8ad71f2a1cef868c63d00e0ac6dc2a6722d171691a422",
"forwardingContractAddress": "0x0000000000000000000000000000000000000000",
"forwardingCalldata": "0x"
}
}
}
],
"encoded": "0x8ddf3a...f9a2",
"messageHashToSign": "0x4f5c6d7e8f90123456789abcdeffedcba9876543210fedcba9876543210abcd"
}
]
}
```
## Step 3. Sign the message hash
Use your [attester](/xreserve/concepts/technical-guide#attesters) keys to sign
the `messageHashToSign` returned in the previous step. This produces the burn
intent signatures.
When a withdrawal draws on more than one xReserve source blockchain (for
example, reserves held on both Ethereum and Arc), `/prepare-withdrawal`
returns a `burnIntents` array with one entry per source blockchain and a
single `messageHashToSign` computed over the entire set. Sign that one hash
and submit all intents together. The burn amount on your blockchain must equal
the sum of `value` plus `maxFee` across every intent in the batch.
## Step 4. Submit the withdrawal
Send the encoded burn intent payload, the array of burn signatures, and the burn
transaction hash to the
[`/withdraw`](/api-reference/xreserve/all/submit-withdrawal) endpoint. Set
`useCircleForwarding` to `true` if you want Circle to submit the withdrawal on
behalf of your user.
**Note**: If you don't use Circle
[forwarding](/xreserve/concepts/technical-guide#withdrawal-forwarding), you'll
need to perform an additional crosschain transfer to withdraw funds from
xReserve.
The following is an example request:
```json json theme={null}
{
"batches": [
{
"burnIntents": {
"maxBlockHeight": "18976543",
"maxFee": "750000",
"spec": {
"version": 1,
"sourceDomain": 0,
"destinationDomain": 0,
"sourceContract": "0x0000000000000000000000000077777d7eba4688bdef3e311b846f25870a19b9",
"destinationContract": "0x0000000000000000000000000022222abe238cc2c7bb1f21003f0a260052475b",
"sourceToken": "0x74ed63088c070c8fd5d8ad71f2a1cef868c63d00e0ac6dc2a6722d171691a422",
"destinationToken": "0x0000000000000000000000001c7d4b196cb0c7b01d743fbc6116a902379c7238",
"sourceDepositor": "0x000000000000000000000000c0ffee254729296a45a3885639ac7e10f9d54979",
"destinationRecipient": "0x000000000000000000000000aabbee11223344556677889900aabbccddeeff00",
"sourceSigner": "0x0000000000000000000000005555555555555555555555555555555555555555",
"destinationCaller": "0x00000000000000000000000000112233445566778899aabbccddeeff00112233",
"value": "2500000000",
"salt": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
"hookData": {
"remoteDomain": 10001,
"remoteDepositor": "0xc0ffee254729296a45a3885639ac7e10f9d54979",
"remoteToken": "0x74ed63088c070c8fd5d8ad71f2a1cef868c63d00e0ac6dc2a6722d171691a422",
"forwardingContractAddress": "0x0000000000000000000000000000000000000000",
"forwardingCalldata": "0x"
}
}
},
"burnSignatures": [
"0x9c1d2e3f4a5b6c7d8e9f00112233445566778899aabbccddeeff0011223344556677",
"0x7f6e5d4c3b2a19080706050403020100ffeeddccbbaa99887766554433221100"
],
"burnTxId": "0x5a7b3c1d4e6f8091a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f70819",
"useCircleForwarding": true
}
]
}
```
**Response**
The API returns `withdrawalId`, a unique identifier for each withdrawal batch.
For example:
```json json theme={null}
[
{
"withdrawalId": "6149dc3d-71bf-4d57-8cc1-5e2d4c0a8e70",
"transferSpecHashes": [
"0x23f8c66d5a8bb5b712f2f4bc1c0a5a51d7c2b4f93d587f1449bcf3da6d8e1f20"
],
"verificationStatus": "unverified",
"attestation": null,
"requireCircleRelay": true
}
]
```
## Step 5. Monitor withdrawal status
Check the status of your withdrawal by calling
[`GET /withdrawals/{withdrawalId}`](/api-reference/xreserve/all/get-withdrawal-status).
xReserve releases funds once the `status` is `finalized`. If the status remains
`created`, `verified`, or `unverified`, keep polling. If the status changes to
`failed`, resolve the issue and resubmit the withdrawal.