# Transaction Evidence Brief

> Transaction Evidence Brief is a paid API for AI agents from transaction-evidence-brief-2026.bowu365.chatgpt.site, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-15).

Verifies and audits Base blockchain transactions by matching on-chain payment records against expected recipients, assets, and amounts.

## Facts

- Endpoint: POST https://transaction-evidence-brief-2026.bowu365.chatgpt.site/api/v1/reconcile/paid
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transaction-evidence-brief-8877fe60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pegd-KRYVD_RmCGrl4a0V

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 transaction-evidence-brief-8877fe60 -d '<json body>'
```

Example prompt: Can you verify that transaction 0x904a17eb77255e1208eea43f3519ec6e5c04c417a21453bb239e1a6de0c8a797 on Base actually paid the right recipient at 0xAbCd1234...5678 and generate an audit brief confirming it matched?

## When to prefer this

Use this endpoint when you need a deterministic, auditable record confirming that one or more Base blockchain transactions actually paid the correct recipient address, asset, and amount — especially for x402 micropayment trails, agent audit logs, or automated reconciliation of crypto invoices. Prefer it over generic block explorers when you need a structured pass/fail summary suitable for downstream automation or compliance records.

## Known failure modes

- Invalid transaction hash format (must be 0x followed by 64 hex chars) returns validation error
- Transaction not yet finalized on Base returns unmatched or pending result
- Wrong expected recipient address causes matched:false for that entry
- Unsupported asset address format causes schema rejection
- Submitting more than 25 transactions in one request returns a validation error
- Network or RPC unavailability may return a 5xx error

## How this service works

Deterministic Base transaction evidence for agents and audit trails.

## Output

Returns a per-transaction array with each hash and a boolean 'matched' flag, plus a summary object with counts of submitted, matched, and mismatched transactions. No on-chain state is modified — the response is a deterministic evidence report suitable for audit logs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transactions": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "hash",
     "expectedRecipient"
    ],
    "properties": {
     "hash": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{64}$"
     },
     "expectedAsset": {
      "type": "string",
      "pattern": "^(native|0x[a-fA-F0-9]{40})$"
     },
     "expectedAmountRaw": {
      "type": "string",
      "pattern": "^(0|[1-9][0-9]*)$"
     },
     "expectedRecipient": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
     }
    },
    "additionalProperties": false
   },
   "maxItems": 25,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "results": [
   {
    "hash": "0x904a17eb77255e1208eea43f3519ec6e5c04c417a21453bb239e1a6de0c8a797",
    "matched": true
   }
  ],
  "summary": {
   "matched": 1,
   "submitted": 1,
   "mismatched": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transaction-evidence-brief-8877fe60/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from transaction-evidence-brief-2026.bowu365.chatgpt.site](https://www.zero.xyz/host/transaction-evidence-brief-2026.bowu365.chatgpt.site/llms.txt)