# Invoket Climate Point Batch

> Invoket Climate Point Batch 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).

Returns historical or current weather data (temperature, precipitation, wind) for multiple geographic coordinates in a single batch call, paid per-call in USDC stablecoin with no account required.

## Facts

- Endpoint: POST https://api.invoket.com/climate/point/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-climate-point-batch-9ea24447
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jp0IJFB1RI0KGbWuQMlQb

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-climate-point-batch-9ea24447 -d '<json body>'
```

Example prompt: Can you pull the temperature, precipitation, and wind conditions for these five locations — (40.71, -74.00), (34.05, -118.24), (51.51, -0.13), (48.85, 2.35), (35.68, 139.69) — for yesterday?

## When to prefer this

Choose this endpoint when you need to look up climate observations for multiple geographic coordinates in one call, especially in autonomous agent or pipeline contexts where no account or API key setup is feasible and USDC micropayment per-call billing is acceptable. Ideal for batch enrichment workflows where weather data is needed for many points simultaneously.

## Known failure modes

- Invalid or out-of-range latitude/longitude values causing a 400 error
- Date out of supported historical range returning empty or partial results
- Coverage incomplete flag set to false when no grid data is available for a point
- Payment failure or insufficient USDC balance causing a 402 response
- Malformed request body causing a 422 validation error
- Rate limiting or upstream data source unavailability causing 503

## How this service works

Before your agent backtests parametric triggers over a site portfolio, verifies claims across parcels or scores weather exposure for an asset fleet: daily 2 m temperature, total precipitation and 10 m wind for up to 500 point/date queries in one call, from the Copernicus ERA5 reanalysis (temperature and precipitation: rolling 30-year window; wind: rolling ~5-year window). Each query takes lat+lon or a city name; an uncovered item is flagged via per-item coverage instead of failing the batch.

## Output

A JSON object containing a results array with one entry per coordinate point, each including the matched grid point, temperature in Celsius, total precipitation in mm, wind speed in m/s and direction in degrees, a coverage completeness flag, and provenance metadata showing the data source and freshness timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "queries"
 ],
 "properties": {
  "queries": {
   "type": "array",
   "description": "Array of point/date queries resolved in one call. 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 a date (YYYY-MM-DD) within the ingested ERA5 window (rolling 30 years for temperature and precipitation, rolling ~5 years for wind)."
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-climate-point-batch-9ea24447/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)