Weather APIs you can pay per call

What a weather API does, and who calls it

A weather API turns a place and a time into numbers a program can use: temperature, precipitation, wind, humidity, sometimes air quality, alerts or the state of the sea. You send a city name or a pair of coordinates, you get JSON back. Besides forecasting, the work can include geocoding the place, picking a model or station, and returning a clean structure instead of a raw grid.

On x402 the caller is often not a person. An AI agent planning a trip, a delivery or an outdoor event asks for the forecast in the middle of a task, pays a fraction of a cent for that single answer and moves on. No account, no API key, no monthly plan: the service answers the first call with HTTP 402 and a price, the agent signs a USDC payment, retries and gets the data. That is why the buyers we count are wallets, not companies: 19 of the 22 services had at least one paying wallet in the last 30 days.

Apps call these APIs too: a widget that shows today's weather, a dashboard for field teams, a bot that warns a farmer about frost. For them pay per call means the bill follows usage, which suits a small app or a prototype that does not want to commit to a plan before it knows its traffic.

Agents also trade on weather. A weather prediction market can settle on the temperature or rainfall read at one named station. An agent following that market needs to match its resolution rule with the station, date and units returned by the endpoint; a city forecast alone need not satisfy that rule.

What weather data the 22 services actually return

We classify the listed endpoint descriptions by what the weather calls return. The table counts services, not endpoints, and gives the cheapest matching endpoint; a service appears in more than one row when it sells more than one kind of data.

Each price is the cheapest endpoint of that service for that kind of data: the same number wherever this page quotes it.

Current conditions come from 15 services and multi-day forecasts from 9 services. For other kinds of weather data, historical weather comes from Vibe Springs, marine data from Vibe Springs, tropical cyclones from VWeatherStation. Air quality is sold by SuVerse Pay and AIMarket.

Coverage matters as much as the type of data. 7 services say they work anywhere on earth; 5 services sell endpoints that answer only for US places, Japan Weather Forecast & Warnings API lists Japanese weather and SENTINEL Compliance Intelligence lists Mauritius weather. Before you choose on price, check that the place your users ask about is covered.

The descriptions name these upstream sources. 6 services relay Open-Meteo, 5 services read the US National Weather Service or NOAA, ISHOB reads MET Norway and Japan Weather Forecast & Warnings API the Japan Meteorological Agency. A shared source does not establish identical answers: compare the model, station and timestamp as well as the packaging (geocoding by city name, decoded condition codes, decision flags, signed receipts) and the price.

The 22 weather APIs: what each one does and what its weather call costs

One row per service, most buyers first. Each service is priced on its plain weather call, and the table names that endpoint: a gateway that sells a cheap hash function next to a dearer weather call is priced here on the weather call.

$/CALL is the price of the endpoint named under it: the cheapest current conditions, daily forecast (days ahead) and hourly or short-range forecast endpoint of the service or, for a service without one, its cheapest weather endpoint. Never the cheapest tool of a gateway. Other kinds of data have their own price in the tables below. WEATHER ENDPOINTS counts the weather endpoints out of all the endpoints the service lists. BUYERS 30D counts distinct wallets that paid the whole service on-chain in 30 days, not only its weather endpoints. "Generalist" marks a gateway that sells more than three unrelated kinds of tools: it is never called the cheapest.

11 of the 22 are generalist gateways: hosts that sell weather tools alongside other products such as crypto prices, web search or sanctions checks. They are listed because their weather endpoint works and is paid, but we never call one of them the cheapest weather API. Check whether weather is a core product or a tool in a broader catalog before depending on its maintenance. We also left out 9 services that mention weather in their description but list no paid weather endpoint.

How to choose a weather API, criterion by criterion

Coverage first

A cheap answer for the wrong country is no answer. 7 services claim worldwide coverage; 5 services sell endpoints that answer only for US places, such as National Weather Service forecasts and alerts. Check coverage for the requested place and data type separately: an alert feed for the US does not establish that another endpoint on the same host covers Paris or Lagos.

Airport reports are the exception: METAR and TAF for any airport by ICAO code, in the US or elsewhere, come from Polyform.

Freshness of the data

Freshness is mostly the upstream's. Services that read station observations ("latest observed conditions", "nearest station") report what the station last sent; services that relay a forecast model update when that model runs.

x402 Factory says it adds a layer of its own: its endpoint description declares “our calibrated station model”. This is the service's claim, rather than a model we have evaluated.

We do not measure the age of the weather data itself. What we do measure is whether the service answers: each one is checked about every 15 minutes, and the date at the top of this page is the last time these numbers were refreshed.

Latency

The fastest service on this page answers in 86 ms on average (Datakoot), the slowest in 1430 ms (GISGP x402 Hazard API); each service's own figure is in the table above. For a chat agent that answers a person, anything under a second is invisible; for a pipeline that geocodes thousands of places it adds up, and a service that geocodes inside the call saves you a second request.

Uptime

The median 30-day uptime is 100%: 16 services were up at every check in 30 days, and the lowest on this page is AnT API — live market data for AI agents at 99.4%. The listing requires at least 90% uptime over 30 days.

Price

Weather calls cost from $0.001 to $0.2, median $0.01. The spread is not about quality: a relay of a public source at $0.001 and a settlement-station reading from $0.04 are different products. Compare prices inside the same job (the section "Which weather API for which job" below does it for you) and look at the price of the kind of data you will actually call: VWeatherStation charges $0.02 for current weather and from $0.04 for settlement readings.

Networks

All 22 services accept USDC on Base, 7 also on Solana, and 7 services accept more than one network; MicroTap and VWeatherStation accept 4. If your agent's wallet lives on one network, filter on it first: paying on another network means bridging.

Buyers

Buyers are distinct wallets that paid the service on-chain in the last 30 days. By buyer count, the top three account for 71% of the counts on this page (a wallet that paid two services counts in both). A service with zero buyers may be new rather than bad, but it has no track record with paying agents yet.

Which weather API for which job

Each job below lists the services whose endpoints do it, with the price of the matching endpoint. A generalist gateway is marked as such.

Current weather for an agent answer or an app widget

A common job: one call, one place, temperature, wind and precipitation now. Pick a service that takes a city name if your agent has no coordinates, and prefer one built for weather when you pay the same: a gateway can drop its weather tool without notice. Order below: most buyers first.

Candidates today, most buyers first: Hugen Weather API ($0.01/call, 312 buyers) · MicroTap ($0.01/call, generalist, 60 buyers) · Losbeto — LLM Gateway & Market Intelligence ($0.01/call, generalist, 32 buyers) · SuVerse Pay ($0.05/call, generalist, 28 buyers) · ISHOB ($0.001/call, generalist, 16 buyers) · AIMarket ($0.001/call, 16 buyers) · Polyform ($0.003/call, generalist, 11 buyers) · DYOE Agent Services ($0.01/call, generalist, 8 buyers) · Datakoot ($0.01/call, generalist, 7 buyers) · SENTINEL Compliance Intelligence ($0.001/call, generalist, 5 buyers) · AgentShop ($0.002/call, generalist, 2 buyers) · PitchPilot Outreach API ($0.001/call, generalist, 1 buyer) · x402.eleeth.com ($0.01/call, generalist, 1 buyer) · VWeatherStation ($0.02/call, 1 buyer) · AnT API — live market data for AI agents ($0.001/call)

Multi-day forecast for planning

Check the forecast horizon in the endpoint description against your planning date. A 3-day forecast may help with "pack an umbrella", but it cannot cover a site visit next week. Check whether the response provides daily summaries or a time series before choosing a candidate below.

Candidates today, most buyers first: Hugen Weather API ($0.01/call, 312 buyers) · Vibe Springs ($0.002/call, 140 buyers) · Losbeto — LLM Gateway & Market Intelligence ($0.01/call, generalist, 32 buyers) · Polyform ($0.003/call, generalist, 11 buyers) · DYOE Agent Services ($0.01/call, generalist, 8 buyers) · Datakoot ($0.01/call, generalist, 7 buyers) · AgentShop ($0.002/call, generalist, 2 buyers) · VWeatherStation ($0.02/call, 1 buyer) · Japan Weather Forecast & Warnings API ($0.005/call)

Hour by hour, or a precise time window

For "will it rain between 6 and 9 pm", check for an hourly series or a score for that time window. Check the endpoint description for the places it covers before you build on one, and confirm that its time zone and forecast horizon fit your request.

Candidates today, most buyers first: Losbeto — LLM Gateway & Market Intelligence ($0.01/call, generalist, 32 buyers) · x402 Factory ($0.01/call, 26 buyers) · ISHOB ($0.001/call, generalist, 16 buyers) · Polyform ($0.003/call, generalist, 11 buyers) · PitchPilot Outreach API ($0.001/call, generalist, 1 buyer)

Severe weather alerts and warnings

Check the coverage and issuer of an alert before acting on it. An endpoint may return an official warning, a travel disruption signal or a derived risk flag; those are different inputs to a decision. If you need an official warning, require the issuing authority, affected area and validity period in the response.

Candidates today, most buyers first: Polyform ($0.003/call, generalist, 11 buyers) · ForgeMesh Travel Agent ($0.01/call, 8 buyers) · Datakoot ($0.01/call, generalist, 7 buyers) · Japan Weather Forecast & Warnings API ($0.005/call) · GISGP x402 Hazard API ($0.2/call)

Air quality

Check which pollutant measurements and AQI scale the endpoint describes: an air quality index alone does not promise PM2.5 and PM10 concentrations. Confirm the location, units and observation time your application needs, then compare the matching per-call prices below before you wire one in.

Candidates today, most buyers first: SuVerse Pay ($0.055/call, generalist, 28 buyers) · AIMarket ($0.001/call, 16 buyers)

Prediction-market settlement and temperature odds

Match the endpoint to the market resolution rule: a station reading, a threshold probability and a change-of-bucket alert serve different purposes. Check the named station, time window and units; a general forecast for the city need not be the number that settles the bet.

Candidates today, most buyers first: LoneStarOracle WeatherOracle ($0.02/call, 39 buyers) · Isocast ($0.1/call, 12 buyers) · VWeatherStation ($0.04/call, 1 buyer)

Go/no-go decisions: travel, drones, routes, airports

Before using a go/no-go flag or risk score, check the endpoint description for its inputs, coverage, thresholds and validity period. An active alert, a forecast and a long-term hazard indicator answer different questions. Choose an input and decision rule that fit the action you are automating.

Candidates today, most buyers first: x402 Factory ($0.02/call, 26 buyers) · ISHOB ($0.001/call, generalist, 16 buyers) · Polyform ($0.03/call, generalist, 11 buyers) · ForgeMesh Travel Agent ($0.03/call, 8 buyers) · VWeatherStation ($0.01/call, 1 buyer) · GISGP x402 Hazard API ($0.2/call)

History, floods and the sea

For past weather, river discharge or marine conditions, compare the matching endpoints below. The candidates come from the descriptions in our current listing.

Candidates today, most buyers first: Vibe Springs ($0.002/call, 140 buyers)

The main weather services, one by one

Selected services with different weather products, ordered for a closer look at their descriptions and endpoints. Endpoints and sources are as each service describes them on x402-list; prices, uptime, latency and buyers are our measurements.

Hugen Weather API

With 312 paying wallets in the last 30 days, it is the most used weather API on x402-list as of October 26, 2026. It does one thing: you pass a city name or coordinates and get either current conditions (GET /weather/current: temperature, feels-like, humidity, wind, precipitation, condition) or a daily forecast for 1 to 7 days (GET /weather/forecast: highs, lows, precipitation amount and probability, peak wind). Geocoding happens inside the call, which suits agents that only have a city name in the prompt. Current weather costs $0.01 per call and the forecast $0.01, payable in USDC on Base and Solana; 30-day uptime is 100% and the average response time we measure is 608 ms.

2 weather endpoints of 2 · $0.01/call (GET /weather/current) · Base/SOL · uptime 30d 100% · 608 ms · 312 buyers in 30 days

Vibe Springs

A data host offering a 16-day forecast (/api/forecast), historical weather (/api/weather), marine conditions with wave heights and swell (/api/marine) and river discharge for flood risk (/api/flood). The forecast costs $0.002 per call, history $0.002, marine data $0.002 and flood data $0.002, on Base. The same host also sells exchange rates and on-chain risk: 4 of its 10 endpoints are weather. It answers in 178 ms on average, has 99.9% uptime over 30 days and 140 buyers.

4 weather endpoints of 10 · $0.002/call (GET /api/forecast) · Base · uptime 30d 99.9% · 178 ms · 140 buyers in 30 days

LoneStarOracle WeatherOracle

For US cities it returns an ensemble high-temperature forecast from the GFS and ECMWF models, the spread between models and the chance that the high exceeds a threshold, the shape a prediction-market agent needs. One endpoint, GET /forecast, at $0.02 per call on Base and Solana. Its average response time is 1012 ms; 39 wallets paid it in 30 days, with 100% uptime.

1 weather endpoint of 1 · $0.02/call (GET /forecast) · Base/SOL · uptime 30d 100% · 1012 ms · 39 buyers in 30 days

x402 Factory

Answers narrow questions rather than returning a full forecast: "will it rain during my event" for Chicago, Denver, Detroit and Houston (/v1/forecast/<city>/window), hourly forecasts up to 168 hours for Philadelphia, San Antonio and San Diego built on National Weather Service data, and weather-driven delay risk for the top 100 US airports in 6-hour blocks. Hourly and event-window forecasts start at $0.01 per call, airport delay risk costs $0.02. Its other endpoints are economic series and filings: 9 of 25 are weather. 26 buyers in 30 days, 100% uptime, 151 ms.

9 weather endpoints of 25 · $0.01/call (GET /v1/forecast/philadelphia) · Base · uptime 30d 100% · 151 ms · 26 buyers in 30 days

Polyform

A generalist gateway with weather tools from the National Weather Service and NOAA: latest observed conditions, a 7-day forecast, an hour-by-hour forecast for 48 hours and active alerts for US places, plus raw and decoded METAR and TAF for any airport by ICAO code. Current conditions cost from $0.003 per call, the forecast $0.003, alerts $0.003, METAR and TAF $0.003. Two bundles sit on top, also for US places: a location brief with address, conditions and alerts, and a severe-weather scan with a CLEAR to AVOID verdict at $0.03. 11 buyers, 100% uptime, 133 ms.

7 weather endpoints of 50 · $0.003/call (GET /v1/weather/current) · Base · uptime 30d 100% · 133 ms · 11 buyers in 30 days

AIMarket

Current weather (/x402/weather-now) and current air quality with PM2.5, PM10 and US and European AQI (/x402/air-quality-now) cost $0.001 and $0.001 per call, and the description advertises signed receipts, useful when an agent has to prove where a number came from. A third endpoint returns the nearest live public sensors to a point. It reads weather from the nearest Open-Meteo relay within 75 km and air quality from Copernicus CAMS. 16 buyers, 99.6% uptime, 366 ms.

3 weather endpoints of 6 · $0.001/call (POST /x402/weather-now) · Base · uptime 30d 99.6% · 366 ms · 16 buyers in 30 days

VWeatherStation

Two families of endpoints. General weather, current plus 7 days for any coordinate, at $0.02; and settlement data from $0.04: temperature, rain, snow and wind read at the exact stations Polymarket and Kalshi weather markets resolve on, plus active hurricanes from the National Hurricane Center, a multi-model confidence score and route risk. 9 of its 9 endpoints match the weather task; it accepts Arbitrum, Base, Polygon and Solana, and it has had 1 buyer in 30 days so far.

9 weather endpoints of 9 · $0.02/call (GET /v1/weather) · ARB/Base/POL/SOL · uptime 30d 100% · 328 ms · 1 buyer in 30 days

Japan Weather Forecast & Warnings API

Built on the Japan Meteorological Agency (気象庁): a regional forecast with a 7-day outlook, the official narrative weather discussion with an English summary, and active warnings and advisories (heavy rain, storm, snow, flood, storm surge), the forecast at $0.005 per call and the warnings at $0.005, plus a batch call for up to 50 regions priced by item count. Uptime 100%, 372 ms, networks Base, Polygon and Solana; 0 paying wallets in the last 30 days.

4 weather endpoints of 5 · $0.005/call (GET /forecast/{area_code}) · Base/POL/SOL · uptime 30d 100% · 372 ms · 0 buyers in 30 days

Pay per call or subscribe: what 1,000 and 100,000 weather calls cost

A subscription weather API bills a monthly plan whether you use it or not, and usually asks for an account and a key per project. An x402 weather API bills each call, settles it on-chain in USDC and needs neither. Compare the price at your expected volume, so here is the pay-per-call side at the prices we measured today.

Each service at the price of its main weather endpoint, the one named in the table above.

At the median price, 1,000 calls cost $10.00 and 100,000 calls cost $1,000.00. At AIMarket, the cheapest specialized service, the same 100,000 calls cost $100.00. For an agent that checks the weather a few hundred times a month, pay per call is a rounding error; at millions of calls a month, compare these figures with the monthly fee of a plan that covers your volume.

Two things are not in the table. The network fee of each payment is usually paid by the facilitator that settles it, not by the buyer; check the terms of yours. And whether a failed call is charged depends on when the service settles: Datakoot, for example, states it charges only on success. Read the description before you build retries.

A real call: the 402 a weather API answers, and how to pay it

This is what an unpaid call to Hugen Weather API for the current weather in Tokyo gets back: HTTP 402 Payment Required and the terms of payment. The body below is the one our monitor stored on its last check, not a mock-up.

curl -i 'https://weather.hugen.tokyo/weather/current?city=Tokyo'

HTTP/1.1 402 Payment Required

{
  "x402Version": 2,
  "resource": {
    "url": "https://weather.hugen.tokyo/weather/current"
  },
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x29322Ea7EcB34aA6164cb2ddeB9CE650902E4f60",
      "amount": "10000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    },
    {
      "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
      "extra": {
        "feePayer": "BENrLoUbndxoNMUS5JXApGMtNykLjFXXixMtpDwDR9SP"
      },
      "payTo": "4du4AfkjJEwch2zk3shkPJVZfyJHNDnNjEWC6AboaS5Z",
      "amount": "10000",
      "scheme": "exact",
      "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
      "maxTimeoutSeconds": 300
    }
  ]
}

402 of Hugen Weather API for GET /weather/current, as stored by the monitor (terms unchanged since 2026-07-20, last check 2026-10-26 15:50 UTC), with every accepted payment exactly as stored and without error, extensions, resource.mimeType and resource.description, which are not payment terms: the full body is also on the service page, under Payment evidence. Amounts are in the asset's smallest unit: USDC has 6 decimals, so 10000 is $0.01.

To get the weather instead of the 402:

• Read the terms: each entry of the payment requirements gives a network, an asset (USDC), the amount in the asset's smallest unit and the address that gets paid.
• Pick the entry on a network your wallet holds USDC on: this service accepts Base and Solana.
• Sign the payment with an x402 client (the official SDKs wrap fetch and axios) and retry the same request with the signed payload in the payment header.
• The service checks the payment through its facilitator, settles it and returns the weather JSON with a receipt of the settlement in the response headers.

An x402 client can automate the payment exchange once a wallet is configured: the call above costs $0.01, with no key and no sign-up.

How we measure

Every number on this page comes from x402-list's own monitoring or from the chain, and is refreshed when the page is built.

• Price: the current price of each weather endpoint, read from the 402 the service returns; we take the cheapest endpoint that returns weather data, and leave out endpoints whose price varies by request.
• Uptime 30d: successful checks divided by all checks over the last 30 days, with a check about every 15 minutes.
• Latency: the average response time of those checks, from our servers; your agent's network will add its own.
• Buyers 30d: distinct wallets that paid the service on-chain in the last 30 days. A measured floor: payments we cannot attribute to the service are not counted.
• What each service does: written from the service's own description and endpoint list. We read the endpoints, we do not test the accuracy of the forecasts.

A service is listed only if it is online, answers with a valid 402, has at least 90% uptime over 30 days and a known price. The method is public on the methodology page, and the data of this page is free to reuse under CC BY 4.0 from its JSON twin.

Questions

How to pay

Each service answers an unpaid call with HTTP 402 and its price; your agent signs a USDC payment on the listed network and retries. No API key, no account, no subscription. See what x402 is.