Webex publishes 178 APIs on the network — Cisco’s collaboration platform, covering messaging, meetings, calling, devices and contact-centre workflows. It scores 58.9, a strong band.
Then there is the number that stops the profile:
Callable contracts: 0.0%.
What that means
The catalog holds 178 Webex contracts. Not one of them resolves to a host a client can actually call as published.
This is not the same as the API being down. Webex works; thousands of integrations run against it every day. It means the published specifications — the machine-readable artifacts an integrator or an agent would generate a client from — do not carry a resolvable server URL.
Compare across this week’s profiles: Microsoft Graph is 100% callable across 564 contracts. Salesforce is 100% across 256. Mastercard is 100% across 166. Webex is 0% across 178.
A developer hits this and shrugs — they read the docs, find the real host, and hardcode it. An agent hits this and stops. The contract is the only thing it has.
Everything else is in decent shape
| Facet | Score |
|---|---|
| Governance | 68.8 |
| Contract quality | 67.4 |
| Commercial clarity | 60.5 |
| Developer ergonomics | 56.5 |
| Discoverability | 50.0 |
| Operational transparency | 42.1 |
Governance at 68.8 is the strongest of this week’s profiles. The catalog holds one AsyncAPI, nine JSON-LD contexts and two Spectral governance rulesets. Webex’s developer surface includes authentication docs, a portal, getting-started guide, engineering blog, support and twenty-two more resources.
Someone at Cisco is doing careful work here. Two Spectral rulesets means governance is being enforced in a pipeline, not just aspired to in a wiki.
Agent readiness: 48.6
1,931 operations, 989 acting, 84 human-in-the-loop.
Eighty-four consent markers is the best ratio in this week’s profiles by a wide margin — roughly one for every twelve acting operations, against Microsoft Graph’s one for every 190 and Mastercard’s one for every 76.
Verified error semantics, verified OpenAPI examples, verified rate-limit signalling. Three verified dimensions, which is more than most providers manage. Absent: MCP server, Agent Skills, .well-known catalog, agent card, consent identity, dry-run mode, idempotency.
Webex also carries the Telecommunications regulatory regime, matched via tags, scoring 58.3 — mid-pack for a regulated communications provider.
The gap between careful and callable
This profile is the clearest illustration on the network that governance and callability are independent variables. Webex has invested in the things that are hard to fake — Spectral rulesets in CI, verified examples, verified error semantics, real consent markers — and shipped 178 specifications that no generated client can reach.
It is also the most fixable finding in this week’s set. Populating servers correctly is a build-pipeline change, not an architecture change. A provider already running Spectral rules has the machinery to enforce it — a single rule requiring a resolvable, non-templated server URL would catch all 178.
Takeaway
178 APIs, the best governance score and the best human-in-the-loop ratio of the week, three verified readiness dimensions — and zero callable contracts. Webex did the expensive parts well and left the cheap part broken.
See the full profile at apis.io/providers/webex/.