> ## 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 a contract > Get a single contract that you've imported or deployed. Retrieved using the contracts ID as opposed to the on-chain address. ## OpenAPI ````yaml openapi/smart-contract-platform.yaml get /v1/w3s/contracts/{id} openapi: 3.0.3 info: description: This is the Circle Contracts API documentation. title: Circle Contracts version: '1.0' servers: - url: https://api.circle.com security: - BearerAuth: [] tags: - name: Templates - name: View / Update - name: Interact - name: Deploy / Import - name: Event Monitors paths: /v1/w3s/contracts/{id}: get: tags: - View / Update summary: Get a contract description: >- Get a single contract that you've imported or deployed. Retrieved using the contracts ID as opposed to the on-chain address. operationId: getContract parameters: - $ref: '#/components/parameters/Id' - $ref: '#/components/parameters/XRequestId' responses: '200': content: application/json: schema: $ref: '#/components/schemas/ContractResponse' description: Contract retrieved successfully. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '400': content: application/json: schema: $ref: '#/components/schemas/Error' description: Error response for the request. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' security: - BearerAuth: [] components: parameters: Id: name: id description: The universally unique identifier of the resource. in: path required: true schema: type: string format: uuid example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 XRequestId: name: X-Request-Id in: header description: > Developer-provided identifier for this request, used for tracing requests in Wallets API logs and the Developer Console, and when communicating with Circle Support. **Must be a UUID to appear in logs.** Non-UUID values are accepted by the API but are ignored by logging and tracing systems. schema: $ref: '#/components/schemas/XRequestId' schemas: ContractResponse: title: ContractResponse type: object required: - data properties: data: type: object required: - contract properties: contract: $ref: '#/components/schemas/Contract' Error: title: Error type: object required: - code - message properties: code: type: integer description: Code that corresponds to the error. message: type: string description: Message that describes the error. 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 Contract: type: object required: - id - name - contractInputType - createDate - updateDate - archived - blockchain - status - functions - events - verificationStatus - sourceCode properties: id: $ref: '#/components/schemas/Id' deployerWalletID: $ref: '#/components/schemas/DeployerWalletId' deploymentTransactionId: $ref: '#/components/schemas/DeploymentTransactionId' txHash: $ref: '#/components/schemas/TransactionHash' abiJson: $ref: '#/components/schemas/AbiJson' archived: $ref: '#/components/schemas/Archived' blockchain: $ref: '#/components/schemas/Blockchain' bytecode: $ref: '#/components/schemas/Bytecode' contractAddress: $ref: '#/components/schemas/ContractAddress' contractInputType: $ref: '#/components/schemas/ContractInputType' deployerAddress: $ref: '#/components/schemas/DeployerAddress' deployerUserID: type: string format: uuid deploymentErrorReason: type: string deploymentErrorDetails: type: string name: $ref: '#/components/schemas/ContractName' description: $ref: '#/components/schemas/ContractDescription' status: $ref: '#/components/schemas/ContractStatus' verificationStatus: $ref: '#/components/schemas/VerificationStatus' metadataLink: $ref: '#/components/schemas/MetadataLink' updateDate: $ref: '#/components/schemas/UpdateDate' createDate: $ref: '#/components/schemas/CreateDate' sourceCode: $ref: '#/components/schemas/SourceCode' functions: $ref: '#/components/schemas/Functions' events: $ref: '#/components/schemas/Events' implementationContract: type: object description: Object of the implementation contract. Id: type: string format: uuid description: System-generated unique identifier of the resource. example: c4d1da72-111e-4d52-bdbf-2e74a2d803d5 DeployerWalletId: type: string format: uuid description: The `id` of the Circle Wallet that deployed this contract. example: f39e3dbd-84af-4d3d-b5ac-98fbe047ce6a DeploymentTransactionId: type: string format: uuid description: The id of the deployment transaction for this contract. example: 00ca46f3-c31b-4e3a-92a9-068d4ff26a63 TransactionHash: type: string description: Blockchain generated identifier of the transaction. example: '0x4a25cc5e661d8504b59c5f38ba93f010e8518966f00e2ceda7955c4b8621357d' AbiJson: type: string description: The contract's ABI in a JSON stringified format. example: >- [{"inputs": [],"stateMutability": "nonpayable","type": "constructor"},... Archived: description: >- The archive state of the contract. If true, the contract will not be visible in your dashboard. type: boolean example: false Blockchain: type: string description: > The blockchain network that the resource is to be created on or is currently on. Required along with `sourceAddress` if you don't provide `walletId`. The `blockchain` and `walletId` fields are mutually exclusive. enum: - ETH - ETH-SEPOLIA - MATIC - MATIC-AMOY - ARB - ARB-SEPOLIA - UNI - UNI-SEPOLIA - BASE - BASE-SEPOLIA - OP - OP-SEPOLIA - AVAX - AVAX-FUJI - ARC - ARC-TESTNET - MONAD - MONAD-TESTNET example: MATIC-AMOY Bytecode: type: string description: Bytecode of the contract being deployed. minLength: 1 writeOnly: true example: 0x60806040523480156200001157600080fd5b50604051806040... ContractAddress: type: string description: The on-chain address of this contract. example: '0x1e124d7384cd34448ea5907bd0052a79355ab5eb' ContractInputType: type: string description: The input type for the contract. enum: - IMPORT - BYTECODE - TEMPLATE - AUTO_IMPORT DeployerAddress: type: string description: The address that created this contract, if deployed. example: '0x1bf9ad0cc2ad298c69a2995aa806ee832788218c' ContractName: type: string description: The name for a contract. Must be alphanumeric [a-zA-Z0-9]. example: First Contract ContractDescription: type: string description: The description for a contract. example: My first hello world contract ContractStatus: type: string description: The status of the contract. enum: - PENDING - FAILED - COMPLETE VerificationStatus: type: string description: The verification status of the contract. enum: - UNVERIFIED - VERIFIED MetadataLink: type: string description: The ipfs metadata link of the contract. example: https://ipfs.io/ipfs/Qme7ss3ARVgxv6rXqVPiikMJ8u2NLgmgszg13pYrDKEoiu UpdateDate: type: string format: date-time description: Date and time the resource was last updated, in ISO-8601 UTC format. example: '2023-01-01T12:04:05Z' CreateDate: type: string format: date-time description: Date and time the resource was created, in ISO-8601 UTC format. example: '2023-01-01T12:04:05Z' SourceCode: type: array readOnly: true items: $ref: '#/components/schemas/SolFile' Functions: type: array description: Functions supported by this contract. Parsed from abi_json. items: $ref: '#/components/schemas/Function' Events: type: array description: Events this contract can emit. Parsed from abi_json. items: $ref: '#/components/schemas/Event' SolFile: type: object description: Source code of a contract from Etherscan. required: - fileContent properties: fileName: type: string description: Name of the file. example: openzeppelin-solidity/contracts/math/SafeMath.sol fileContent: type: string description: >- Content of the file. If the contract's source code was flattened before verification, this may be the entire source code. example: |- pragma solidity ^0.4.24; /** * @title SafeMath * @dev Math operations with safety checks... Function: type: object required: - type properties: name: type: string example: approve stateMutability: type: string example: nonpayable type: type: string example: function inputs: type: array items: $ref: '#/components/schemas/ParamType' outputs: type: array items: $ref: '#/components/schemas/ParamType' Event: type: object required: - type properties: name: type: string example: Approval type: type: string example: event anonymous: type: boolean example: false inputs: type: array items: $ref: '#/components/schemas/ParamType' ParamType: type: object properties: components: type: array items: $ref: '#/components/schemas/AnyValue' indexed: type: boolean name: type: string example: to type: type: string example: address flattenedType: type: string AnyValue: description: Can be any value - string, number, boolean, array or object. 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' securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: PREFIX:ID:SECRET description: >- Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are required to make a successful request. ````