# Arbitrum Transaction Receipt Lookup

> Arbitrum 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-11-20).

Fetches the on-chain receipt for an Arbitrum One transaction by its hash, returning status, gas used, block, fee, and log count.

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/arb/receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/arbitrum-transaction-receipt-lookup-7ffe8f2e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k4nOc-86k7vco6CXnIQJM

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 arbitrum-transaction-receipt-lookup-7ffe8f2e
```

Example prompt: Can you pull the receipt for Arbitrum transaction 0xf03682db039f7b1b72ddf4d17572738f142cf63ecb36c90afa570430ea9774c4 and tell me if it succeeded, what block it landed in, and how much gas was used?

## When to prefer this

Use this endpoint when you specifically need an Arbitrum One transaction receipt — status, gas, fee, block, and log details — by hash. Prefer it over generic block explorers when you need structured JSON output directly consumable by an agent. If you need receipts on other chains (Base, Ethereum, Optimism, Polygon), use the sibling chain-specific endpoints from the same provider.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on Arbitrum One (wrong chain or not yet indexed)
- Node or RPC timeout causing a failed lookup
- Hash from a different chain (e.g. Ethereum mainnet) will not resolve correctly on this endpoint

## How this service works

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

## Output

Returns a JSON object with the transaction hash, status (success/failure), block number, chain name and ID (Arbitrum One / 42161), gas used, effective gas price in Gwei, total fee in ETH, number of logs emitted, and contract address if a contract was deployed (null otherwise).

## 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/arbitrum-transaction-receipt-lookup-7ffe8f2e/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)
