# Natur Halowerk Earthquake Brief

> Natur Halowerk Earthquake Brief is a paid API for AI agents from natur.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Returns a single earthquake in decision-ready form — by USGS event ID or as the most significant matching event — including magnitude with its type (e.g. Mw, ML)

## Facts

- Endpoint: POST https://natur.halowerk.com/v1/earthquake-brief
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/natur-halowerk-earthquake-brief-d576ed20
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Qa9svVl4soBVud-Y1T0na

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 natur-halowerk-earthquake-brief-d576ed20 -d '<json body>'
```

Example prompt: What was the most significant earthquake in Japan in the past 7 days? Give me the magnitude with its magnitude type, depth, and exact location.

## When to prefer this

Choose this endpoint when you need a single, clean, decision-ready earthquake record — either by exact USGS event ID or as the top event from a search — and when correct magnitude type attribution (Mw vs ML) matters for downstream decisions. Prefer it over raw USGS API calls when you need a pre-digested, agent-friendly response without parsing complex GeoJSON. Less appropriate when you need a list of many earthquakes or want to cluster events (see the sibling clustering endpoint).

## Known failure modes

- Event ID not found — returns error if the specified USGS event identifier does not exist or has been removed
- No matching event — if search parameters yield no earthquakes, returns an empty or not-found response
- Ambiguous search — if search parameters match multiple events, returns only the most significant one (which may not be the intended event)
- Stale data — USGS catalog may have slight ingestion delays for very recent events
- Invalid parameters — malformed coordinates, dates, or magnitudes return a validation error

## How this service works

Returns a single earthquake in decision-ready form, either by its USGS event identifier or as the most significant event matching a search. Magnitude is reported with the magnitude type, because moment magnitude and local magnitude are not interchangeable at the edges of their ranges.

## Output

A single earthquake record in decision-ready form, including the event's magnitude (with its magnitude type such as Mw or ML), geographic location, depth, origin time, and USGS event identifier. The magnitude type is explicitly reported because moment magnitude and local magnitude are not interchangeable at the edges of their ranges.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hours": {
   "type": "integer",
   "default": 24,
   "maximum": 720,
   "minimum": 1,
   "description": "Search window when no event_id is given."
  },
  "event_id": {
   "type": "string",
   "maxLength": 40,
   "description": "USGS event id, e.g. us7000abcd. Without it the strongest recent event matching the filters is returned."
  },
  "min_magnitude": {
   "type": "number",
   "default": 5,
   "maximum": 10,
   "minimum": 0,
   "description": "Used only when no event_id is given."
  },
  "reference_lat": {
   "type": "number",
   "maximum": 90,
   "minimum": -90,
   "description": "Your location, to get distance and bearing."
  },
  "reference_lon": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/natur-halowerk-earthquake-brief-d576ed20/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from natur.halowerk.com](https://www.zero.xyz/host/natur.halowerk.com/llms.txt)