# Base Contract Event Logs Reader

> Base Contract Event Logs Reader is a paid API for AI agents from auditor-x402.onrender.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-30).

Fetches recent event logs (via eth_getLogs) for any contract on Base, with optional topic0 filtering, returning up to 50 logs with block, tx hash, topics, and data.

## Facts

- Endpoint: POST https://auditor-x402.onrender.com/api/contract-logs?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-contract-event-logs-reader-6f790348
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MSTuT38q4VSvlvVBOFb6d

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 base-contract-event-logs-reader-6f790348 -d '<json body>'
```

Example prompt: Can you pull the recent event logs for the contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base, filtering by the Transfer event signature hash 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef, scanning the last 100 blocks?

## When to prefer this

Use this endpoint when you need generic event log queries for any Base contract not covered by specialized endpoints like whale-wallet-tracker or token-deploy-radar. Ideal when you know the contract address and optionally the event signature hash, and want raw log data including topics and calldata. Prefer this over full indexers when you only need a recent bounded window and don't need historical depth beyond 120 blocks.

## Known failure modes

- RPC log-range quota exceeded if windowBlocks is too large or contract is too active
- Invalid contract address returns empty logs or error
- Malformed topic0 hash causes filter to fail or return no results
- Block window outside allowed range (10-120) rejected
- Render.com cold start may cause initial latency or timeout
- No logs found returns empty array (not an error, but may confuse agent)

## How this service works

Recent event logs for any contract on Base over a bounded recent window (reads eth_getLogs). Optionally filter by topic0 (event signature hash). Returns up to 50 logs with block, tx hash, topics and data. Window is limited by the RPC log-range quota. Use this for generic event queries not covered by whale-wallet-tracker or token-deploy-radar.

## Output

Returns up to 50 recent event log entries, each containing block number, transaction hash, log index, topics array (including topic0 through topic3), and raw data hex — all scoped to the specified contract address within the requested block window.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "topic0": {
   "type": "string",
   "description": "Optional 32-byte event signature hash (0x...) to filter by"
  },
  "address": {
   "type": "string",
   "description": "Contract address (0x...) to read logs from"
  },
  "windowBlocks": {
   "type": "number",
   "description": "Blocks to scan (10-120, default 100)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-contract-event-logs-reader-6f790348/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from auditor-x402.onrender.com](https://www.zero.xyz/host/auditor-x402.onrender.com/llms.txt)