# Earthquake Entity Detail Lookup

> Earthquake Entity Detail Lookup is a paid API for AI agents from oracles-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns stored detail for a single earthquake event by entityId (e.g. 'quake:us7000...'), or lists all tracked earthquake entities when no ID is provided.

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/earthquakes-all/status
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/earthquake-entity-detail-lookup-e0d40a95
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k4hPass8zMsSSgkSh6PbM

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 earthquake-entity-detail-lookup-e0d40a95
```

Example prompt: Pull up the full stored details for earthquake quake:us7000nxl4 — I want to see its magnitude, location, and any other data you have on it.

## When to prefer this

Use this endpoint when you already have a specific earthquake entityId (e.g. from a listing or digest endpoint) and need full structured detail for that event. Prefer this over the LLM digest endpoints when you need raw, machine-readable data rather than a narrative summary. Use the list mode (no ID) to enumerate all currently tracked earthquake entities.

## Known failure modes

- Invalid or malformed entityId returns empty or error response
- EntityId not found in stored data returns null or 404-style response
- Omitting the 'id' query param returns a list instead of a specific record
- Payment failure (x402) blocks access entirely
- Network timeout on Railway-hosted service

## How this service works

Stored detail for a single earthquake (entityId like 'quake:us7000...').

## Output

Returns a JSON object containing the stored entity record for the specified earthquake, including fields such as magnitude, location, time, and other event metadata. If no ID is provided, returns a list of all tracked earthquake entity IDs.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string",
       "description": "entityId to look up; omit to list tracked entities"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "entity": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/earthquake-entity-detail-lookup-e0d40a95/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oracles-production.up.railway.app](https://www.zero.xyz/host/oracles-production.up.railway.app/llms.txt)