# Foundry NWS Alert Interval Relevance

> Foundry NWS Alert Interval Relevance 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).

Checks whether any active NWS weather alerts overlap a given geographic point and time window, returning matched alert counts and source provenance.

## Facts

- Endpoint: POST https://foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/v2/official/nws-alert-interval-relevance
- 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-nws-alert-interval-relevance-5324e646
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c2P6q0yAxcCc5QgN3Dw7J

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-nws-alert-interval-relevance-5324e646 -d '<json body>'
```

Example prompt: Are there any active NWS weather alerts near latitude 40.71, longitude -74.01 between 2025-07-15T14:00:00Z and 2025-07-15T22:00:00Z? Give me the matched alert count and any source attribution.

## When to prefer this

Use this endpoint when you need official, source-attributed NWS weather alert coverage for a specific geographic point and time interval — particularly for go/no-go decisions, event safety checks, or audit trails requiring explicit provenance. Prefer this over generic weather APIs when you need the raw alert match count, limitation disclosures, and NOAA attribution in a structured JSON contract. Not suitable for historical alert archives or future forecast alerts beyond what NWS currently exposes as active.

## Known failure modes

- Invalid or out-of-range latitude/longitude returns a validation error
- Malformed ISO 8601 datetime strings rejected by the pattern validator
- NWS upstream API unavailability may result in empty or stale responses
- No alerts returned does not confirm safe conditions — stated explicitly in limitations
- Time window outside current NWS active alert horizon returns empty results with historical_coverage: NOT_AN_ARCHIVE
- Missing temporal fields in NWS alerts result in UNKNOWN status counts rather than definitive matches

## 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 list of currently active NWS alerts matched to the point and window (may be empty), the count of matched/examined/unknown alerts, a flag indicating whether results were truncated, the requested time window echoed back, source metadata including the NWS API URL and retrieval timestamp, and a list of data limitations (e.g. no historical archive coverage, no independent geometry guarantee).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "end": {
   "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|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
  },
  "start": {
   "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|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "route": "nws-alert-interval-relevance",
  "result": {
   "alerts": [],
   "source": {
    "url": "https://api.weather.gov",
    "terms_url": "https://www.weather.gov/disclaimer",
    "updated_at": null,
    "attribution": "NOAA / National Weather Service; normalized by Foundry; no endorsement",
    "retrieved_at": "2026-09-06T00:00:00Z",
    "cache_age_seconds": 0
   },
   "truncated": false,
   "limitations": [
    "Only alerts currently returned by the NWS active point filter are examined. This is not historical or future alert coverage.",
    "Point relevance is delegated to the official NWS point filter; no independent geometry guarantee is made.",
    "Missing temporal fields remain UNKNOWN; no alerts does not establish safe conditions."
   ],
   "matched_count": 0,
   "unknown_count": 0,
   "examined_count": 0,
   "requested_window": {
    "end": "2026-09-07T12:00:00Z",
    "start": "2026-09-07T00:00:00Z"
   },
   "historical_coverage": "NOT_AN_ARCHIVE"
  },
  "observed_at": "2026-09-06T00:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-nws-alert-interval-relevance-5324e646/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)