One install, every provider

A dependency-light client that authenticates with a Leumas API key and calls the same operations this site documents. It does not bundle the engine — the catalogue lives on our side, so a new provider appears without you upgrading anything.

Two ways to call the same thing

Name the provider and the operation when you mean that provider. Name the capability when you do not care, and the client resolves which of your linked accounts or our credentials answers it. The second form is what makes a provider outage a preference change rather than a deploy.

Errors are shaped, not stringly

A refusal carries a status, a machine-readable code and the detail you need to act — an exhausted quota is a 402 with the limit and the count in it, not a sentence you would have to parse. A vendor error is passed through with its own status intact rather than flattened into a generic failure.

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 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.

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.