Back to Browse
Polygon Transaction Receipt Consistency Checker
x402
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.
Price / call$0.01
Success—
StatusUnknown
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.
Example use cases
Payment verification before releasing goods
“I received a Polygon transaction as payment and have the receipt and transaction data. Can you verify that the receipt hash, from address, to address, and chain ID all match the transaction before I mark the order as paid?”
DeFi protocol receipt audit
“We processed a batch of Polygon PoS transactions in our DeFi protocol and I want to check this specific transaction receipt against the transaction record to make sure no fields were tampered with — here's the combined JSON.”
Blockchain forensics consistency check
“I'm investigating a suspicious Polygon transaction and I have both the transaction data and the receipt. Can you compare them field by field — hash, from, to, type, chain ID — and flag any mismatches?”
Technical details
Endpoint
POSThttps://signalharness.ai/api/agent/services/polygon_transaction_receipt_consistency/invokeWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| request_json | string |
Output
Schema · Response
{
"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"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"