# Foundry USGS Earthquake Radius + Time Window Query > Foundry USGS Earthquake Radius + Time Window Query is a paid API for AI agents from foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14). Returns USGS earthquake catalog events within a geographic radius and time window, filtered by minimum magnitude, with source provenance and completeness evidence. ## Facts - Endpoint: POST https://foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/v2/official/usgs-radius-incident-window - 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/foundry-usgs-earthquake-radius-time-window-query-b7f753e6 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W0D2oVJQE67IXItZwygtl 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 foundry-usgs-earthquake-radius-time-window-query-b7f753e6 -d '' ``` Example prompt: Can you pull all USGS earthquakes within 150 km of Seattle (47.61, -122.33) between 2024-03-01T00:00:00Z and 2024-03-07T00:00:00Z with a minimum magnitude of 2.5, returning up to 20 events? ## When to prefer this Use this endpoint when you need official, source-attributed USGS earthquake records for a specific geographic area and time window — especially for evidence, audit, or verification use cases where provenance and completeness flags matter. Prefer it over generic web searches when you need structured JSON with explicit source metadata and public-domain licensing. It is bounded to a single spatial+temporal query per call. ## Known failure modes - Invalid date-time format (must be ISO 8601 UTC with Z suffix) returns validation error - radius_km of 0 or negative rejected by exclusiveMinimum constraint - latitude outside -90 to 90 or longitude outside -180 to 180 returns schema error - limit exceeding 20 rejected - No events in range returns empty events array with complete:true (not an error) - USGS upstream unavailability may cause delayed or failed responses - Payment not included or insufficient USDC returns 402 ## How this service works Pay-per-request evidence and data tools: CSV validation and reconciliation, DNS/email configuration evidence, and bounded official weather, earthquake, vehicle, company and study records. Exact USDC prices, explicit JSON contracts and source provenance. No mailbox, ownership, medical or safety guarantees. ## Output A JSON object containing the echoed query parameters, a list of earthquake events (each with USGS identifiers, magnitude, location, and time), a 'complete' boolean indicating whether the result was truncated, an evidence block with source URL, attribution, retrieval timestamp, cache age, and upstream call count, plus a limitations array and observed_at timestamp. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "limit": { "type": "integer", "default": 10, "maximum": 20, "minimum": 1 }, "end_time": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "latitude": { "type": "number", "maximum": 90, "minimum": -90 }, "longitude": { "type": "number", "maximum": 180, "minimum": -180 }, "radius_km": { "type": "number", "maximum": 2000, "exclusiveMinimum": 0 }, "start_time": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "minimum_magnitude": { "type": "number", "default": 0, "maximum": 10, "minimum": -2 } } } ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "route": "usgs-radius-incident-window", "result": { "query": { "limit": 10, "end_time": "2026-09-06T00:00:00Z", "latitude": 37.77, "longitude": -122.42, "radius_km": 100, "start_time": "2026-09-05T00:00:00Z", "minimum_magnitude": 0 }, "events": [], "complete": true, "evidence": { "source": "USGS Earthquake Catalog", "license": "US public-domain earthquake facts; no third-party media", "terms_url": "https://www.usgs.gov/information-policies-and-instructions/copyrights-and-credits", "source_url": "https://earthquake.usgs.gov/fdsnws/event/1/query", "attribution": "US Geological Survey and the contributing seismic network identified in each record", "retrieved_at": "2026-09-06T00:00:00Z", "upstream_calls": 1, "cache_age_seconds": 0, "source_generated_at": null }, "limitations": [ "Reported seismic observations may be revised; no emergency warning or impact prediction.", "Complete means the bounded source query was not truncated at retrieval; it does not guarantee all earthquakes are catalogued.", "Synthetic empty result only; no live observation claimed." ], "observed_at": "2026-09-06T00:00:00Z" }, "observed_at": "2026-09-06T00:00:00Z" } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-usgs-earthquake-radius-time-window-query-b7f753e6/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev](https://www.zero.xyz/host/foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/llms.txt)