> ## 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. # How-to: Create deposit addresses > Generate blockchain deposit addresses to receive stablecoin deposits Generate blockchain-specific deposit addresses so your end customers can receive stablecoins from external wallets. After creating an address, you can list existing addresses for an account and monitor incoming deposits as they credit the account balance. ## Prerequisites Before you begin: * Obtain an API key for Digital Asset Accounts from Circle. * Have an onboarded and active account with an `accountId`. * Install cURL on your development machine. The Digital Asset Accounts API base URL is `https://api-sandbox.circle.com` for sandbox and `https://api.circle.com` for production. Set your API key in the `Authorization` header using the format `Bearer YOUR_API_KEY`. See [Sandbox environment](/digital-asset-accounts/references/testing-in-sandbox) and [Going to production](/digital-asset-accounts/references/going-to-production) for environment details. ## Steps ### Step 1. Generate a deposit address Create a deposit address for a specific blockchain. You can create multiple addresses per account, one for each blockchain. For valid `chain` values, see [Supported currencies and blockchains](/digital-asset-accounts/references/supported-currencies-and-blockchains). ```shell theme={null} curl --request POST \ --url https://api-sandbox.circle.com/v1/accounts/addresses/deposit \ --header 'Accept: application/json' \ --header 'Authorization: Bearer ${YOUR_API_KEY}' \ --header 'Content-Type: application/json' \ --data ' { "idempotencyKey": "${RANDOM_UUID}", "currency": "USD", "chain": "ETH", "accountId": "${ACCOUNT_ID}" } ' ``` **Response** ```json theme={null} { "data": { "id": "d1e2f3a4-b5c6-7890-def1-234567890abc", "address": "0xabcdef1234567890abcdef1234567890abcdef12", "currency": "USD", "chain": "ETH", "accountId": "1017381855" } } ``` Share the `address` value with your end customer. Any USDC sent to this Ethereum address is credited to the account. If you pass an unsupported value in the `chain` field, the API returns a `400` error: ```json theme={null} { "code": 400, "message": "Unsupported chain value. See supported currencies and blockchains for valid options." } ``` See the [supported currencies and blockchains](/digital-asset-accounts/references/supported-currencies-and-blockchains) reference for valid values. ### Step 2. List deposit addresses Retrieve all deposit addresses for an account. ```shell theme={null} curl --request GET \ --url 'https://api-sandbox.circle.com/v1/accounts/addresses/deposit?accountId=${ACCOUNT_ID}' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer ${YOUR_API_KEY}' ``` **Response** ```json theme={null} { "data": [ { "id": "d1e2f3a4-b5c6-7890-def1-234567890abc", "address": "0xabcdef1234567890abcdef1234567890abcdef12", "currency": "USD", "chain": "ETH", "accountId": "1017381855" } ] } ``` ### Step 3. Monitor incoming deposits Track stablecoins as they arrive at a deposit address. A stablecoin sent to a deposit address is recorded as a transfer with a blockchain source, so you monitor it with the Transfers endpoints. The Deposits endpoint returns bank deposits only. List the transfers that arrived from a blockchain by calling [List account transfers](/api-reference/digital-asset-accounts/all/list-account-transfers) with `sourceType=blockchain`. Pass the `clientEntityId` of the end customer that owns the account. You receive it when you [create a partner client](/api-reference/end-user-onboarding/create-partner-client). Without it, the list is empty. Results are sorted newest first, up to 50 per page. ```bash theme={null} curl --request GET \ --url 'https://api-sandbox.circle.com/v1/accounts/transfers?accountId=${ACCOUNT_ID}&clientEntityId=${CLIENT_ENTITY_ID}&sourceType=blockchain' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer ${YOUR_API_KEY}' ``` **Response** ```json theme={null} { "data": [ { "id": "f3a4b5c6-d7e8-9012-f345-6789abcdef01", "source": { "type": "blockchain", "chain": "ETH" }, "destination": { "type": "account", "id": "1017381855", "address": "0xabcdef1234567890abcdef1234567890abcdef12" }, "amount": { "amount": "1000.00", "currency": "USD" }, "transactionHash": "0x4cebf8f90c9243a23c77e4ae20df691469e4b933b295a73376292843968f7a63", "status": "complete", "createDate": "2026-03-16T08:30:00Z" } ] } ``` Use the following fields to identify each deposit: * `destination.address`: the deposit address that received the funds * `source.chain`: the blockchain the funds arrived on * `transactionHash`: the hash of the onchain transaction * `status`: `pending`, `complete`, or `failed` ### Step 4. Get a deposit Retrieve a single deposit by its transfer ID, for example to check whether a `pending` deposit is now `complete`. Use the `id` value from the list response in Step 3. For the full response schema, see [Get an account transfer](/api-reference/digital-asset-accounts/all/get-account-transfer). ```bash theme={null} curl --request GET \ --url https://api-sandbox.circle.com/v1/accounts/transfers/${TRANSFER_ID} \ --header 'Accept: application/json' \ --header 'Authorization: Bearer ${YOUR_API_KEY}' ``` **Response** ```json theme={null} { "data": { "id": "f3a4b5c6-d7e8-9012-f345-6789abcdef01", "source": { "type": "blockchain", "chain": "ETH" }, "destination": { "type": "account", "id": "1017381855", "address": "0xabcdef1234567890abcdef1234567890abcdef12" }, "amount": { "amount": "1000.00", "currency": "USD" }, "transactionHash": "0x4cebf8f90c9243a23c77e4ae20df691469e4b933b295a73376292843968f7a63", "status": "complete", "createDate": "2026-03-16T08:30:00Z" } } ``` ## See also * [Send crypto transfers](/digital-asset-accounts/howtos/crypto-transfers) * [Set up webhook notifications](/api-reference/webhook-endpoints#v2-notifications)