# Robinhood Chain Oracle Health Check

> Robinhood Chain Oracle Health Check is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Verifies the health of a tokenized stock price oracle on Robinhood Chain by checking round validity, positive price answer, and freshness within the 24-hour heartbeat window for a given ticker symbol.

## Facts

- Endpoint: POST https://x402.forgemesh.io/robinhood-oracle-health
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robinhood-chain-oracle-health-check-2c053fa3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lwEooO3yiI0baKVamCYz9

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-oracle-health-check-2c053fa3 -d '<json body>'
```

Example prompt: Can you check if the AAPL price oracle on Robinhood Chain is healthy — specifically whether the latest round has a valid positive answer and the feed is within its 24-hour heartbeat window?

## When to prefer this

Use this endpoint when you need to verify the on-chain health of a Robinhood Chain price oracle for a specific tokenized stock ticker before relying on its price data in a DeFi application, smart contract, or trading system. Prefer this over generic oracle monitoring tools when you specifically need Robinhood Chain compatibility and granular round-level diagnostics including heartbeat window validation.

## Known failure modes

- Unknown or unsupported ticker symbol returns 'unsupported' status rather than an error
- Feed update timestamp outside the 24-hour heartbeat window returns 'stale'
- Round with zero or negative answer returns 'invalid'
- Round accounting inconsistencies (e.g., answeredInRound < roundId) return 'invalid'
- Network or RPC connectivity issues to Robinhood Chain may cause request failure
- Payment failure (insufficient USDC balance) results in 402 response before processing

## How this service works

Health check for a tokenized stock's price oracle on Robinhood Chain: verifies the latest round has a positive answer, valid round accounting, and an update timestamp inside the feed's 24-hour heartbeat window. Returns healthy, stale, or invalid, with every raw round value included. Checks that cannot be verified from official contracts report unsupported — never a silent pass.

## Output

Returns a health status of 'healthy', 'stale', or 'invalid', along with every raw round value (round ID, answer, started-at timestamp, updated-at timestamp). Any check that cannot be verified from official contracts is reported as 'unsupported' rather than silently passing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "symbol": {
   "type": "string",
   "description": "Ticker symbol, e.g. AAPL, NVDA, SPY (case-insensitive)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "round": {
   "age_seconds": 512,
   "heartbeat_seconds": 86400
  },
  "checks": {
   "freshness": "fresh",
   "round_valid": true,
   "sequencer_up": "unsupported",
   "answer_positive": true
  },
  "status": "healthy",
  "symbol": "NVDA"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robinhood-chain-oracle-health-check-2c053fa3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)