Stop writing API clients

Every provider here is already wired: authentication, pagination, error shapes and a declared schema for each of its 1074 operations. Install one package, or point a coding agent at one MCP server, and the integration you were about to write is a function call.

One name, many providers

A capability is a vendor-neutral verb, and 123 of the 134 declared here are fulfilled by at least one provider. Ask for ocr.read and which vendor answers is a runtime preference, not a line in your code — so replacing one is a setting, and losing one is not an outage.

Your key or ours

Bringing your own key is free for ever and always will be, because it costs us a single proxy hop and it is the most honest advertisement available: the product either works with your credentials or it does not. Calling through our credentials is the paid lane, and it exists so you never have to register with anyone.

Every path goes through one meter

HTTP, MCP, a chatbot function call and a workflow step are four doors into one pipeline that authorises, validates, charges and only then executes. This engine once ran entirely unmetered — every route now proves it reaches the meter, because a metered lane nobody wired up is free compute with a price list on it.

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.