AI Readiness AuditRef. APM-D8A38C93 · Confidential
Getting Started with Passport Global API
An independent assessment of whether the Getting Started with Passport Global API specification is ready for AI-assisted integration and autonomous agents, prepared for Passport.
61/100
Significant gaps
Functional 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
61
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
478
Total instances: 0 critical, 111 high, 180 medium, 187 low
33
Rule groups across 4 pillars: 0 critical, 111 high sev. instances
Executive summary
Your API scores 60.8 out of 100, reflecting significant gaps across multiple areas. Standards compliance scored 55.1, while documentation readiness for AI and SDK readiness for AI scored 61.7 and 69.5, respectively. Agents cannot make autonomous calls due to the API's current lack of readiness, although it functions for AI-assisted builds. Prioritizing improvements in standards compliance will address the most pressing weaknesses.
Readiness by pillar
Significant gaps
61 / 100
FoundationThe spec itself
55/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
55Significant gaps
Build Time ReadinessAI writes the code
66/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
62Significant 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
70Significant 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 Getting Started with Passport Global 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
Residual risks to monitor
No active failures, but elevated risks remain. Continued improvement will bring these into the managed band.
Foundation
The spec itself
55 / 100
Elevated risk · Standards compliance
Fix Spec Violations to Ensure Compliance
You must address multiple spec violations that break toolchains and hinder SDK generation for the Passport Global 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
66 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
You must improve documentation clarity and detail to prevent incorrect assumptions during builds.
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
Success response lacks body schema
The API's success response fails to define a body schema, causing generated SDKs and AI-written code to produce incorrect types and formats.
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 Essential Operation Identifiers
The absence of operationIds in your API prevents autonomous agents from executing tasks correctly, risking operational failures.
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