# Earthquake Significant Event Detail Lookup

> Earthquake Significant Event 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).

Retrieves stored details for a single significant earthquake event by its entity ID, or lists all tracked earthquake entities.

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/earthquakes-significant/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-significant-event-detail-lookup-538bb5c4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_df9EmHTAb33lBcSyFnUqr

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-significant-event-detail-lookup-538bb5c4
```

Example prompt: Pull up the stored details for earthquake entity quake:us7000nph5 — I want to see the full record for that significant event.

## When to prefer this

Use this endpoint when you have a specific earthquake entity ID (in the format quake:us7000...) and need the full stored detail record for that event. Prefer this over the digest or list endpoints when you need structured data for a single known event rather than a narrative summary or a broad recent list.

## Known failure modes

- Entity ID not found — returns empty or 404-like response if the quake:us7000... ID does not exist in the store
- Missing or malformed entity ID format — unexpected string format may yield no results
- Payment failure — x402 payment of $0.01 USDC required; unpaid requests will be rejected
- Service unavailable — Railway.app hosting may experience downtime

## How this service works

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

## Output

Returns a JSON object containing the stored entity details for the requested earthquake, including fields like magnitude, location, depth, time, and other event metadata. If no ID is provided, returns a list of all tracked significant earthquake entities.

## 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-significant-event-detail-lookup-538bb5c4/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)