AI Readiness AuditRef. APM-9BBD5196 · Confidential
Whereby REST API
An independent assessment of whether the Whereby REST API specification is ready for AI-assisted integration and autonomous agents, prepared for Whereby.
58/100
Significant gaps
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
58
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
404
Total instances: 0 critical, 82 high, 152 medium, 170 low
35
Rule groups across 4 pillars: 0 critical, 82 high sev. instances
Executive summary
Whereby REST API scores 58.3/100: Significant gaps · Grade D. The weakest pillar is Standards compliance at 55; the strongest is SDK readiness for AI at 65. We recorded 404 finding instances: 0 critical, 82 high, 152 medium, and 170 low. Gaps for AI-assisted builds. Not ready for autonomous agents. Every finding lives in the specification, and the roadmap in this report orders the fixes by impact; resolving them projects the score to 100/100.
Readiness by pillar
Significant gaps
58 / 100
FoundationThe spec itself
55/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
55Not ready
Build Time ReadinessAI writes the code
60/100
Documentation Readiness for AI
Descriptions that say when to use an operation, examples that pin down every shape: whether an AI can learn the truth of your API from what you publish
55Significant gaps
SDK Readiness for AI
Clean types, predictable naming, correct formats: whether production-grade client code can be generated from your spec, by SDK pipelines and AI coding assistants alike
65Significant gaps
Runtime ReadinessAgents make the calls
60/100
MCP Readiness
Whether your operations survive being turned into tools: distinct names, descriptions that carry what an agent must know, safe invocation semantics, auth, error recovery, and context budget
60Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Whereby REST API specification against thousands of deterministic rules we have refined over twelve years of building API tooling, supplemented by AI-based analysis. Every finding is reproducible from the spec itself, scored consistently, and paired with a concrete fix.
What's at stake
Where you’re exposed – and where you’re not
4 failure modes across 3 groups. Some are active risks; others are under control.
Foundation
The spec itself
55 / 100
Active risk · Standards compliance
Specification Violations Disrupt API Functionality
You must address multiple specification violations that break toolchains and hinder SDK generation for the Whereby REST API.
22→29
code quality score out of 40: the lift consumers achieve when the underlying spec is clean and standards-compliant
APIMatic Context Plugins research · Series B · June 2026
Build Time Readiness
AI writes the code
60 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You must provide detailed parameter descriptions to prevent coding assistants from building on incorrect assumptions.
74%
of developers name missing or unclear documentation as the top reason they abandon an API. AI readers are stricter: what a human would ask about, an AI assumes.
APIMatic Developer Experience research · June 2026
Elevated risk · SDK readiness for AI
SDKs generate incorrect types and formats
You should refine the schema layer to ensure accurate integration code and improve SDK readiness.
0
fabricated API constructs when a coding assistant was grounded in an AI-ready spec. Ambiguity in the spec is what triggers hallucinated integration code
APIMatic Context Plugins research · 6 APIs · 3 models · June 2026
Runtime Readiness
Agents make the calls
60 / 100
Elevated risk · MCP readiness
MCP Tools Lack Operation Identifiers
You must define `operationId` for each API operation; missing identifiers prevent agents from executing tasks effectively.
65%
reduction in token consumption when agent tools are grounded in authoritative API context. Bloated or confusable tools consume up to 3.3× more.
APIMatic Context Plugins research · Series A · June 2026
The evidence numbers come from our controlled research: 6 experiments across 3 models, 6 commercial APIs, and 3 languages. We derive each card's risk status from this API's pillar scores. Full methodology at apimatic.io.
Contents