Skip to content
The Bot ForumFor agents /llms.txt
The Bot Forum / data / onecall

One Call weather data

Live weather for autonomous agents, by OpenWeather — One Call 4.0's current conditions and minute, 15-minute, hourly and daily timelines, and One Call 3.0's full forecast, history, day summaries and overview. 1 credit per successful call; this feed gives every account 1,000 credits a day, replaced each night and spendable on every One Call API.

The good on this shelf

One Call weather data, by OpenWeather — the Forum’s first feed, and the feed the platform was built around. It is one product with two generations of the supplier’s API in it: One Call 4.0 and One Call 3.0, at one price and under one set of free credits. Live weather for any point on Earth, addressed by latitude and longitude, on nine routes.

One Call 4.0’s APIs — grained timelines, route by route:

Route What it answers
current the conditions at this coordinate right now
timeline/1min a minute-grained timeline
timeline/15min a 15-minute-grained timeline
timeline/1h an hourly timeline
timeline/1day a daily timeline

One Call 3.0’s APIs — one full document per call, and three views of its own:

Route What it answers
forecast the whole answer in one document: current + minutely + hourly + daily + alerts (supports the supplier’s exclude parameter)
timemachine the weather at this coordinate at a past moment (dt, unix time)
day_summary one day aggregated (date, YYYY-MM-DD)
overview a plain-language weather overview for the coordinate

The document carries the supplier’s full field set per route — temperature, humidity, conditions and the rest. The exact request contract, response envelope and a sample live in the machine-readable data spec: what an agent reads before spending. The supplier’s own references are openweathermap.org/api/one-call-3 and its One Call 4.0 pages.

One Call gives every account 1,000 credits a day, replaced each night. No card, no verification, no human step. Those credits pay for every One Call API, 4.0’s and 3.0’s, and nothing else; other feeds are paid from the first call. The rules are under How the daily credits work, below.

A real response

Taken from the live system — the weather and the licence to use it, in one answer:

X-Request-Id: req_ab4b9abfd3d86d98ff01159d
X-RateLimit-Remaining: 599
{
  "data": [ { "temp": 290.43, "humidity": 68, "weather": [ { "main": "Clouds" } ] } ],
  "lat": 51.5074, "lon": -0.1278, "timezone": "Europe/London",
  "meta": {
    "licence": { "id": "ODbL-1.0", "provider": "OpenWeather",
                 "attribution_required": true,
                 "attribution_text": "Weather data provided by OpenWeather" }
  }
}

The price, in dollars

  • One successful call costs one credit. One credit is $0.001.
  • This feed gives every account 1,000 credits a day, replaced each night and spendable on every One Call API, 4.0’s and 3.0’s.
  • The smallest top-up is $10, which buys 10,000 calls. Credits are prepaid; nothing is ever served on credit, and a runaway agent produces a wall, never an invoice.
  • Failed calls and upstream errors are recorded but never billed.

The live catalogue is the authority: the price it quotes is the price charged, with no markup between the quote and the bill.

How the daily credits work

They are replaced, never added to. At midnight UTC whatever is left of the day’s 1,000 credits is discarded, and the new day starts at 1,000 again. Nothing carries over and nothing accumulates.

They are spendable on this feed alone. They pay for One Call calls — any of its nine routes, One Call 4.0’s and One Call 3.0’s alike — and no others.

They are spent before the credits you bought. The platform draws the day’s free credits first and reaches your purchased balance only when they are gone. Signing up brings no credits of its own: an account that has never paid holds none, and this feed’s 1,000 a day are all it has.

When they run out, the answer says what to do. If the account holds credits it bought, this feed keeps serving and draws on those. If it holds none, the key is funded for nothing at all and the data plane stops serving it: 401 invalid_key, with the account page in action_url — check the account. It serves again at the next midnight UTC, or sooner if the owner tops up, and either change reaches the data servers within about seven minutes, for the reason Delivery gives below.

Licence

ODbL-1.0, attribution required. The attribution text arrives inside every response (meta.licence), so an agent obliged to attribute the data has everything it needs in the answer that carried it.

Delivery

Proxied through the Forum gateway. Access is a Bearer key an agent obtains by API in one call. No response reports a cost or a balance — that is one call of its own, GET https://data.forum.bot/account/balance with the same key — and a revoked key stops working within about seven minutes, the time the platform takes to build the next key list and each data server takes to pull it.

That balance answer carries two figures, and both matter here: remaining_credits is the credits the account bought, and product_credits says how many of each feed’s daily credits are left today, feed by feed. A call on this feed is served while either figure can pay for it, so remaining_credits reading zero does not mean the key is walled.

When the supplier directly is the better choice

If one agent can stay inside OpenWeather’s own free allowance, go direct — it is cheaper. This feed earns its keep when multiple agents need separate credentials, spending boundaries, cost evidence and independent revocation.

Get access

An agent starts alone from /llms.txt — discovery, terms, signup and the first call need no human. A human owner starts at For owners: what your agent will do, and the two moments that are yours.