# Arbitrum Event Log Reader

> Arbitrum Event Log Reader is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-19).

Fetches recent event logs from a smart contract address on the Arbitrum One blockchain, with optional block range and topic filtering.

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/arb/logs?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/arbitrum-event-log-reader-c1a5e304
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-efQZMkj-4-hKqB3aSNpf

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-event-log-reader-c1a5e304
```

Example prompt: Fetch the last 100 blocks of event logs from the Arbitrum contract at 0xaf88d065e77c8cC2239327C5EDb3A432268e5831, and filter only Transfer events using topic hash 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef.

## When to prefer this

Use this endpoint when you need raw on-chain event logs from a specific Arbitrum One contract address, especially when you want to filter by event signature. Prefer this over Ethereum or Polygon log endpoints when the contract is deployed on Arbitrum. Ideal for DeFi monitoring, contract auditing, or building event-driven workflows on Arbitrum One.

## Known failure modes

- Invalid or malformed contract address returns an error
- Block range exceeding 1000 blocks is rejected
- Invalid topic0 hash format causes a filtering error
- Contract with no logs in the scanned range returns empty logs array
- Network congestion or RPC unavailability may cause timeout
- Payment failure results in no charge and no response

## How this service works

Recent contract event logs on Arbitrum One (eth_getLogs): the events a contract emitted over the last N blocks (1-1,000, default 50), optionally filtered by topic0 (the 0x 32-byte event signature hash). Returns up to 100 logs with block, transaction hash and topics. Use to watch transfers or contract events; for one transaction's outcome use arb_receipt.

## Output

Returns a JSON object containing an array of event log entries (each with transaction hash, raw data, block number, log index, and topics array), plus metadata including chain name, chain ID, from/to block range, total count, and a truncated flag indicating if results were capped.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "blocks": {
       "type": "integer",
       "examples": [
        50
       ],
       "description": "How many recent blocks to scan (1-1000, default 50)"
      },
      "topic0": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{64}$",
       "examples": [
        "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
       ],
       "description": "Optional 0x event signature hash to filter by"
      },
      "address": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{40}$",
       "examples": [
        "0xaf88d065e77c8cC2239327C5EDb3A432268e5831"
       ],
       "description": "0x contract address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "logs": {
       "type": "array",
       "items": {
        "type": "object",
        "properties": {
         "tx": {
          "type": "string"
         },
         "data": {
          "type": "string"
         },
         "block": {
          "type": "number"
         },
         "topics": {
          "type": "array",
          "items": {
           "type": "string"
          }
         },
         "logIndex": {
          "type": "number"
         }
        }
       }
      },
      "chain": {
       "type": "string"
      },
      "count": {
       "type": "number"
      },
      "address": {
       "type": "string"
      },
      "chainId": {
       "type": "number"
      },
      "toBlock": {
       "type": "number"
      },
      "fromBlock": {
       "type": "number"
      },
      "truncated": {
       "type": "boolean"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "logs": [
   {
    "tx": "0x…",
    "data": "0x…",
    "block": 123456780,
    "topics": [
     "0xddf2…"
    ],
    "logIndex": 3
   }
  ],
  "chain": "Arbitrum One",
  "count": 2,
  "address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
  "chainId": 42161,
  "toBlock": 123456789,
  "fromBlock": 123456739,
  "truncated": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/arbitrum-event-log-reader-c1a5e304/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)