Circle Usdc

Circle USDC is a US dollar stablecoin that Circle issues on several blockchains. (https://www.circle.com) A developer reaches it through Circle's own APIs for account-level actions. Balances and transfer history come from the token contract on each chain.

What developers mean by Circle USDC

USDC is a stablecoin that Circle issues and publishes as a token on multiple public blockchains. Circle documents the supported networks at https://www.circle.com, and that documentation is the authority for which chains a given release supports.

Each chain runs its own token contract with its own address. A balance check that reads the contract on one network does not read the deployment on another, so the chain is part of every request your code makes.

Choose between the Circle API and direct chain reads

The Circle API handles account-level actions, such as creating wallets and initiating transfers under your Circle account. Direct chain reads query the token contract and return balances, allowances, and transfer events for any address on that chain. Chain reads need no Circle account.

• Use the Circle API when your product moves money under a Circle account.
• Use direct chain reads when you only need to observe balances or transfers.
• Use both when an agent reads state first and then requests a transfer.

Separating the two paths also separates the permissions. A read-only agent needs chain access, and it never needs the credentials that authorize a transfer.

Give an agent USDC access through MCP tools

An MCP tool wraps one operation with a typed input schema. The tool returns JSON that the agent can parse. Keep read tools and write tools in separate definitions. An agent that only checks balances then holds no transfer permission.

Fix the chain and the contract address inside the tool definition. The agent supplies an address to check or a recipient to pay, but it cannot choose a different contract. Anyone can deploy a token named USDC, so the contract address is the only reliable identifier.

Set a maximum amount per call inside the tool. A limit written into the system prompt is a request to the model, not a control. The tool code is where the limit holds.

Read balances and transfer events

A balance read takes two inputs: the chain and the holder address. The tool calls the token contract and returns the amount in the token's smallest unit, along with the decimal places needed to format it. Convert that value once in your code, and keep the raw integer in your stored records.

Transfer history comes from the contract's event log. Filter the log by the token contract address and by the sender or recipient field. Confirm each event against a finalized block before you act on it, because a recent block can be reorganized.

Store the block number with each result. An agent that reads a balance without a block reference cannot tell a stale answer from a current one.

Price of tool calls through APIbase

Each tool call carries a price on its catalog entry. Per-call prices fall between 0 and 29.99 across the catalog. Each tool's page lists its exact price.

This page does not state Circle's own API charges. No verified public pricing source for that usage was available when this page was written, so check Circle's developer documentation before you set a budget for account-level calls.

Safety checks before a transfer

Test every write path on a testnet before you move mainnet funds. Confirm that the tool reads the testnet contract address and that the balance changes match what the test expected.

• Pin the chain ID and the contract address in code.
• Require a confirmation step for any transfer above your ceiling.
• Store API keys outside the agent's context window.
• Log each write call with its input and the resulting transaction hash.

Review the log after each run. A missing transaction hash means the write did not complete, and the agent should report that state instead of retrying blindly.

What this page does not cover

This page does not list Circle's full API surface or every supported blockchain. Both change over time. Circle's developer documentation is the current reference, and the APIbase catalog shows which Circle-related tools are available at the time you read this page.

Check the catalog before you assume a tool exists for a specific operation. A tool missing from the catalog means you need a direct integration or a custom MCP tool.

Live pricing — developer

Connect via MCP

$ curl -X POST https://apibase.pro/api/v1/tools/account.timeseries/call \
  -H "Content-Type: application/json" -d '{"params": {}}'

FAQ

Is Circle USDC the same token on every blockchain?

No. Circle issues USDC on several chains, and each chain has its own contract address. Verify the address for the chain you use against Circle's documentation before you send funds.

Can an AI agent hold and move USDC?

Yes, if you give it tools that call a wallet or transfer API. Restrict those tools to a fixed chain, a fixed contract, and a spending ceiling that your code enforces.

Do I need a Circle account to read a USDC balance?

No. A direct read of the token contract returns the balance for any address on that chain. A Circle account is needed only for actions performed under your Circle account, such as initiating transfers through the Circle API.

What does a Circle USDC tool call cost?

Per-call prices vary by tool and fall between 0 and 29.99. This page does not state Circle's own API charges because no verified public pricing source was available.

Recommended next step

1. STEP 1/2 Connect your MCP client
2. STEP 2/2 Browse the full catalog

Related guides

• llm api
• fabric iq mcp
• openweather api
• x402 payments

Published: 2026-11-02Source: live apibase.pro catalog snapshot