# stall-row Receipt Verifier

> stall-row Receipt Verifier is a paid API for AI agents from stall-row-production.up.railway.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-20).

Verifies a Base blockchain transaction hash and returns a normalized receipt with payer, payee, USDC amount, settlement status, and candidate route matches.

## Facts

- Endpoint: POST https://stall-row-production.up.railway.app/v1/receipt-verify?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stall-row-receipt-verifier-88ca7d64
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RwzhwZJTCvtUMwGoRG2bi

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 stall-row-receipt-verifier-88ca7d64 -d '<json body>'
```

Example prompt: Someone says they paid for access — can you verify transaction hash 0xabc123... on Base and tell me the payer, the payTo address, the USDC amount, whether it's settled, and how many confirmations it has?

## When to prefer this

Use this endpoint when you need to verify a claimed USDC payment on the Base network from a transaction hash — especially in x402 payment flows where a user or counterparty asserts they paid and you want independent on-chain confirmation. Prefer this over trusting user-supplied receipts, off-chain claims, or third-party settlement assertions. Not suitable for Ethereum mainnet or other L2s.

## Known failure modes

- Unknown transaction hash returns an error indicating the tx could not be found on Base
- Transaction not yet settled returns an unsettled status rather than confirmed receipt
- Hash for a non-USDC transfer may yield no Transfer log data
- Only Base network is supported — Ethereum mainnet or other chains will error
- Amount matching candidate routes is non-deterministic — an amount alone cannot prove which route was called

## How this service works

Receipt Verifier — a Base transaction hash in, a normalized verified receipt out: payer, payTo and amount from the USDC Transfer log, asset and network, settled status and confirmations. When the payTo is this fleet's own and the amount matches a priced route, routes at that price are listed as candidates — an amount alone never proves which route was called. Unknown transactions error honestly, unsettled. Use this when someone claims they paid and you want the chain's version. Base only.

## Output

Returns a normalized receipt object containing: payer wallet address, payTo wallet address, USDC amount from the Transfer log, asset identifier, network (Base), settled boolean, confirmation count, and — if the payTo matches this fleet and the amount aligns with a known priced route — a list of candidate route matches. Unknown or unsettled transactions return an honest error.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx_hash": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stall-row-receipt-verifier-88ca7d64/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stall-row-production.up.railway.app](https://www.zero.xyz/host/stall-row-production.up.railway.app/llms.txt)
