> ## 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.

# Dev-controlled wallets

> Understand how dev-controlled wallets work, when to use them, and how Circle enables programmatic wallet infrastructure.

Dev-controlled wallets are blockchain wallets you manage programmatically from
your application. You control wallet creation, transaction execution, and
signing through Circle APIs and SDKs. For a comparison of all wallet products,
see [Choose your wallet product and account types](https://developers.circle.com/wallets/account-types.md).

## Key features

> [card] API-driven
>
> Create wallets and send transactions with Circle APIs and SDKs. No node
> setup or low-level signing required for supported chains. For unsupported chains, bring your own node with [Signing APIs](https://developers.circle.com/wallets/signing-apis.md).

> [card] You retain custody
>
> Your
> entity secret (A 32-byte secret that secures your dev-controlled wallets. Circle never stores it; you pass it in API calls to authorize signing. You are responsible for keeping it safe.)
> stays with you: built-in encryption, registration, rotation, and recovery
> keep compliance and custody clear.

> [card] Web3 for users
>
> Run transfers, smart contract interactions, and other onchain actions on
> behalf of your users so they can hold and use digital assets without
> managing keys or understanding blockchain details.

> [card] Scalability
>
> Scale to many wallets across chains from a single entity secret. Supports
> unified EVM addresses and high throughput across ECDSA and EdDSA blockchains.

Dev-controlled wallets are designed for server-side, automated, or custodial use
cases. You define policies, execute transactions, and manage wallet operations.
Unlike user-controlled wallets, end users don't control the private keys
directly.

## What you can build

Use dev-controlled wallets when you need funds you control, automation, or many
wallets from a single API. Here are some common use cases:

> [accordion] Custodial wallets
>
> You hold and manage assets on behalf of users; they don't control keys
> directly. You create and fund wallets per user or account, execute
> withdrawals and transfers when users request them, and enforce your own
> policies (limits, KYC, fraud checks) before any onchain action.
>
> If your platform holds assets on behalf of end users, regulatory licensing
> requirements may apply in your jurisdiction. See
> [Compliance requirements](https://developers.circle.com/wallets/compliance-requirements.md) for details.

> [accordion] Treasury and liquidity management
>
> Manage platform reserves, liquidity pools, and rebalancing from programmatic
> wallets. You hold and move funds between pools or protocols, execute
> rebalancing or yield strategies, and keep operational and reserve wallets
> under one entity secret and API surface.
>
> Dev-controlled wallets do not include a built-in policy engine. If you
> require transaction restrictions, destination allowlists, or multi-party
> approval flows, enforce those controls in your own application logic before
> calling Circle APIs.

> [accordion] Automated payouts
>
> Run scheduled or event-driven disbursements to many recipients. You trigger
> payouts (payroll, rebates, refunds, incentives) to a list of addresses or to
> wallets you create per recipient, with full control over timing, amounts,
> and auditability.

> [accordion] Exchange or marketplace infrastructure
>
> Use programmatic wallets for deposits, withdrawals, and settlement. Incoming
> funds land in wallets you control; you move assets between hot/cold or
> operational wallets, process withdrawals to user addresses, and settle
> marketplace or P2P trades without handing keys to end users.

> [accordion] Gaming or rewards systems
>
> Power in-game or loyalty balances and automated distribution. You create and
> fund wallets for players or reward recipients. You credit and debit balances
> using your logic, then run batch payouts or airdrops without each user
> managing their own keys.

## Account types

On EVM chains, a developer-controlled wallet is created as either an externally
owned account (EOA) or a smart contract account (SCA). Pick one based on your
needs. For non-EVM chains such as Aptos or Solana, see
[Choose your wallet product and account types](https://developers.circle.com/wallets/account-types.md) for a
full breakdown by blockchain.

> [card] EOA (Externally Owned Account)
>
> Select when the source wallet can hold native token for gas, you want simple
> key-controlled accounts, and you don't need multiple operations in one
> transaction (batch execution).

> [card] SCA (Smart Contract Account)
>
> Select when you need gas paid by a relayer or platform (gas sponsorship),
> batch execution, or other programmable behavior. For details on gas
> sponsorship, see [Gas Station](https://developers.circle.com/wallets/gas-station.md).

## Get started

Create your first dev-controlled wallet or jump straight to a fee-paying
transfer after the quickstart:

> [card] [Create a dev-controlled wallet](https://developers.circle.com/wallets/dev-controlled/create-your-first-wallet.md)
>
> Create a wallet set and EOA wallet on Arc Testnet, then use it in the
> transfer and signing guides.

> [card] [Send a transaction with fee](https://developers.circle.com/wallets/dev-controlled/transfer-tokens-across-wallets.md)
>
> Send USDC from one dev-controlled wallet to another and verify the recipient
> balance.
