# Agent Commerce Gate — Settlement Receipt Binding

> Agent Commerce Gate — Settlement Receipt Binding is a paid API for AI agents from contextiq.trango-compute.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Binds a blockchain settlement receipt to a prior payment-authorization decision, confirming whether the on-chain transfer matches the expected payment terms

## Facts

- Endpoint: POST https://contextiq.trango-compute.com/api/v1/policy-check/receipt/x402-v2
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-commerce-gate-settlement-receipt-binding-e7d99eeb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_scx00X5dnwTjbwy2_XkkQ

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 agent-commerce-gate-settlement-receipt-binding-e7d99eeb -d '<json body>'
```

Example prompt: I just completed the on-chain payment for checkId 'chk_abc123' and the transfer confirmed — can you bind the settlement receipt to that prior authorization decision and tell me if the payment matched the expected payTo address and amount?

## When to prefer this

Use this endpoint as the final step of an x402 agent commerce flow after a pre-payment counterparty risk check has been completed and a payment has been submitted on-chain. It is the correct endpoint when you need to close the loop between a prior authorization decision and an actual blockchain settlement, rather than re-running the risk check or simply looking up a prior decision without a receipt.

## Known failure modes

- Unknown checkId — prior decision not found, returns not_found or error status
- Receipt status is 'not_found' — transaction not yet indexed on-chain
- matchesExpectedPayment is false — payment amount or payTo address mismatch, binding may be rejected
- Duplicate binding attempt — receipt already bound to this checkId
- Malformed receipt object — missing required fields causing validation error
- Network or blockchain indexer latency causing stale or unresolvable transaction status

## How this service works

Agent Commerce Gate — bind a settlement receipt to a prior decision — per call

## Output

Returns a binding confirmation that associates the provided settlement receipt with the prior decision identified by checkId, indicating whether the on-chain transfer status and payment match are reconciled against the original authorization terms.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "checkId": {
   "type": "string"
  },
  "receipt": {
   "type": "object",
   "properties": {
    "status": {
     "type": "string",
     "description": "confirmed, reverted, not_found, or error"
    },
    "matchesExpectedPayment": {
     "type": "boolean",
     "description": "Whether the on-chain transfer matches the payTo and amount from the original decision"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-commerce-gate-settlement-receipt-binding-e7d99eeb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from contextiq.trango-compute.com](https://www.zero.xyz/host/contextiq.trango-compute.com/llms.txt)