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

# Reporting

> Reference for Managed Payments reporting: the report types available through the /v1/reports API, how to request and download them, and how they differ from Circle Mint reporting.

Managed Payments generates reports through the core Circle Reports API
([`/v1/reports`](/api-reference/circle-mint/account/request-report)). The
following report types cover Managed Payments activity only. They're separate
from the Circle Mint `camt053` daily statement, which isn't available on Managed
Payments keys.

## Report types

| `reportType` | Contents | `timeframe` | Format |
| - | - | - | - |
| `managed_payin_transactions` | Payin (deposit) transactions for the period | `daily`, `monthly` | CSV |
| `managed_payout_transactions` | Payout transactions for the period | `daily`, `monthly` | CSV |
| `managed_payment_wallet_balances` | Wallet and subaccount balance snapshot | `daily` | CSV |
| `camt_managed` | ISO 20022 CAMT.053 bank-to-customer statement, Managed Payments scope | `daily` | XML |

<Note>
  Use `camt_managed` for CAMT.053 statements on Managed Payments. The Circle
  Mint `camt053` type isn't valid on Managed Payments keys. It covers Circle
  Mint accounts, not Managed Payments. See [CAMT.053 daily
  statements](/circle-mint/references/camt053-statements) for the ISO 20022 XML
  structure, which `camt_managed` shares.
</Note>

## Request and download a report

1. Request the report with
   [`POST /v1/reports`](/api-reference/circle-mint/account/request-report),
   passing `reportType`, `timeframe` where the type supports it, and `date`.
   Format `date` to match the timeframe: daily reports use `YYYY-MM-DD` (for
   example, `2026-06-30`), and the monthly `managed_payin_transactions` and
   `managed_payout_transactions` reports use `YYYY-MM` (for example, `2026-06`).
   Passing a full date for a monthly report returns `400`. Circle interprets
   `date` in your entity's reporting timezone, not UTC. For example, a Circle SG
   entity uses Singapore Time (SGT). Circle generates Managed Payments reports
   on a schedule:
   * If the report is available, the response is `200 OK` with the report `id`
     and a pre-signed `downloadUrl`.
   * If the report is still being generated, the response is `202 Accepted` with
     a report `id` and no `downloadUrl`.
2. If the response was `202 Accepted`, poll
   [`GET /v1/reports/{id}`](/api-reference/circle-mint/account/get-report-by-id)
   until `status` is `ready` and a `downloadUrl` is present.
3. Download the report. Either fetch the file from `downloadUrl` before the time
   given by `expiresAt`, or stream it directly from
   [`GET /v1/reports/{id}/content`](/api-reference/circle-mint/account/get-report-content),
   which returns the raw file and responds with `409` if the report isn't
   `ready`. After a `downloadUrl` expires, call `GET /v1/reports/{id}` for a
   fresh URL. You can also request the report again. Requests are idempotent, so
   the same parameters return the same report.

```bash theme={null}
curl -X POST https://api-sandbox.circle.com/v1/reports \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"reportType":"camt_managed","timeframe":"daily","date":"2026-06-30"}'
```

```json theme={null}
{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "reportType": "camt_managed",
    "status": "ready",
    "downloadUrl": "https://s3.amazonaws.com/...",
    "expiresAt": "2026-06-30T15:00:00Z"
  }
}
```

<Info>
  `expiresAt` uses different formats across endpoints. Create (`POST
      /v1/reports`) and get-by-ID (`GET /v1/reports/{id}`) responses return it as an
  ISO 8601 timestamp, as in the preceding example. The list endpoint (`GET
      /v1/reports`) returns it as epoch milliseconds.
</Info>

## List generated reports

To find reports you've already generated, use
[`GET /v1/reports`](/api-reference/circle-mint/account/list-reports) with a
`reportType` and a date range. Each report in the response carries its own
pre-signed `downloadUrl`. The list endpoint doesn't return the Circle Mint
`camt053` statement. Request that report with `POST /v1/reports` instead.

<Warning>
  The `id` returned by `GET /v1/reports` is a storage object key (for example,
  `managed_payout_transactions/{UUID}/{date}/report.csv`), not the deterministic
  report UUID. You can't pass it to `GET /v1/reports/{id}` or `GET /v1/reports/   {id}/content`. Download a listed report from its own `downloadUrl`.
</Warning>