Coveo publishes 152 APIs on the network — an AI-relevance platform delivering search, recommendations and discovery across digital workplaces, service portals, websites and commerce storefronts. It scores 62.0, a strong band, with 55.0 on agent readiness.
What is in the surface
The API family decomposes cleanly by function: search, content indexing via Push and Stream, usage analytics, machine learning, commerce, and platform administration. Named entries include the Activities API, Administration API v15, Advanced Model Configurations, Analysis V3, Analytics API v14, and — notably — an Agent Configuration API and an Agent Orchestration API.
The catalog also holds three JSON-LD contexts and two Spectral governance rulesets, plus a first-party MCP server.
Coveo’s developer surface includes authentication docs, documentation, GitHub presence, support, a CLI, tooling and thirty more resources. The CLI matters more than it sounds — a provider that ships a command-line tool has already made the operations composable, which is most of the work of making them agent-callable.
One facet drags the whole score
| Facet | Score |
|---|---|
| Contract quality | 73.2 |
| Governance | 68.8 |
| Discoverability | 68.5 |
| Commercial clarity | 60.5 |
| Developer ergonomics | 58.7 |
| Operational transparency | 36.8 |
Five facets between 58.7 and 73.2, and then operational transparency at 36.8 — twenty-two points below the next-lowest.
Operational transparency is the facet that asks whether you can see what the API is doing: status page, incident history, changelog, deprecation notices, uptime signalling. It is the difference between an API you can integrate and an API you can depend on.
For a platform sitting in the critical path of a customer’s search experience — where an outage is immediately visible to that customer’s customers — 36.8 is the number to fix. Everything else here is in good order.
Agent readiness: 55.0
1,018 operations, 551 acting, 13 human-in-the-loop.
Present: spec presence, an MCP server, auth clarity, verified error semantics, verified rate-limit signalling. Absent: Agent Skills, .well-known catalog, agent card, consent identity, dry-run mode, idempotency, and event surface description.
The event_surface_described: false is worth noting alongside the operational transparency score — they are the same gap seen from two angles. Coveo indexes content continuously through Push and Stream, which is inherently an eventful process, and neither the events nor the operational state of that process is described in a machine-readable form.
Shipping an MCP server before Agent Skills
Coveo has an MCP server and no Agent Skills, which is the common ordering — the transport before the guidance. It is also the harder half done first.
Where it gets interesting is the Agent Configuration and Agent Orchestration APIs sitting in the surface. Coveo is not just making itself callable by agents; it is selling agent orchestration as a product. A company doing that has a stronger-than-average reason to describe its own event surface, and has not yet.
Takeaway
152 APIs, an MCP server, a CLI, two Spectral rulesets and five healthy facets — held back by a 36.8 on operational transparency and no described event surface, at a company whose product is continuous indexing and agent orchestration. One facet, and it is the one their customers feel.
See the full profile at apis.io/providers/coveo/.