Weather data for AI agents

Most integrations do not need this page. When a person sets the agent up in advance, we recommend a direct OpenWeather account: the full product range, 1,000 One Call 4.0 calls a day free, pay-per-call above that, and as many keys as you want to issue.

This page is for the other case — an agent that has to obtain and fund its own access while nobody is watching it.

1. Reads the catalogue, prices, licence and terms from one address. No key and no account are needed to do this.
2. Accepts the terms by exact version string. The terms are JSON, and every version stays retrievable at its own permanent address.
3. Creates an account with a single POST and receives its key once, in the response to that call. The email address in that call is the account's only human credential — use an address the responsible person can actually receive mail at, because the Forum console has no password and admits nobody except through a link mailed to that address.
4. Calls for data, and reads what the call cost and what remains from headers on the same response that carries the data.
5. Asks for a payment link when the balance runs low and hands it to the person responsible for it.

An agent cannot pay. Attaching a card and approving spend are human steps, by design. An agent may open the payment page; a person completes it, on the payment provider's own page — card details never reach the Forum. When the balance reaches zero, the data stops and the error names the address to send that person to. Attaching a card is also the Forum's other human checkpoint: a new account is untrusted until someone does, which the platform signals as 403 verification_required.

• One credit is $0.001. One Call costs one credit per successful call.
• Only successful responses are billed.
• A new account receives a one-time signup grant of 1,000 credits — 1,000 calls of either product — into one balance. The signup response names it in its grant block.
• Top-ups are in US dollars, ten dollars minimum. The agent starts the payment; a person completes it on the provider's page. Credits land about fifteen seconds after that — poll for them, and never open a second payment because the first has not arrived.
• Data responses also carry rate-limit headers, and a 429 rate_limited names the interval to wait.
• At a zero balance, calls answer 402 payment_required and carry the page to send a human to. Nothing is ever served on credit.

Every refusal answers with a stable code, one HTTP status, and the next action to take — so error handling is written once, against a list that does not grow. An agent never has to read a sentence to find out what to do about a refusal.

• The error dictionary — every code and the reaction it calls for
• Every stage, with a real request and a real answer

Data served through The Bot Forum is OpenWeather data, licensed ODbL-1.0, and attribution is required: Weather data provided by OpenWeather. The Bot Forum is an authorized channel for One Call data.

Its terms are versioned and machine-readable, and every version remains at its own permanent address, so an agent can record exactly which terms it accepted and when.

If your agent stores what it fetches and serves it on to others, ODbL's share-alike conditions may apply — the distinction between a produced work and an adapted database is worth reading before you cache.

• Agent quickstart — signup, first call and the money wall, with verbatim commands
• Machine manifest — products, prices, endpoints and the current terms version in one fetch
• Terms, current version — the terms to accept, by version

Everything else — the OpenAPI contract, the per-product specs and the error dictionary — is reachable from those three.

One page shows the balance, what the agent has spent and the keys it holds, and it is where a top-up is started: console.forum.bot. The payment itself completes on the provider's own page. The console is the destination an agent hands a human — it holds nothing when signed out, so an agent polls GET /v1/account/usage instead. Revoke a key there and the agent stops using it.

The Bot Forum is not an OpenWeather product and we do not operate it. It is operated by Extreme Electronics Ltd, a company connected to OpenWeather's founders. We supply One Call data to it under licence.

OpenWeather support covers OpenWeather accounts and API keys. It does not cover the Forum's accounts, credits, keys or billing — send those to the Forum.

• Support for third-party applications