# Base Transaction Receipt Consistency Checker

> Base Transaction Receipt Consistency Checker is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Validates that fields in a Base blockchain transaction receipt match the corresponding transaction data, detecting inconsistencies across key fields like hash, from, to, type, and chain ID.

## Facts

- Endpoint: POST https://signalharness.ai/api/agent/services/base_transaction_receipt_consistency/invoke
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-transaction-receipt-consistency-checker-bd6410bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BGl5IOWb57p2DdlMs6QQO

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 base-transaction-receipt-consistency-checker-bd6410bf -d '<json body>'
```

Example prompt: Can you check whether this Base network transaction receipt is consistent with the transaction data? Here's the JSON with both the transaction and receipt details — I want to know if fields like the hash, from address, to address, chain ID, and type all match up.

## When to prefer this

Choose this endpoint when you need a structured, field-by-field consistency audit of a Base blockchain transaction and its receipt — particularly useful for agent payment workflows, fraud detection, or audit pipelines on the Base/OP Stack network. It does not fetch on-chain data itself but validates that caller-supplied transaction and receipt objects agree with each other.

## Known failure modes

- Malformed or invalid JSON input results in a parsing error
- Missing required transaction or receipt fields cause incomplete field checks
- Inconsistent fields return consistent=false with specific mismatched field details
- Caller-supplied data cannot prove on-chain authenticity — only internal consistency is verified
- Unsupported chain IDs outside Base mainnet (8453) or testnet (84532) may produce unexpected results

## How this service works

Explore 330 pay-per-call x402 API services and 27 agent-native digital products, with Base USDC pricing, secure Polar checkout, and free discovery.

## Output

Returns a detailed JSON analysis with per-field match results (hash, transaction_hash, from, to, type, chain_id), an overall 'consistent' boolean, network context including accepted chain IDs and OP Stack fee model metadata, plus any warnings about the limits of caller-supplied data as proof of authenticity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "request_json": {
   "type": "string",
   "maxLength": 65536,
   "minLength": 2
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "replay": false,
  "result": {
   "warnings": [
    "Consistent supplied records are not proof of authenticity."
   ],
   "service_id": "base_transaction_receipt_consistency",
   "analysis_json": "{\"checks\":[{\"field\":\"hash\",\"match\":true,\"receipt\":\"0x1111111111111111111111111111111111111111111111111111111111111111\",\"transaction\":\"0x1111111111111111111111111111111111111111111111111111111111111111\"},{\"field\":\"transaction_hash\",\"match\":true,\"receipt\":\"0x1111111111111111111111111111111111111111111111111111111111111111\",\"transaction\":\"0x1111111111111111111111111111111111111111111111111111111111111111\"},{\"field\":\"from\",\"match\":true,\"receipt\":\"0x0000000000000000000000000000000000000001\",\"transaction\":\"0x0000000000000000000000000000000000000001\"},{\"field\":\"to\",\"match\":true,\"receipt\":\"0x0000000000000000000000000000000000000002\",\"transaction\":\"0x0000000000000000000000000000000000000002\"},{\"field\":\"type\",\"match\":true,\"receipt\":\"0x2\",\"transaction\":\"0x2\"},{\"field\":\"chain_id\",\"match\":true,\"receipt\":\"8453\",\"transaction\":\"8453\"}],\"consistent\":true,\"network_context\":{\"accepted_chain_ids\":[\"8453\",\"84532\"],\"deposit_transaction_type\":\"0x7e\",\"fee_model\":\"L2 execution plus caller-supplied L1 data/operator components\",\"protocol_family\":\"OP Stack\"}}",
   "evidence_scope": "caller_supplied_data",
   "analyzed_network": "base"
  },
  "status": "succeeded",
  "receipt": {
   "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "usage": [],
   "status": "succeeded",
   "network": "eip155:8453",
   "artifacts": [],
   "endedAtMs": 0,
   "latencyMs": 0,
   "paymentId": "example-payment",
   "receiptId": "example-receipt",
   "requestId": "example-request",
   "serviceId": "base_transaction_receipt_consistency",
   "executionId": "example-execution",
   "startedAtMs": 0,
   "amountAtomic": "10000",
   "resultSha256": "dc81fe82f65d08177c9f1914dbcad5927f5f39e67ca33d726928e8e631db9fc9",
   "serviceVersion": "1.0.0",
   "settlementReference": "0x0000000000000000000000000000000000000000000000000000000000000000"
  },
  "artifacts": [],
  "requestId": "example-request",
  "executionId": "example-execution"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-transaction-receipt-consistency-checker-bd6410bf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from signalharness.ai](https://www.zero.xyz/host/signalharness.ai/llms.txt)