# Coins Agent Check — BSC Transaction Reconciliation

> Coins Agent Check — BSC Transaction Reconciliation is a paid API for AI agents from coins.zhidun.ai, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-27).

Reconciles a BNB Smart Chain transaction against expected ERC-20 token receipts and validates minimum net received amounts

## Facts

- Endpoint: POST https://coins.zhidun.ai/v1/bsc/reconcile?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coins-agent-check-bsc-transaction-reconciliation-10cf9932
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m0Qaus1g6HD2-YHHiGpHP

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 coins-agent-check-bsc-transaction-reconciliation-10cf9932 -d '<json body>'
```

Example prompt: Check whether BSC transaction 0xabc123...def456 delivered at least 1000000 units of token 0xTokenAddress to my account 0xMyWallet on chain 56.

## When to prefer this

Choose this endpoint when you need to verify or reconcile a specific BNB Smart Chain (BSC, chain 56) transaction against expected ERC-20 token receipts with minimum amount thresholds. It is ideal for agentic payment verification workflows, DeFi settlement confirmation, marketplace escrow checks, or any scenario where you need cryptographic on-chain evidence that a BSC token transfer met a minimum threshold — especially when you have a transaction hash and want a structured reconciliation report rather than raw RPC data.

## Known failure modes

- Invalid transaction hash format (not 0x + 64 hex chars) returns validation error
- Transaction not found on BSC chain 56 returns not-found error
- Account address not involved in the specified transaction returns mismatch
- Net received amount below specified minimum returns reconciliation failure
- chainId other than 56 is rejected by schema constraint
- Token address pattern mismatch causes input validation failure
- Payment of 0.02 USDC via x402 not fulfilled returns 402 Payment Required

## How this service works

USDC receipt evidence for x402 merchants and wallet agents. Try a free public-chain receipt example, then verify your own Base USDC transfers for 0.02 USDC per report.

## Output

Returns a JSON report with kind 'bsc_receipt_reconciliation', a private report ID, and details on whether the transaction on BSC chain 56 delivered the expected minimum net token amounts to the specified account — providing cryptographic transaction evidence and pass/fail reconciliation per token expectation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "txHash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$"
  },
  "account": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  },
  "chainId": {
   "type": "number",
   "const": 56
  },
  "expected": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "token",
     "minimumNetReceivedRaw"
    ],
    "properties": {
     "token": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$"
     },
     "minimumNetReceivedRaw": {
      "type": "string",
      "pattern": "^(0|[1-9][0-9]{0,77})$"
     }
    },
    "additionalProperties": false
   },
   "default": [],
   "maxItems": 10
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "bsc_receipt_reconciliation",
  "reportId": "private-request-hash"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coins-agent-check-bsc-transaction-reconciliation-10cf9932/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from coins.zhidun.ai](https://www.zero.xyz/host/coins.zhidun.ai/llms.txt)