# Money AI USDC Settlement Check

> Money AI USDC Settlement Check is a paid API for AI agents from money-ai-shop.money-ai.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Verifies a USDC transaction on Base mainnet — confirming amount, recipient address, and confirmation count against live chain data.

## Facts

- Endpoint: POST https://money-ai-shop.money-ai.workers.dev/s/settlement-check
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/money-ai-usdc-settlement-check-74ceaf7c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T3q32u4AunaSWaEp_k2m4

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability money-ai-usdc-settlement-check-74ceaf7c -d '<json body>'
```

Example prompt: Can you verify that transaction 0xabc123def456... actually paid 1 USDC to 0xRecipient456... on Base — confirm the amount, the recipient, and how many confirmations it has?

## When to prefer this

Choose this endpoint when you need authoritative, live on-chain verification that a specific USDC payment landed correctly on Base — especially when the amount, recipient, and confirmation count all need to be checked together in a single call. Prefer it over general transaction decoders when your primary goal is pass/fail payment settlement validation rather than decoding full transaction internals.

## Known failure modes

- Transaction hash not found on Base mainnet — may be on wrong network or not yet mined
- Recipient address mismatch — actual recipient differs from expected
- Amount mismatch — USDC transferred differs from expected amount
- Transaction still pending — zero or insufficient confirmations
- Invalid transaction hash format — must be 66-character 0x-prefixed hex string
- RPC or chain connectivity issues causing lookup failure

## How this service works

Verify a USDC payment actually landed - amount, recipient and confirmations - checked against the chain rather than taken on trust. Answered from live Base mainnet, not a model, so it is current and costs the same every time. Use it for: Did tx 0xabc123... pay 1 USDC to the address I expected?; Confirm this payment settled and how many confirmations it has

## Output

Returns verification of whether the on-chain transaction matches the expected recipient address and USDC amount, along with the number of confirmations the transaction has received on Base mainnet — sourced live from the chain, not from cached or modeled data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx": {
   "type": "string",
   "description": "transaction hash (0x..., 66 chars)"
  },
  "skill": {
   "type": "string",
   "const": "settlement-check",
   "description": "which service to run"
  },
  "expect_to": {
   "type": "string",
   "description": "address the payment should have reached"
  },
  "expect_amount_usdc": {
   "type": "string",
   "description": "amount it should have been"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/money-ai-usdc-settlement-check-74ceaf7c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from money-ai-shop.money-ai.workers.dev](https://www.zero.xyz/host/money-ai-shop.money-ai.workers.dev/llms.txt)