# Robinhood Chain Contract Event Logs

> Robinhood Chain Contract Event Logs is a paid API for AI agents from x402-services-production.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Fetches on-chain event logs emitted by a smart contract on Robinhood Chain over a recent block window, with optional topic0 filtering

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/rhchain/logs
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robinhood-chain-contract-event-logs-746678df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AX4NSWOe98-4YSQM8xGta

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 robinhood-chain-contract-event-logs-746678df -d '<json body>'
```

Example prompt: Pull the recent event logs for contract address 0xAbC123... on Robinhood Chain — filter by topic0 0xddf252... so I only see Transfer events from the last 500 blocks.

## When to prefer this

Use this endpoint when you specifically need event log data from smart contracts deployed on Robinhood Chain (RH Chain), especially when you want to filter by event type via topic0. Prefer this over generic EVM log endpoints when working within the Robinhood Chain ecosystem, or when monitoring tokenized equity contract events that are native to that chain.

## Known failure modes

- Invalid or non-existent contract address returns empty logs or error
- Malformed topic0 hash causes filter to return no results
- Block window too large may be capped or time out
- Contract not deployed on Robinhood Chain returns no logs
- Missing required 'address' field returns validation error

## How this service works

Robinhood Chain event logs for a contract over a recent block window (optionally filtered by topic0). Send { address, topic0?, blocks? }.

## Output

Returns a list of event log entries emitted by the specified contract on Robinhood Chain within the requested block window. Each log typically includes the block number, transaction hash, log index, topics array (with topic0 as the event signature), and the raw data field. Results can be filtered to a specific event type via topic0.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robinhood-chain-contract-event-logs-746678df/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-services-production.up.railway.app](https://www.zero.xyz/host/x402-services-production.up.railway.app/llms.txt)