01
Discover data
The agent starts with one address and finds the available feed, terms and usage contract.
forum.bot
/llms.txt/index.json/tosData access led by the agent
From needing data to using it. One smooth agent-led flow.
Give an agent one address. It discovers available data, activates access, receives a key and starts using live weather data. Cost stays visible, the account's one budget bounds every call, and the owner joins only when financial authority must change.
Agent-led setupReady
Weather data requested
One public address begins the complete path
- Discover
- One Call weather data
- Activate
- Account + key
- Operate
- Receive data + read the balance
Agent handles the flow→Owner at funding
Example balance read200
GET data.forum.bot/account/balance
Authorization Bearer <data key>
{ "remaining_credits": 739 }One call, with the key it already has
01public starting address
01available data feed
Everysuccessful call shows cost
Onceowner acts when authority changes
Available data
One Call weather data
Give autonomous workflows governed access to live weather data through one Forum credential model.
Browse the data catalogue ›Data feed / 01Available
- Delivery
- Proxied through the Forum gateway
- Agent access
- Bearer key
- Consumption
- Successful responses only
- Data licence
- ODbL-1.0 · attribution required
One real feed, presented with the rules an owner and an agent both need to understand. Read the product page ›
From need to data
The agent handles the ordinary path.
Discovery, activation, access, data and cost awareness form one continuous flow. The owner appears only when new financial authority is required.
02
Activate access
The agent accepts the current terms and opens an account through the same public contract.
AccountActivated✓
03
Receive a key
The agent gets an immediately usable credential that reaches every feed on the shelf.
BFWeather accessall feedsready
04
Receive live data
The agent calls the feed and receives weather data without another manual setup step.
200
product onecallresult delivered05
Understand spending
One call returns the balance, with the same key. No header guessing, no stale number at the edge.
ask/account/balance→remaining739
06
Stay inside budget
The agent continues autonomously inside its line. At the boundary, it receives one precise next action.
invalid_keyaction urlthe owner tops up at the account pageRecovery is part of the product
A wall tells the agent what to do next.
Stable codes replace guesswork. The client can retry, change the request, stop or involve its owner.
invalid_keyHTTP 401Don't retry; check the account at the address in action_url. On the data plane this is the one refusal for a key a data server cannot serve — a spent balance is the usual reason — and a human clears it there.
upstream_errorHTTP 502Retry with backoff; the call was not charged.
key_revokedHTTP 401Stop and escalate as a possible incident. The platform host only: a data call answers invalid_key.
rate_limitedHTTP 429Wait for the supplied retry interval, then resume.
When direct access is the better choice
If one agent can stay inside a supplier’s direct free allowance, use the supplier directly. It is cheaper.
The Forum earns its place when multiple agents need separate credentials, boundaries, spending evidence and independent revocation.
Direct is cheaper in dollars and more expensive in blast radius — the reach of one leaked or runaway credential.One service, two reading modes
The promotional site and the machine contract tell the same story.
Humans get explanation and context. Agents get deterministic routes, versioned terms and closed dictionaries. Neither surface invents a second product.
One public surface
Clear enough for owners. Exact enough for agents.
Start with the human explanation or hand the machine entry directly to an agent.