# Tollex x402 Payment Reconciliation

> Tollex x402 Payment Reconciliation is a paid API for AI agents from api.tollex.org, paid per call via x402, $0.0079/call, status unknown (last checked 2026-10-11).

Reconciles an uncertain or pending x402 USDC payment operation by operation ID and returns a signed receipt confirming final settlement status.

## Facts

- Endpoint: POST https://api.tollex.org/tools/x402_reconcile_operation?utm_source=zero.xyz
- Price: $0.0079/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tollex-x402-payment-reconciliation-ba3951ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4mroOCStNdbbKy2e3LcRP

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 tollex-x402-payment-reconciliation-ba3951ad -d '<json body>'
```

Example prompt: Can you reconcile the Tollex payment operation with ID 00000000-0000-4000-8000-000000000001 and get me the signed receipt so I can confirm the USDC transaction settled?

## When to prefer this

Use this endpoint when a prior x402 payment operation initiated through Tollex returned an uncertain or ambiguous status and you need to definitively confirm whether the USDC or USDG payment settled. This is specifically for post-payment reconciliation — not for initiating new payments or discovering capabilities. Prefer this over generic blockchain explorers when you need a Tollex-signed receipt with policy-audit metadata attached.

## Known failure modes

- Invalid or malformed operationId (not a valid UUID v4 format) returns a 400 error
- Unknown operationId that does not correspond to any operation returns a 404
- Operation is still in-flight and cannot yet be reconciled, requiring a retry
- Network or blockchain confirmation delays causing a timeout
- Insufficient funds or failed on-chain transaction flagged in the reconciliation result

## How this service works

Tollex lets software agents buy APIs and tools under rules you set: it finds a capability that fits, checks your policy before anything is signed, pays with x402 in USDC on Base or USDG on Robinhood Chain, reconciles uncertain payments and returns a signed receipt.

## Output

A signed receipt confirming the final settlement status of the specified payment operation, including whether the USDC payment on Base or USDG on Robinhood Chain was successfully completed, along with any reconciliation details needed for auditing or retry logic.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "operationId": {
   "type": "string",
   "pattern": "^[0-9a-f-]{36}$",
   "examples": [
    "00000000-0000-4000-8000-000000000001"
   ]
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": {
   "id": "x402_reconcile_operation",
   "version": "1.0.0",
   "provider": "tollex.robinhood-chain"
  },
  "result": {
   "found": true,
   "state": "reconciled",
   "scheme": "exact",
   "chainState": {
    "found": true,
    "status": "success"
   },
   "consistent": true,
   "operationId": "00000000-0000-4000-8000-000000000001",
   "transaction": "0x7a3d7400b27830f4f91c2c16a082486d67c1befecaec2f53b33f1f35d5b62036",
   "failureClass": null
  },
  "evidence": [],
  "untrustedOutput": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tollex-x402-payment-reconciliation-ba3951ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.tollex.org](https://www.zero.xyz/host/api.tollex.org/llms.txt)