AI Readiness AuditRef. APM-EB9C506C · Confidential
Address API
An independent assessment of whether the Address API specification is ready for AI-assisted integration and autonomous agents, prepared for Bring.
62/100
Significant gaps
Functional for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach Mostly ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
62
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
449
Total instances: 0 critical, 43 high, 183 medium, 223 low
36
Rule groups across 4 pillars: 0 critical, 43 high sev. instances
Executive summary
Your Address API scores 61.8 out of 100, reflecting significant gaps and a grade of D. The API shows weaknesses in standards compliance at 50 out of 100 and documentation readiness for AI at 56 out of 100, while SDK readiness for AI scores 77.4 out of 100 and MCP readiness stands at 69.5 out of 100. The API functions for AI-assisted builds but is only partially ready for autonomous agents. Prioritizing improvements in standards compliance and documentation will drive the most impact.
Readiness by pillar
Significant gaps
62 / 100
FoundationThe spec itself
50/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
50Not ready
Build Time ReadinessAI writes the code
67/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
56Significant 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
77Needs work
Runtime ReadinessAgents make the calls
70/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
70Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Address 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
50 / 100
Active risk · Standards compliance
Fix Spec Violations to Prevent Breaks
You must define the `schema` or `content` for Parameter Objects to avoid breaking toolchains and integrations.
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
67 / 100
Elevated risk · Documentation readiness for AI
AI Readers Misinterpret API Documentation
You must improve parameter descriptions; 28 parameters lack sufficient detail, leading AI readers to build 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 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
70 / 100
Elevated risk · MCP readiness
Autonomous Agents Misidentify API Operations
Autonomous agents misidentify two API operations due to confusing tool names, risking incorrect execution and potential failures in the address API.
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