Questions worth answering before you wire this in
The things people ask in the first ten minutes, answered without a sales voice. If your question is not here, the answer is probably on the provider or capability page it concerns.
The short version
Browse for free, call with your own key for free, pay when you want our credentials. Everything is metered through one pipeline, keys are sealed at rest, and every count on this site is read from the live registry rather than written down by anyone.
Questions
Do I have to bring my own API keys?
You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.
What happens to a key I store here?
It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.
What is a capability, and why not just name the provider?
A capability is the vendor-neutral verb — ocr.read, weather.current — and 123 of them are fulfilled by at least one provider today. Calling the capability means the provider is a runtime choice rather than a line in your code, so swapping one out is a preference change and not a rewrite. Naming the provider directly still works when you actually mean that provider.
Is every call metered?
Yes, and deliberately so: every path — HTTP, the MCP server, a chatbot function call, a workflow step — goes through one pipeline that charges before it executes. This engine once ran entirely unmetered, which is free compute with a price list on it, and a test now asserts there is no route around the meter.
What does a call cost?
Browsing everything here and calling with your own key cost nothing. Calls through our credentials come out of your plan allowance and then out of the token wallet, charged per operation with the vendor cost recorded alongside so the price is not a guess.
Can a coding agent use this?
That is what the MCP server is for. Point any MCP client at the bridge one-liner and every operation you are entitled to becomes a tool it can call, with the same names, the same schemas and the same meter as the HTTP API.
What happens when a provider changes its API?
The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.
Do you rate-limit me?
Per account, never per IP. Everything here sits behind a proxy the whole platform shares, so a per-IP bound would be a platform-wide bound the first busy hour exhausts. Where a provider publishes its own limits we pass its throttling response straight back rather than retrying into it.
What if nothing fulfils the capability I need?
11 capabilities are declared and not yet fulfilled by any provider, and their pages say so rather than 404ing. That list is the honest shape of the gap, and it is the shortest route to telling us what to add next.
Can I use this without a Leumas account?
Browsing, reading every schema and comparing providers need no account at all. Making a call needs one, because a call that cannot be attributed to an owner cannot be charged to anyone and cannot be refused to anyone — that boundary is the security model as much as the billing one.