# Invoket Batch Weather Forecast

> Invoket Batch Weather Forecast is a paid API for AI agents from api.invoket.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Fetches weather forecasts for multiple locations in a single request, resolved from official sources with provenance included in every response.

## Facts

- Endpoint: POST https://api.invoket.com/weather/forecast/batch
- 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/invoket-batch-weather-forecast-faef2809
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qR-t8v_rqdvKM-s96PM2f

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 invoket-batch-weather-forecast-faef2809 -d '<json body>'
```

Example prompt: Can you get me the current weather forecast for New York, London, Tokyo, and Sydney all at once — I need it with source provenance included so I know where the data came from?

## When to prefer this

Prefer this endpoint when an AI agent needs weather forecasts for multiple locations simultaneously and requires provenance on each result for audit or verification purposes. It is especially suited for pre-action checks where a single settlement covers all queries cost-efficiently (one flat fee up to 500 locations). Choose it over single-location APIs when batching is needed, and over generic weather APIs when source attribution is required.

## Known failure modes

- Batch size exceeds 500 queries — returns HTTP 400 rejection
- Invalid or unresolvable location (bad lat/lon or unknown city name) — individual query may fail or return null
- Unparseable lead-time selector — query item rejected
- Payment not settled via x402 — request not processed
- Upstream official weather source unavailable — may return partial results or error

## How this service works

Before your agent plans across a whole network — fleet routing, multi-site operations, portfolio hedging: 2 m temperature, precipitation and 10 m wind forecasts for up to 500 point + lead-time queries in one call, from the deterministic NOAA GFS run (~16 days). Each query takes lat+lon or a city name plus an optional lead selector (omitted, it defaults to the current analysis time); an uncovered item is flagged via per-item coverage instead of failing the batch.

## Output

An object containing weather forecast data for each queried location, including conditions, temperatures, and lead-time forecasts, along with provenance metadata indicating the official source used for each result.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "queries"
 ],
 "properties": {
  "queries": {
   "type": "array",
   "description": "Array of point/lead-time queries resolved in one settlement. Its length is priced per unit (base + N x unit), capped at 500; a batch over 500 is rejected with 400. Each item takes a point (lat + lon, or a city name) and at most one lead selector (omitted = current analysis time)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-batch-weather-forecast-faef2809/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.invoket.com](https://www.zero.xyz/host/api.invoket.com/llms.txt)