# Foundry USGS Asset-Incident Composite

> Foundry USGS Asset-Incident Composite is a paid API for AI agents from foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev, paid per call via x402, $0.009/call, status unknown (last checked 2026-09-14).

For a set of geographic asset locations, queries USGS earthquake catalog data within a given radius and time window and returns which seismic events are near each asset.

## Facts

- Endpoint: POST https://foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/v2/official/usgs-asset-incident-composite
- Price: $0.009/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-asset-incident-composite-ec4cf2d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sCnJjoyh17C_OuhkZ2UTu

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-asset-incident-composite-ec4cf2d9 -d '<json body>'
```

Example prompt: Check if any earthquakes of magnitude 3.0 or greater were recorded within 200km of my two warehouses — warehouse-alpha at 37.77°N, 122.42°W and warehouse-beta at 37.33°N, 121.89°W — between 2024-01-01T00:00:00Z and 2024-01-31T23:59:59Z, and tell me how many events matched each site.

## When to prefer this

Use this endpoint when you need to correlate multiple named geographic asset locations against the official USGS earthquake catalog for a bounded time window, and you want per-asset match summaries with full source provenance. Prefer it over generic earthquake APIs when you need explicit evidence metadata, source attribution, and asset-incident pairing in a single call. It is particularly well-suited for risk assessment, insurance, facility management, and compliance workflows that require auditable, official seismic records rather than third-party aggregations.

## Known failure modes

- Invalid datetime format in start_time or end_time returns a validation error
- radius_km of 0 or negative is rejected (exclusiveMinimum: 0)
- Fewer than 2 or more than 5 assets in the assets array causes a schema validation error
- Asset ID not matching pattern ^[A-Za-z0-9_-]{1,40}$ is rejected
- latitude/longitude values outside valid range (-90 to 90, -180 to 180) are rejected
- limit exceeding 20 is clamped or rejected
- Payment failure (insufficient USDC) returns HTTP 402
- USGS upstream unavailability may cause incomplete results flagged in the response

## 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 list of input assets with their coordinates; per-asset summaries (matched event count, completeness status); asset-event pairs listing which specific earthquakes were near each asset; the raw USGS query parameters used; source evidence metadata (source name, license, terms URL, retrieval timestamp, cache age); and a set of limitations disclaimers about data completeness and no emergency/safety guarantees.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "default": 20,
   "maximum": 20,
   "minimum": 1
  },
  "assets": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "latitude",
     "longitude"
    ],
    "properties": {
     "id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,40}$"
     },
     "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90
     },
     "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180
     }
    },
    "additionalProperties": false
   },
   "maxItems": 5,
   "minItems": 2
  },
  "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))$"
  },
  "radius_km": {
   "type": "number",
   "maximum": 500,
   "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-asset-incident-composite",
  "result": {
   "pairs": [],
   "assets": [
    {
     "id": "warehouse-a",
     "latitude": 37.77,
     "longitude": -122.42
    },
    {
     "id": "warehouse-b",
     "latitude": 37.33,
     "longitude": -121.89
    }
   ],
   "current": {
    "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"
   },
   "radius_km": 100,
   "limitations": [
    "Synthetic empty example; no actual asset exposure observation."
   ],
   "observed_at": "2026-09-06T00:00:00Z",
   "asset_summaries": [
    {
     "status": "NONE_OBSERVED_COMPLETE",
     "asset_id": "warehouse-a",
     "matched_events": 0,
     "pair_list_complete": true
    },
    {
     "status": "NONE_OBSERVED_COMPLETE",
     "asset_id": "warehouse-b",
     "matched_events": 0,
     "pair_list_complete": true
    }
   ],
   "distance_method": "SPHERICAL_HAVERSINE_R6371.0088_KM",
   "unlocated_event_ids": []
  },
  "observed_at": "2026-09-06T00:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-usgs-asset-incident-composite-ec4cf2d9/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)