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

# Place your first order

> Submit a burn order to the Match sandbox and check its status.

A burn order redeems USDC for USD through Match's batch auction. Submissions are
asynchronous; fill results arrive after the auction cycle closes.

## Prerequisites

Before you begin, ensure that you've:

* Obtained a Circle API key with Match access
* Created a Circle Mint account and funded it with a USDC balance to cover the
  burn order
* Added a linked fiat account in Circle Mint to receive settlement proceeds

See [Funding model](/circle-match/concepts/funding-model) for how USDC is
reserved on the burn side.

## Step 1: Place the order

Send a `POST /v1/match/orders` request to create a burn order. The
`idempotencyKey` you supply becomes the `orderId` for all subsequent lookups.
Use a unique UUID v4 for each new order.

```bash theme={null}
curl -X POST https://api-sandbox.circle.com/v1/match/orders \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "idempotencyKey": "550e8400-e29b-41d4-a716-446655440000",
    "orderType": "BURN",
    "amount": {
      "amount": "500.00",
      "currency": "USD"
    },
    "feeBps": "5",
    "postFillAction": "cancel",
    "sourceWalletId": "$WALLET_ID",
    "fiatAccountId": "$FIAT_ACCOUNT_ID"
  }'
```

For the full request schema and field descriptions, see
[Place order](/api-reference/circle-match/all/place-order) in the API reference.

A successful submission returns `202 Accepted`:

```json theme={null}
{
  "data": {
    "auctionId": 42,
    "orderId": "550e8400-e29b-41d4-a716-446655440000",
    "status": "pending"
  }
}
```

The `orderId` matches the `idempotencyKey` you supplied. The `auctionId`
identifies the auction cycle your order entered.

## Step 2: Check order status

Fill is asynchronous. The `status` stays `pending` until the auction cycle
closes and matching runs. Poll `GET /v1/match/orders/{id}` using your `orderId`
to check progress.

```bash theme={null}
curl https://api-sandbox.circle.com/v1/match/orders/550e8400-e29b-41d4-a716-446655440000 \
  -H "Authorization: Bearer $API_KEY"
```

While the auction is still open, you'll see:

```json theme={null}
{
  "data": {
    "orderId": "550e8400-e29b-41d4-a716-446655440000",
    "auctionId": 42,
    "lineage": {
      "parentOrderId": null,
      "childOrderId": null
    },
    "orderType": "BURN",
    "amount": { "amount": "500.00", "currency": "USD" },
    "feeBps": "5",
    "postFillAction": "cancel",
    "status": "pending",
    "createdAt": "2026-08-17T00:00:00Z",
    "updatedAt": "2026-08-17T00:00:00Z",
    "sourceWalletId": "1000001234",
    "fiatAccountId": "550e8400-e29b-41d4-a716-446655440001",
    "fill": null
  }
}
```

Once the auction clears, `status` transitions to one of the following terminal
or settlement values:

| Status | Meaning |
| - | - |
| `settling` | Matched; funds are moving to settlement |
| `filled` | The full order amount matched |
| `partial_fill` | Only part of the order matched |
| `unfilled` | The auction closed with no match |
| `cancelled` | The order was cancelled before it matched |
| `failed` | USDC funding was not received before the auction closed; no trade occurred |

After a match, the response includes a `fill` object with the cleared amounts
and fee:

```json theme={null}
{
  "data": {
    "orderId": "550e8400-e29b-41d4-a716-446655440000",
    "auctionId": 42,
    "lineage": {
      "parentOrderId": null,
      "childOrderId": null
    },
    "orderType": "BURN",
    "amount": { "amount": "500.00", "currency": "USD" },
    "feeBps": "5",
    "postFillAction": "cancel",
    "status": "filled",
    "createdAt": "2026-08-17T00:00:00Z",
    "updatedAt": "2026-08-17T00:05:00Z",
    "sourceWalletId": "1000001234",
    "fiatAccountId": "550e8400-e29b-41d4-a716-446655440001",
    "fill": {
      "filledAmount": { "amount": "500.00", "currency": "USD" },
      "unfilledAmount": { "amount": "0.00", "currency": "USD" },
      "clearingFeeBps": "3",
      "matchedAt": "2026-08-17T00:05:00Z"
    }
  }
}
```

`clearingFeeBps` reflects the actual fee applied at settlement, which will not
exceed your `feeBps` limit.

<Note>
  As an alternative to polling, subscribe to the WebSocket account channel to
  receive real-time order status events without repeated HTTP requests.
</Note>