{
  "id": "p_6hhYKSNKQEvg9zf-",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_6hhYKSNKQEvg9zf-",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You are putting together a shortlist of customer service automation vendors, and you want to know which ones an AI agent could actually work with. Ada is on the list. You pull its profile on APIs.io, and the headline is strong: a Kin Score of 87.3, 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 company, the post says, that puts it among the strongest public surfaces in the catalog.\n\nYou keep reading, because a score only helps if you know what is under it. Ada describes a suite of REST APIs for knowledge, end users, conversations, data export, data compliance and integrations, all on rotatable API keys, with JSON and cursor pagination. The record carries 27 contracts, none marked as derived, and all 27 score as callable. That matters to you. Unlike tenant-templated platforms, an agent reading Ada's contracts has an endpoint it can reach.\n\nThe facet table shows where the score comes from. Operational transparency is 92.1, developer ergonomics 85.7, discoverability 83.3, access clarity 75.0 and contract quality 71.0. Then there is contract governance at 35.6, the one facet that looks like a different company when every other facet sits above 70. Operational transparency carries the score.\n\nNow you try to answer a simple question: how many APIs does Ada have? You compare it against peers on API count, and the page turns on its own authors. 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 different answers, depending on which field you read.\n\nThe post does not blame Ada for this. It says the problem is the catalog's own. Three of those pages 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. The catalog's pipeline split the same surface twice under two naming conventions and kept both. If you had ranked vendors by count, you would have been ranking on the catalog's mistake.\n\nThen you get to the agent story, which is what you came for. 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 the post calls 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.\n\nThe post is careful about what it will not credit. Agentic access, at 45 operations with 26 of them acting, is a derived artifact, the catalog's 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 post says the delegated-identity gap is the one that matters. If you plan to let an agent act on your customers' behalf through Ada, that is the line you underline.\n\nYou also see that Ada carries the AI and Biometrics regulatory regime, where it scores 41.8, with PIPEDA, GDPR, CCPA, CPRA and HIPAA in view. That is a note for your compliance team, not a verdict.\n\nThe post ends with a short list of what 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 the catalog's side, the duplicate API pages need to collapse to one slug each, and api_count needs to match what the record actually lists.\n\nWhat you take away is two things. Ada's surface is strong and reachable, but its delegated-identity gap is real and worth raising before you hand an agent any authority. And the count you saw on the page is not a fact about Ada. It is a flaw in the record that describes Ada, one the catalog says it owes a fix. As the post puts it, Ada has done more than most, and the record should say so in one number.\n\nRead the original: https://apis.io/2026/10/22/ada-scores-87-3-exemplar-and-its-catalog-cannot-agree-how-many-apis-it-has/",
  "title": "You read Ada's 87.3 exemplar score, then count its APIs three ways and get three answers",
  "topics": [
    "agent-readiness",
    "customer-service",
    "api-catalog",
    "mcp"
  ],
  "published_at": "2026-10-22T13:42:12.032Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}