# Foundry Earthquake Incident Comparison

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

Compares a caller-supplied earthquake record against the current USGS Catalog entry for the same event ID and returns field-level diff results with full source provenance.

## Facts

- Endpoint: POST https://foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/v2/official/earthquake-incident-comparison
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-earthquake-incident-comparison-0f060a51
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4gTIFukWgbUOjTvFUDyaz

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-earthquake-incident-comparison-0f060a51 -d '<json body>'
```

Example prompt: I have a cached record for USGS earthquake event us7000m9g4 showing magnitude 6.2, coordinates [-118.3, 34.1, 10.0], status 'reviewed', and event time '2025-03-15T08:22:00Z' — can you compare those against the current official USGS entry and tell me which fields have changed?

## When to prefer this

Choose this endpoint when you need to verify or audit a previously stored earthquake record against the authoritative USGS Earthquake Catalog with explicit field-level diff output and full source provenance. It is purpose-built for reconciliation workflows, change detection pipelines, and fact-checking scenarios where you have a prior snapshot of a specific event ID and want to know exactly which fields have changed. Prefer this over a raw USGS lookup when you need structured comparison results rather than just raw retrieval, and over generic data-diffing tools when USGS attribution and licensing provenance are required.

## Known failure modes

- Invalid event_id format (must be alphanumeric, 1–40 chars) returns a validation error
- USGS event ID not found in the catalog returns null current values with UNKNOWN comparison statuses
- USGS catalog temporarily unavailable returns a service error or degraded response
- Previous field values outside allowed numeric ranges (e.g. magnitude > 15) are rejected at schema validation
- Stale cache (up to 30 seconds) may cause a brief lag between an upstream revision and the returned current value

## 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

Returns a JSON object containing the current USGS values for magnitude, coordinates, status, and eventTime alongside a per-field comparison array where each field is labeled MATCH, MISMATCH, or UNKNOWN. Includes full source provenance (USGS attribution, terms URL, license), freshness metadata (retrieval timestamp, cache age), and upstream source URL.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "event_id": {
   "type": "string",
   "pattern": "^[a-zA-Z0-9]{1,40}$"
  },
  "previous": {
   "type": "object",
   "required": [
    "magnitude",
    "coordinates",
    "status",
    "eventTime"
   ],
   "properties": {
    "status": {
     "anyOf": [
      {
       "type": "string",
       "maxLength": 200
      },
      {
       "type": "null"
      }
     ]
    },
    "eventTime": {
     "anyOf": [
      {
       "type": "string",
       "maxLength": 200
      },
      {
       "type": "null"
      }
     ]
    },
    "magnitude": {
     "anyOf": [
      {
       "type": "number",
       "maximum": 15,
       "minimum": -10
      },
      {
       "type": "null"
      }
     ]
    },
    "coordinates": {
     "anyOf": [
      {
       "type": "array",
       "items": false,
       "maxItems": 3,
       "minItems": 3,
       "prefixItems": [
        {
         "type": "number",
         "maximum": 180,
         "minimum": -180
        },
        {
         "type": "number",
         "maximum": 90,
         "minimum": -90
        },
        {
         "type": "number",
         "maximum": 1000,
         "minimum": -100
        }
       ]
      },
      {
       "type": "null"
      }
     ]
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "route": "earthquake-incident-comparison",
  "result": {
   "current": {
    "status": null,
    "eventTime": null,
    "magnitude": null,
    "coordinates": null
   },
   "event_id": "illustrative",
   "evidence": {
    "query": {
     "event_id": "us7000m9g4"
    },
    "source": "USGS Earthquake Catalog",
    "freshness": {
     "state": "CURRENT_RETRIEVAL",
     "retrievedAt": "2026-09-06T00:00:00Z",
     "cacheAgeSeconds": 0,
     "maximumCacheSeconds": 30,
     "recordAgeIsNotRetrievalAge": true
    },
    "sourceUrl": "https://earthquake.usgs.gov",
    "observedAt": "2026-09-06T00:00:00Z",
    "provenance": {
     "license": "US public-domain earthquake facts; no third-party media",
     "termsUrl": "https://www.usgs.gov/information-policies-and-instructions/copyrights-and-credits",
     "truncated": false,
     "attribution": "US Geological Survey and the contributing seismic network identified in each record",
     "limitations": [
      "Synthetic example only; identifiers and null values illustrate fields, not a live observation."
     ],
     "modifications": "Selected factual fields, normalized names and bounded result count; no source ownership claimed.",
     "upstreamCalls": 1,
     "documentationUrl": "https://earthquake.usgs.gov/fdsnws/event/1/"
    },
    "sourceUpdatedAt": null,
    "normalizedResult": [
     {
      "id": "illustrative-record",
      "place": null,
      "status": null,
      "network": null,
      "eventTime": null,
      "magnitude": null,
      "sourceUrl": null,
      "updatedAt": null,
      "coordinates": null
     }
    ],
    "sourceProcessedAt": null,
    "rawSourceIdentifiers": []
   },
   "observedAt": "2026-09-06T00:00:00Z",
   "comparisons": [
    {
     "field": "magnitude",
     "status": "UNKNOWN"
    },
    {
     "field": "coordinates",
     "status": "UNKNOWN"
    },
    {
     "field": "status",
     "status": "UNKNOWN"
    },
    {
     "field": "eventTime",
     "status": "UNKNOWN"
    }
   ],
   "limitations": [
    "Synthetic example only."
   ]
  },
  "observed_at": "2026-09-06T00:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-earthquake-incident-comparison-0f060a51/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)
