> ## 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 USDC transfer fees > Retrieves the applicable fees for a USDC transfer between the specified source and destination domains. The fee is returned in basis points (1 = 0.01%). ## OpenAPI ````yaml openapi/cctp.yaml get /v2/burn/USDC/fees/{sourceDomainId}/{destDomainId} openapi: 3.0.2 info: version: '1.0' title: Cross-Chain Transfer Protocol (CCTP) description: > Circle's Cross-Chain Transfer Protocol enables you to build seamless user experiences for sending and transacting USDC natively across blockchains. CCTP endpoints enable advanced capabilities such as fetching attestations for faster-than-finality burn events, verifying public keys across versions, accessing transaction details, querying Fast Transfer allowances and fees, and initiating re-attestation processes. servers: - url: https://iris-api-sandbox.circle.com - url: https://iris-api.circle.com security: [] tags: - name: CCTP description: Cross-Chain Transfer Protocol endpoints - name: CCTP V1 (Legacy) description: Legacy Cross-Chain Transfer Protocol endpoints - name: Quotes description: Signed, time-bound fee quotes for USDC transfers paths: /v2/burn/USDC/fees/{sourceDomainId}/{destDomainId}: get: tags: - CCTP summary: Get USDC transfer fees description: >- Retrieves the applicable fees for a USDC transfer between the specified source and destination domains. The fee is returned in basis points (1 = 0.01%). operationId: getBurnUsdcFees parameters: - $ref: '#/components/parameters/SourceDomainIdPath' - $ref: '#/components/parameters/DestinationDomainIdPath' - in: query name: forward description: >- Whether to include fees for using the Circle Forwarder in the return value. required: false schema: type: boolean default: false - in: query name: hyperCoreDeposit description: >- Whether to include the forwarding fee for depositing into HyperCore in the return value. This parameter should only be used if the `forward` parameter is set to `true` and the destination domain is HyperEVM. required: false schema: type: boolean default: false responses: '200': description: Successfully retrieved the USDC transfer fees. content: application/json: schema: $ref: '#/components/schemas/USDCBurnFeesResponseV2' '400': $ref: '#/components/responses/BadRequest' '404': $ref: '#/components/responses/NotFound' components: parameters: SourceDomainIdPath: name: sourceDomainId description: Source domain identifier for a blockchain on CCTP. in: path required: true schema: type: integer minimum: 0 example: 3 DestinationDomainIdPath: name: destDomainId description: Destination domain identifier for a blockchain on CCTP. in: path required: true schema: type: integer minimum: 0 example: 3 schemas: USDCBurnFeesResponseV2: title: GetBurnUSDCFeesResponse type: array items: type: object required: - finalityThreshold - minimumFee properties: finalityThreshold: type: integer description: >- The finality threshold, such as block confirmations, used to determine whether the transfer qualifies as a Fast or Standard Transfer. minimumFee: type: number description: >- Minimum fees for the transfer, expressed in basis points (bps). For example, 1 = 0.01%. forwardFee: type: object description: >- Gas and forwarding fees for using the Circle Forwarder in USDC minor units. properties: low: type: integer description: The low gas estimate plus forwarding fee. example: 90 medium: type: integer description: The medium gas estimate plus forwarding fee. example: 110 high: type: integer description: The high gas estimate plus forwarding fee. example: 160 example: - finalityThreshold: 1000 minimumFee: 1 forwardFee: low: 90 medium: 110 high: 160 - finalityThreshold: 2000 minimumFee: 0 forwardFee: low: 90 medium: 110 high: 160 XRequestId: type: string format: uuid description: >- A unique identifier, which can be helpful for identifying a request when communicating with Circle support. example: 2adba88e-9d63-44bc-b975-9b6ae3440dde responses: BadRequest: content: application/json: schema: type: object title: BadRequestResponse required: - code - message properties: code: type: integer description: Code that corresponds to the error. message: type: string description: Message that describes the error. example: code: 400 message: Bad request. description: Request cannot be processed due to a client error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' NotFound: content: application/json: schema: type: object title: NotFoundResponse required: - code - message properties: code: type: integer description: Code that corresponds to the error. message: type: string description: Message that describes the error. example: code: 404 message: Not found. description: Specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' headers: XRequestId: description: > Developer-provided header parameter or Circle-generated universally unique identifier (UUID v4). Useful for identifying a specific request when communicating with Circle Support. schema: $ref: '#/components/schemas/XRequestId' ````