For Agents and Bots

Weather data for AI agents

Two ways to put OpenWeather data behind an agent. Set it up yourself with an ordinary OpenWeather API key, or let the agent set itself up through OpenWeather for agents — our agent lane, powered by The Bot Forum — where it signs up over the API with one request and pays per call from a balance you fund. Both serve OpenWeather data. The difference is who does the setup, and how the spending is bounded.

Get an OpenWeather API key Send your agent to the agent lane A person sets up the first. An agent sets up the second, with the prompt further down this page.

You set it up

A direct OpenWeather key

You create the account and paste the key into the agent's configuration.
The full OpenWeather product range, including One Call 4.0 and everything else on the API list.
The right choice when a person configures the agent in advance and manages the account.
Your coding agent can read any of our docs pages as plain markdown by adding .md to its address, for example openweathermap.org/api/one-call-4.md.

1,000 One Call 4.0 calls a day, freethen 0.0012 GBP a call, charged at the end of the month. Other products on their own plans.

The agent sets itself up

OpenWeather for agents · powered by The Bot Forum

The agent signs up with one POST. No browser, no password, no CAPTCHA, no form. Its two strings arrive in the same response: the secret that runs the account, the data key that fetches data.
Every response says what the call cost and what is left. The balance is prepaid, so the agent can never spend past it.
Each agent can hold its own data key. Revoke one and the others keep working; the secret stays with you.
One Call 4.0 and One Call 3.0 data, served at data.openweathermap.org by The Bot Forum's engine — our data and our brand, under licence to the lane's operator.
Or as MCP tools: the same loop through six tools on mcp.openweathermap.org, for Claude Code, Cursor, VS Code and every other MCP host. mcp.openweathermap.org ↗

$0.001 a call1,000 calls granted at signup, once. Top-ups from $10, approved by you on the payment provider's page, in The Bot Forum's name.

Give your agent the prompt agents.openweathermap.org ↗

Give this to your agent

Any agent that can make HTTP requests can use the lane. There is nothing to install and no dashboard to sign up on. Paste this into your coding agent or assistant. Replace <YOUR EMAIL ADDRESS> with an address you read: it becomes the account's only human credential.

Prompt for your agent

Read https://agents.openweathermap.org/llms.txt and follow it.
Sign up with the email <YOUR EMAIL ADDRESS> and store the two strings it returns securely —
the secret and the data key, each shown exactly once and never again.
Then fetch the current weather for latitude 51.5074, longitude -0.1278,
and tell me what the call cost and how much of the balance remains.

On its first runYour agent has an account, its two strings, and live weather data. It starts with 1,000 credits, which is 1,000 calls of either product.

When the credits run lowIt brings you two links: a one-time payment page at the provider, in The Bot Forum's name, and the owner console that explains what is being asked. You pay on the provider's page. Card details never touch the lane.

After you payCredits land in about fifteen seconds and the agent continues on its own. The smallest top-up is $10, which is 10,000 calls.

Your account lives at The Bot Forum, and so does its console. The lane's operator keeps the account. Its owner console is console.forum.bot, a Forum-branded page, not an OpenWeather one. Signed out, it explains the payment being asked of you. Signed in, it lists the account's data keys, shows its usage and its money, and mints a new secret if the agent lost the old one. You log in with your email alone: a one-time link arrives from info@forum.bot. Every payment-required answer your agent receives carries the console's address, so there is nothing to remember.

Or add it as MCP tools

If your agent runs in a host that speaks the Model Context Protocol — Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Codex, the OpenAI Responses API, the connectors of claude.ai and ChatGPT — it can do everything on this page through six tools instead of raw HTTP: list the feeds, inspect one, sign up, fetch data, read the balance, fetch a top-up link. No key is needed to look. The key sign_up returns does the rest, and the tool descriptions carry the whole loop, so the prompt above shrinks to the task itself.

One configuration entry, for any MCP host

{ "url": "https://mcp.openweathermap.org/mcp" }

Claude Code:  claude mcp add --transport http forum https://mcp.openweathermap.org/mcp

Same data, same pricesEvery tool call is one of the public calls on this page, with the same cost headers on the answer, the same terms and the same $0.001 a call. No tool pays: a top-up is still a link a person completes.

Nothing storedThe server keeps no state and no keys of its own. Your key rides in the host's configuration, or as an argument in the session that signed up.

The full descriptionThe six tools, the two-string rule and the entry for each client, served by the server itself as markdown: mcp.openweathermap.org ↗.

Side by side

Both prices and both allowances, so you can decide with the numbers in front of you. For an integration a person sets up in advance, the direct account is usually the better deal.

	Direct OpenWeather account	OpenWeather for agents
Who signs up	A person, on this site.	The agent, with one API call.
What is served	The full OpenWeather range.	One Call 4.0 and One Call 3.0.
Price	1,000 One Call 4.0 calls a day free, then 0.0012 GBP a call.	$0.001 a call, in US dollars, from a prepaid balance.
Free allowance	1,000 calls a day, every day.	A one-time grant of 1,000 credits at signup.
Where the cost of a call is shown	On your invoice.	In headers on the response that carries the data.
Keys	As many as you issue, from your account page.	One per agent if you like, issued by the agent itself; each can be revoked on its own, within seconds.
Spending limit	A daily call limit per product, set in your account's Billing plans tab.	The prepaid balance. Nothing is served on credit; at zero the calls stop with a named error.
Human steps at setup	Signup and payment details, once.	None until the granted credits run low.
Human steps afterwards	None. The subscription renews.	A person approves each top-up, $10 minimum.
Account console	Your account page on this site.	The Bot Forum's page at console.forum.bot; you log in by a mailed link.
Support	OpenWeather support.	The lane's operator, The Bot Forum: info@forum.bot.

What the agent does by itself, and what it cannot

By itself

Reads the catalog, prices, license and terms from one address. No key and no account are needed for that.
Accepts the terms by signing up. The terms are JSON; the version served at that moment is recorded and returned, and every version stays readable at its own permanent address.
Creates the account with a single POST and receives its two strings once, in the response — the secret that runs the account and the data key that fetches data. The email in that request is the account's only human credential: the owner console has no password and admits nobody except through a link mailed to that address.
Calls for data and reads what the call cost and what remains from headers on the same response.
Asks for a payment link when the balance runs low and hands it to the person responsible.

Never by itself

An agent cannot pay. Approving spend is a human step by design. The agent may open the payment, but a person completes it on the payment provider's own page, and no surface of the lane accepts a card. Anything that asks your agent for card details is neither us nor The Bot Forum.

When the balance reaches zero, the data stops. The error names the address to send that person to, and it is a stable address, so a link to it in a log or an email stays good.

A revoked key is told the truth, key_revoked, not a vague failure, so a well-written agent stops instead of retrying.

Signup to first call

The whole path in four requests. Everything below was read from the live systems; the agent's own guide shows every stage with a real request and a real answer.

Read the terms

curl -s https://agents.openweathermap.org/tos

The Terms are The Bot Forum's — the lane's operator and the party you contract with — served on this lane's own name; the same document, byte for byte, that the Forum serves at its own address. Signing up accepts the version served at that moment, and the answer tells you which; there is no string to quote. Every past version stays readable at /tos?version=<version>.

Create the account

curl -s -X POST https://agents.openweathermap.org/v1/accounts \
  -H 'Content-Type: application/json' \
  -d '{"email": "<your email address>"}'

One field, no header. The answer is a 201 carrying the account, the secret — the one string that runs the account — the data_key, whose key fetches data, and a grant block of 1,000 credits. Both strings are shown exactly once; store them before anything else. Nothing is asked that the agent must invent: no Terms string, no marker. If the answer never reached you, do not sign up again — the account exists, and the person responsible recovers it at the console by mail.

Call for data with the data key signup returned

curl -s -H 'Authorization: Bearer <data key>' \
  'https://data.openweathermap.org/onecall/current?lat=51.5072&lon=-0.1276'

The data key goes in the Authorization header, never in the URL; the secret fetches nothing here, and a data key runs nothing on the platform host — the wrong string answers 403 wrong_credential naming the right one. The body is our One Call document, unchanged, so the fields are the ones in our One Call 4.0 and 3.0 docs. The lane adds one block, meta, carrying the license and attribution text and an echo of the location, and replaces our prev/next pagination links with opaque next_cursor/prev_cursor values.

Read the price on the answer

X-Cost-Charged: 1
X-Cost-Remaining: 999
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 599
X-RateLimit-Reset: 1787604249
X-Request-Id: req_ab4b9abfd3d86d98ff01159d

X-Cost-Remaining is a credit count, or the string unknown while the balance has not replicated yet. Never read unknown as unlimited. Keep the X-Request-Id of anything that goes wrong; it is how the exact call is found.

Routes are GET https://data.openweathermap.org/{product}/{route}, with no /v1 prefix on the data host. The two products are onecall, which is One Call 4.0, and onecall3, which is One Call 3.0. onecall serves current, timeline/1min, timeline/15min, timeline/1h and timeline/1day. onecall3 serves forecast, timemachine, day_summary and overview. Any other route answers 404, including 4.0's alert-detail endpoint, which the lane does not serve. Parameters follow our own documentation: timemachine needs dt, day_summary needs date.

Prices, limits and errors on the agent lane

Prices and limits

One credit is $0.001. One Call costs one credit per successful call, on either product. The price list at agents.openweathermap.org/v1/products is the authority, and the quoted price is the charged price.
Only successful responses are billed. An upstream failure costs nothing and says so.
A new account receives 1,000 credits once, into one balance spendable on any product.
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 later. Poll for them, and never open a second payment because the first has not arrived.
Data responses carry the three X-RateLimit headers shown in step 4, and a 429 rate_limited names the interval to wait. An answer may be shared for up to 60 seconds on any route; after that the call reaches our API live.
At a zero balance, calls answer 402 payment_required and carry the page to send a human to. Nothing is ever served on credit.

Errors and next steps

Every refusal answers with a stable code, one HTTP status, and a machine-readable next action where one exists. The dictionary is closed at seventeen codes, so an agent's error handling is written once, against a list that does not grow. It branches on the code, never on prose.

The error dictionary, every code and the reaction it calls for.
The agent guide, every stage with a real request and a real answer, including the money wall. Its Stage 9 is a complete Python agent, signup to the money wall, in one piece.

Licensing

Data served on the agent lane is OpenWeather data, licensed ODbL-1.0, and attribution is required: Weather data provided by OpenWeather. The license and the attribution text travel inside every data response, so the agent never has to fetch them separately. The lane is OpenWeather's own channel for One Call data to agents, run for us by The Bot Forum.

The lane's terms are The Bot Forum's — 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.

Questions people ask

Can an AI agent get OpenWeather data without a person filling in a form?

Yes, through OpenWeather for agents, our agent lane. The agent reads the terms, creates an account with one POST, receives its two strings in the same response, and calls for data. A person is needed only when money is involved: the agent starts a top-up, a person completes it on the payment provider's page, and the agent continues.

Which is cheaper?

For an integration a person sets up, the direct account: 1,000 One Call 4.0 calls a day are free, every day, then 0.0012 GBP a call. The agent lane charges $0.001 a call, in US dollars, from a prepaid balance, with a one-time grant of 1,000 calls. The lane's price per call is lower; the direct account's daily free allowance is larger. Both numbers are on this page so you can decide.

Why would I use the agent lane if I already have an OpenWeather key?

Three cases. An agent has to obtain its own access with no form in front of it. You run several agents and want each on a data key you can revoke on its own, while the secret that runs the account stays with you. You want a hard spending line the agent cannot cross, with the cost of every call on the response that carries it.

Can the agent spend my money?

No. The balance is prepaid and nothing is served on credit. The agent can ask for a payment link; only a person can complete it, on the provider's page. When the balance reaches zero, the calls stop with a named error.

Does it work over MCP?

Yes. The lane has an MCP server, mcp.openweathermap.org, run by The Bot Forum, that presents the same signup, data and balance as six tools for any MCP host: Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Codex, the OpenAI Responses API, the claude.ai and ChatGPT connectors. One configuration entry, no key needed to look, the same prices and terms. The description and the entry for each client: mcp.openweathermap.org.

Who runs the agent lane, and who takes the money?

OpenWeather for agents is our agent lane, powered by The Bot Forum. It is operated and sold by Extreme Electronics Ltd, trading as The Bot Forum — a company under common ownership with OpenWeather, registered in England and Wales, no. 08247457. The account, the balance, the terms and the payment are the Forum's; the data is ours, supplied under licence. Write to the Forum about accounts, credits, keys and billing (info@forum.bot), and to us about OpenWeather accounts and keys.

Machine resources

If you are a program, start with the first one. Everything else, the OpenAPI contract, the per-product specs and the error dictionary, is reachable from it.

Agent quickstartSignup, first call and the money wall, with verbatim commands.
agents.openweathermap.org/llms.txt Machine manifestProducts, prices, endpoints and the current terms version in one fetch.
agents.openweathermap.org/ Terms, current versionThe machine-readable terms — signing up accepts the version served at that moment; every past version at /tos?version=<version>.
agents.openweathermap.org/tos Agent guideEvery stage with a real request and a real answer.
agents.openweathermap.org/guide.md Error dictionarySixteen codes, their HTTP status and the reaction each calls for.
agents.openweathermap.org/errors.json Platform contractThe OpenAPI description of every platform route.
agents.openweathermap.org/openapi.json Over MCPThe six tools, the two-string rule and the entry for each client, as markdown, served by the server itself at its root.
mcp.openweathermap.org/

If you are the person responsible for the agent

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 console is The Bot Forum's — the lane's operator and seller — and the payment itself completes on the payment provider's own page, in the Forum's name, which sends you back to the console when it is done. You sign in with a link mailed to the account's address; there is no password. Revoke a key there and the agent stops using it within seconds. The console is the destination an agent hands you; it holds nothing when signed out, so an agent reads its own balance from the API instead.

Something wrong on the lane's side — accounts, credits, keys, billing — with or without an account: The Bot Forum, info@forum.bot. Ask your agent for the X-Request-Id of the failing call and quote it.

About the agent lane

OpenWeather for agents · powered by The Bot Forum. The agent lane is operated and sold by Extreme Electronics Ltd, trading as The Bot Forum — a company under common ownership with OpenWeather, registered in England and Wales, no. 08247457. The account, the balance, the terms and the payment are the Forum's; the data is OpenWeather's, supplied under licence. The Bot Forum is the platform behind the lane, and this is its first deployment under a supplier's own brand: forum.bot.

OpenWeather support covers OpenWeather accounts and API keys. The lane's accounts, credits, keys and billing are the Forum's: info@forum.bot. For everything about OpenWeather's own APIs, start at How to start.