# Invoket Climate Point Lookup

> Invoket Climate Point Lookup is a paid API for AI agents from api.invoket.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-16).

Returns temperature, precipitation, and wind data for a specific geographic coordinate and date via stablecoin pay-per-call

## Facts

- Endpoint: POST https://api.invoket.com/climate/point
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-climate-point-lookup-ccf43b9e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_viiCo4-Vz5vv9Vw0GHDsP

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-lookup-ccf43b9e -d '<json body>'
```

Example prompt: What was the temperature, precipitation, and wind at latitude 48.8566 and longitude 2.3522 on 2024-06-15?

## When to prefer this

Choose this endpoint when you need point-level climate data (temperature, precipitation, wind) for a specific lat/lon and date without requiring an account or API key, and when your agent can pay per call in USDC via the x402 protocol. Ideal for autonomous agents that need on-demand, low-cost weather lookups billed in stablecoin with no subscription overhead.

## Known failure modes

- Invalid or out-of-range latitude/longitude returns an error
- Date outside available data range returns no coverage or error
- Missing required parameters returns a 400-level error
- Payment failure (insufficient USDC) returns HTTP 402
- Coverage incomplete flag set to false when data is partial for that point

## How this service works

The checks your agent runs before it acts: verify a bank account, a phone number, a law in force, the weather or a vehicle — computed from official sources, with provenance in every response. You only pay for answers.

## Output

Returns a JSON object containing temperature in Celsius, total precipitation in mm, wind speed in m/s and direction in degrees, the nearest grid point coordinates and its distance, coverage completeness flag, and data provenance including source, freshness kind, as-of timestamp, and fetch time.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "city",
  "date"
 ],
 "properties": {
  "city": {
   "type": "string",
   "description": "City or place name, resolved against the embedded GeoNames cities500 gazetteer: exact name match (case- and accent-insensitive, no fuzzy matching), ties broken by population (most populous wins). Alias: location. Narrow with country=<ISO 3166 alpha-2>. Alternative: pass lat + lon directly instead. The resolved place is echoed back as data.location."
  },
  "date": {
   "type": "string",
   "description": "Calendar day (YYYY-MM-DD) within the ingested ERA5 window: rolling 30 years for temperature and precipitation, rolling ~5 years for wind (a deep date returns the covered families and flags the rest via coverage); a date outside the widest window returns 400 with the covered range"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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