# Polygon Transaction Receipt Consistency Checker

> Polygon 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-15).

Validates that a caller-supplied Polygon transaction receipt matches the corresponding transaction data across key fields, flagging any inconsistencies.

## Facts

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

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

Example prompt: Can you check whether this Polygon transaction receipt is consistent with the transaction data I have — here's the JSON bundle with the transaction hash, from/to addresses, type, and chain ID — and tell me if anything doesn't match?

## When to prefer this

Choose this endpoint when you need a structured, field-level consistency check between a Polygon transaction and its receipt using caller-supplied data, particularly in payment verification workflows, fraud detection pipelines, or DeFi audit trails. It is purpose-built for Polygon PoS (mainnet chain ID 137 and testnet 80002) and returns machine-readable JSON suitable for automated downstream decisions. Prefer this over generic blockchain explorers when you need a deterministic per-field comparison rather than a raw data lookup.

## Known failure modes

- Malformed or invalid request_json input returns a parse error
- Missing required transaction or receipt fields causes incomplete analysis
- Caller-supplied data cannot be authenticated — service warns that matching records are not proof of authenticity
- Chain ID not in accepted list (137 or 80002) may yield unexpected results
- Service may return replay:false if the same request is deduplicated

## 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 JSON analysis containing field-by-field match results (hash, transaction_hash, from, to, type, chain_id), an overall consistency boolean, network context describing the Polygon PoS bridge model and accepted chain IDs, and any warnings about the evidential limitations of the check.

## 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": [
    "Matching supplied records are not proof of authenticity."
   ],
   "service_id": "polygon_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\":\"137\",\"transaction\":\"137\"}],\"consistent\":true,\"network_context\":{\"accepted_chain_ids\":[\"137\",\"80002\"],\"bridge_model\":\"root-child state sync plus checkpoint evidence\",\"completion_policy\":\"never inferred without supplied evidence\",\"protocol_family\":\"Polygon PoS\"}}",
   "evidence_scope": "caller_supplied_data",
   "analyzed_network": "polygon"
  },
  "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": "polygon_transaction_receipt_consistency",
   "executionId": "example-execution",
   "startedAtMs": 0,
   "amountAtomic": "10000",
   "resultSha256": "ecba55883debd477ff0b45f3d240fa2cceb3988c24b8471fe16d2d99a60ceb02",
   "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/polygon-transaction-receipt-consistency-checker-7f7d5a94/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)