# Agent Data Tools: Polygon Transaction Receipt Lookup

> Agent Data Tools: Polygon Transaction Receipt Lookup is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Fetches the on-chain receipt for a Polygon PoS transaction by hash, returning status, gas used, fees, block number, and logs count.

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/polygon/receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-data-tools-polygon-transaction-receipt-lookup-399cec03
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_I10IaN1sHYWKiKTz-6JQW

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 agent-data-tools-polygon-transaction-receipt-lookup-399cec03
```

Example prompt: Can you pull up the receipt for Polygon transaction 0x23e86c30c46638b2e9798692fe89327a66aa8569a5d4a566125f655aeb8f80c7 and tell me if it succeeded, how much gas was used, and what fee was paid?

## When to prefer this

Use this endpoint when you need to verify the outcome of a specific Polygon PoS transaction — its success/failure status, gas cost, fee, block, or whether it deployed a contract. Prefer this over Ethereum/Base/Arbitrum/Optimism receipt endpoints specifically for chainId 137 (Polygon PoS). No API key required; payment is per-call at $0.001 USDC via x402.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on Polygon PoS returns not-found error
- Network/RPC timeout may return a 5xx error (not charged on failure)
- Passing an Ethereum or other chain's tx hash will not match Polygon data

## How this service works

Transaction receipt on Polygon PoS (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in POL, number of event logs and any contract created. Use to confirm a payment or call went through; for sender, value and calldata use polygon_tx. Input is a 0x-prefixed 64-hex hash; a pending or unknown hash returns 404, uncharged.

## Output

A JSON object containing: transaction hash, status (success/failure), block number, chain name ('Polygon PoS'), chainId (137), gasUsed (as string), effectiveGasPriceGwei (as string), fee in MATIC (as string), number of logs emitted, and contractAddress (null if not a deployment).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "hash"
 ],
 "properties": {
  "hash": {
   "type": "string",
   "description": "0x-prefixed transaction hash (64 hex characters)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "fee": {
   "type": "string"
  },
  "hash": {
   "type": "string"
  },
  "logs": {
   "type": "number"
  },
  "block": {
   "type": "number"
  },
  "chain": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "chainId": {
   "type": "number"
  },
  "gasUsed": {
   "type": "string"
  },
  "contractAddress": {},
  "effectiveGasPriceGwei": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-data-tools-polygon-transaction-receipt-lookup-399cec03/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)