# Tollex Chain Get Logs

> Tollex Chain Get Logs is a paid API for AI agents from api.tollex.org, paid per call via x402, $0.0079/call, status unknown (last checked 2026-10-11).

Fetches EVM blockchain event logs filtered by contract address, event topic, and block range

## Facts

- Endpoint: POST https://api.tollex.org/tools/chain_get_logs?utm_source=zero.xyz
- Price: $0.0079/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tollex-chain-get-logs-e435f397
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zYn__hgv5-quaA-YI6L_5

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 tollex-chain-get-logs-e435f397 -d '<json body>'
```

Example prompt: Pull all on-chain logs for contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 where topic0 is 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef from block 18000000 to block 18001000.

## When to prefer this

Choose this endpoint when you need to query EVM-compatible blockchain event logs in a pay-per-call model with policy-controlled USDC micropayments via x402, without setting up your own RPC node or managing API keys. It is especially useful for AI agents that need on-demand, metered access to on-chain data with cryptographic payment receipts for auditability.

## Known failure modes

- Invalid address format (not a valid 40-character hex address) returns a validation error
- Invalid topic0 format (not a 64-character hex hash) returns a schema error
- fromBlock greater than toBlock returns an invalid range error
- Block range too large may return a timeout or truncated result
- No logs found in the specified range returns an empty array
- Payment failure or insufficient USDC balance results in a 402 Payment Required error
- Network congestion on Base or Robinhood Chain may delay receipt delivery

## How this service works

Tollex lets software agents buy APIs and tools under rules you set: it finds a capability that fits, checks your policy before anything is signed, pays with x402 in USDC on Base or USDG on Robinhood Chain, reconciles uncertain payments and returns a signed receipt.

## Output

An array of EVM event log objects matching the filter criteria, each containing fields such as block number, transaction hash, log index, contract address, topics array, and raw data payload. The response is delivered as a signed receipt via Tollex's x402 payment protocol after USDC payment is settled.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "topic0": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$"
  },
  "address": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  },
  "toBlock": {
   "type": "integer",
   "minimum": 0
  },
  "fromBlock": {
   "type": "integer",
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": {
   "id": "chain_get_logs",
   "version": "1.0.0",
   "provider": "tollex.robinhood-chain"
  },
  "result": {
   "logs": [
    {
     "tx": "0x7a3d7400b27830f4f91c2c16a082486d67c1befecaec2f53b33f1f35d5b62036",
     "data": "0x0000000000000000000000000000000000000000000000000000000000001edc",
     "topics": [
      "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
     ],
     "logIndex": 0,
     "blockNumber": "83335219"
    }
   ],
   "count": 1,
   "truncated": false
  },
  "evidence": [],
  "untrustedOutput": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tollex-chain-get-logs-e435f397/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.tollex.org](https://www.zero.xyz/host/api.tollex.org/llms.txt)