Pick the verb, not the vendor

A capability names what you want done. This page lists all of them, and each one opens onto every provider that can do it — which is the comparison you were about to do by hand across a dozen pricing pages.

Why this is the useful direction

Choosing an OCR vendor means comparing what half a dozen of them actually return for the same image, and that comparison is normally spread across six marketing sites that each describe a different shape. Here the shape is one canonical input and one canonical output, and the vendors are rows underneath it.

The gaps are shown too

11 capabilities are declared and not yet fulfilled by anything. Their pages exist and say so, because a documented gap is useful — it tells you what to route around today and what we would add next — where a missing page tells you nothing at all.

Questions

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.

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.