Ada scores 87.3 on the Kin Score, exemplar band, up 2.9 from 84.4 at the last run. Its Agent Readiness is 47.3, agent-ready, and the rubric records that a gate held it back from agent-native. For a Toronto-founded customer service automation company, that puts it among the strongest public surfaces in the catalog. The record that describes the surface is the weak part.
What is in the surface
Ada describes a suite of REST APIs for knowledge, end users, conversations, data export, data compliance and integrations, all on rotatable API keys, JSON and cursor pagination. The record carries 27 contracts, none marked as derived, and all 27 score as callable. That callable figure is the detail worth stopping on: unlike tenant-templated platforms, an agent reading Ada’s contracts has an endpoint it can reach.
| Facet | Score |
|---|---|
| Operational transparency | 92.1 |
| Developer ergonomics | 85.7 |
| Discoverability | 83.3 |
| Access clarity | 75.0 |
| Contract quality | 71.0 |
| Contract governance | 35.6 |
Operational transparency carries the score. Contract governance is the one facet that looks like a different company: 35.6 when every other facet sits above 70.
The count problem
Here is the tension, and it is ours. The provider record says api_count: 6, on a published basis. The same record lists 22 APIs. The site builds 26 API pages under apis/_apis/ada/. Three of those are pairs of the same API under two slugs: ada-audit-log-api and ada-auditlog-api, ada-end-users-api and ada-endusers-api, ada-webhook-management-api and ada-webhookmanagement-api. Ada did not publish duplicates. Our pipeline split the same surface twice under two naming conventions and kept both. A reader comparing Ada against peers on API count gets three different answers depending on which field they read.
The agent story
Ada ships a first-party remote MCP server on the customer’s own Ada instance domain, behind OAuth, documented at docs.ada.cx/mcp. The record scores it as templated, which is the honest description: the endpoint exists per tenant, not at one public address. Idempotency is documented, error semantics are verified, rate limits are documented, an event surface is described, and a well-known catalog is present. Agent Skills are first-party too.
What I do not credit: agentic access (45 operations, 26 of them acting) is a derived artifact, ours rather than Ada’s. And the identity row is dark. Protected resource metadata, delegated identity, dynamic client registration and consent identity are all unlit, as are reversibility, dry-run mode and an agent card. For a company whose product is AI agents acting on behalf of customers, the delegated-identity gap is the one that matters.
Ada also carries the AI and Biometrics regulatory regime, where it scores 41.8, with PIPEDA, GDPR, CCPA, CPRA and HIPAA in view.
Takeaway
Three things would move the number. On Ada’s side, protected resource metadata on the MCP server would light the identity row, and documented reversibility for the 26 acting operations would close the gap to agent-native. On our side, the duplicate API pages need to collapse to one slug each, and api_count needs to match what the record actually lists. Ada has done more than most. The record should say so in one number.
See the full profile at apis.io/providers/ada/.