AI Readiness AuditRef. APM-B5B845F2 · Confidential
Rating API
An independent assessment of whether the Rating API specification is ready for AI-assisted integration and autonomous agents, prepared for Canada Post.
71/100
Needs work
Ready for AI-assisted builds.
Ready for autonomous agents.
Ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
71
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
274
Total instances: 0 critical, 31 high, 84 medium, 159 low
31
Rule groups across 4 pillars: 0 critical, 31 high sev. instances
Executive summary
Your Rating API has a composite score of 71.3 out of 100, reflecting a grade of C. The API shows readiness for AI-assisted builds and autonomous agents, but it has significant gaps in standards compliance with a score of 61.5. Documentation, SDK, and MCP readiness scores all fall below expectations, with each needing work. Addressing the 31 high findings across 31 rule groups will be essential for improving overall performance.
Readiness by pillar
Needs work
71 / 100
FoundationThe spec itself
62/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
62Significant gaps
Build Time ReadinessAI writes the code
76/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
74Needs work
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
78Needs work
Runtime ReadinessAgents make the calls
77/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
77Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Rating 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
62 / 100
Elevated risk · Standards compliance
Invalid HTTP Status Codes Detected
You must correct 30 instances of invalid HTTP status codes to prevent toolchain failures and ensure proper SDK generation.
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
76 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You should improve parameter descriptions to ensure coding assistants build accurately without 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 improve accuracy in AI-generated integration code.
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
77 / 100
Elevated risk · MCP readiness
Autonomous agents struggle with API execution
Autonomous agents misinterpret tool names and lack safety semantics, which degrades their ability to execute the Rating API 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