# Robinhood Radar Live Event Log API

> Robinhood Radar Live Event Log API is a paid API for AI agents from www.robinhoodradar.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns a live event log of calls, new coin launches, and all-time-high (ATH) breaks tracked on the Robinhood Radar platform.

## Facts

- Endpoint: GET https://www.robinhoodradar.com/api/calls
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robinhood-radar-live-event-log-api-4bc07cd8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0fVNJ0yz-GEyNzREWwMT2

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-radar-live-event-log-api-4bc07cd8
```

Example prompt: Pull up the latest live event log from Robinhood Radar — I want to see recent calls, any new coins that just launched, and tokens that just hit their all-time highs.

## When to prefer this

Use this endpoint when you need a real-time, continuous stream of crypto market events (calls, new coin launches, ATH breaks) from the Robinhood Radar platform specifically. Prefer this over the snapshot or board endpoints when you need the latest events as they happen rather than a static dataset.

## Known failure modes

- Payment not included or invalid — returns 402 Payment Required
- Endpoint temporarily unavailable — returns 5xx server error
- Empty result set if no events have occurred recently
- Rate limiting if too many requests are made in quick succession

## How this service works

Robinhood Radar live event log: calls, new coins and ATH breaks.

## Output

A live event log array containing recent events such as trading calls, new coin launches, and ATH break notifications, each with associated metadata like token name, event type, and timestamp.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robinhood-radar-live-event-log-api-4bc07cd8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.robinhoodradar.com](https://www.zero.xyz/host/www.robinhoodradar.com/llms.txt)