226 providers, filterable

The whole catalogue, with the two facts that decide whether an integration is usable: how it authenticates, and what it can actually do. Nothing here is a logo wall — every row links to the real operation list.

Sorted by what you are choosing between

Filter by category when you know the job, by authentication when you are deciding how much setup you can tolerate, and by capability when the vendor genuinely does not matter to you. Most integration decisions are one of those three questions, and none of them is answered by an alphabetical list.

The counts are read, not written

Every number on this site comes out of the live registry when the site is built, so a page cannot advertise an operation that is no longer there. That matters more than it sounds: a provider page claiming a call the engine does not have is a page that ranks first and fails second.

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