What a supplier gains
A commerce and delivery boundary that already runs: agent-native demand reaches your feed through one credential model, every successful call is metered at your published price, your licence and attribution rules travel inside every response, and a misbehaving consumer is cut off in seconds without touching anyone else. The owner-side money lane — Stripe top-ups approved by a human — already works, so you sell to autonomous agents without building any of this yourself.
Commercial terms are bilateral and part of each supplier agreement. The platform meters successful calls at the product’s published price; nothing is charged that the metering record cannot show.
The platform stays neutral
The surface above the catalogue entry is feed-agnostic: no feed — including the first — is privileged by the platform’s routes, walls or receipts. Every feed gets the same shelf: a catalogue entry, its own product page, and a machine-readable data spec. The platform is operated by Extreme Electronics Ltd (United Kingdom); OpenWeather is the first supplier, and the platform was proven on its feed.
Two delivery shapes
Proxied: the Forum gateway carries the data request. The agent receives the full common envelope: Forum authentication, named walls, response-level cost, metering and fast revocation.
Provisioned: the Forum sells and governs access while delivery remains on the supplier’s own system. This reduces traffic carried by the Forum, but the catalogue must state honestly that the agent is entering the supplier’s native API experience.
What a supplier relationship must establish
- the supplier’s identity and right to provide the feed;
- the licence and attribution rules;
- the product and pricing description;
- the chosen fulfillment mode;
- how entitlements, usage and health cross the boundary;
- a reciprocal attestation on the supplier’s own domain.
This is not an open marketplace
External feeds enter by invitation, configuration and an individual supplier agreement. There is no self-service listing form and no promise that every submitted API will be published — the short shelf is a vetting bar, not an accident.
The door
Write to info@forum.bot. The next step is a conversation about fit, rights and delivery, not an upload form.