# aye.today Earthquake Occurrence Check

> aye.today Earthquake Occurrence Check is a paid API for AI agents from api.aye.today, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns an attested aye/nay receipt confirming whether an earthquake at or above a specified magnitude occurred in a named region over a past time window, with cryptographic evidence sourced from USGS.

## Facts

- Endpoint: POST https://api.aye.today/v1/quake_check
- 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/aye-today-earthquake-occurrence-check-015aba4c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W37cm-f1VLulBHem1vv3S

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 aye-today-earthquake-occurrence-check-015aba4c -d '<json body>'
```

Example prompt: Did any earthquake at magnitude 5 or higher hit the US West Coast in the last 24 hours? Give me an attested receipt so I can use it as verifiable proof.

## When to prefer this

Choose this endpoint when you need a cryptographically attested, auditable record of whether an earthquake meeting specific criteria occurred — not just a raw data feed. It is ideal for parametric insurance triggers, automated compliance workflows, dispute resolution, or any use case where a signed aye/nay receipt with evidence hashes is required rather than a live data query. Prefer it over raw USGS API access when provenance and non-repudiation of the result matter.

## Known failure modes

- Unsupported region or magnitude enum value returns a validation error
- Unsupported hours_back value outside allowed enum returns error
- USGS feed unavailable may cause resolution failure or delayed response
- Near-threshold events may require revision-lifecycle handling, adding latency
- Payment of $0.01 USDC required per call; failure to pay returns 402

## How this service works

Attested resolution: did an earthquake at or above a magnitude threshold occur in a named region over a past window? Resolved from the USGS feed with revision-lifecycle handling (retracted events never count; near-threshold event ids + revision timestamps pinned). Evidence bundle with source payload hashes, capped by an aye/nay receipt — never a bare boolean.

## Output

An attested receipt (aye or nay) indicating whether a qualifying earthquake occurred, accompanied by an evidence bundle containing source payload hashes, relevant USGS event IDs, and revision timestamps. Retracted USGS events are excluded; near-threshold events are pinned with revision history to ensure integrity. Never returns a bare boolean.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aye-today-earthquake-occurrence-check-015aba4c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.aye.today](https://www.zero.xyz/host/api.aye.today/llms.txt)