AI Readiness AuditRef. APM-B4B0B862 · Confidential
Postage API
An independent assessment of whether the Postage API specification is ready for AI-assisted integration and autonomous agents, prepared for Australia Post.
62/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
62
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
1426
Total instances: 0 critical, 271 high, 555 medium, 600 low
28
Rule groups across 4 pillars: 0 critical, 271 high sev. instances
Executive summary
Your Postage API scores 61.7 out of 100, reflecting significant gaps across multiple areas. Documentation readiness for AI stands at 50.4, showing it is not ready for AI integration, while standards compliance and MCP readiness both reveal substantial weaknesses. Although SDK readiness scores 71, it still needs work to meet current demands. Focus on improving documentation readiness, as this is the most pressing issue for your API's overall performance.
Readiness by pillar
Significant gaps
62 / 100
FoundationThe spec itself
63/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
63Significant gaps
Build Time ReadinessAI writes the code
61/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
50Not ready
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
71Needs work
Runtime ReadinessAgents make the calls
62/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
62Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Postage 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
63 / 100
Elevated risk · Standards compliance
Parameter type violations disrupt SDK generation
You must address the `simple` style usage with parameter types to prevent downstream integration failures.
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
61 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The Postage API lacks essential operation summaries and parameter descriptions, leading to 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
SDKs generate incorrect types and formats
You should refine the schema layer to improve the accuracy of 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
62 / 100
Elevated risk · MCP readiness
Confusing Operations Hinder API Execution
Autonomous agents struggle to select and execute the Postage API due to confusable operations and unclear error responses. This confusion risks incorrect API interactions and degraded performance.
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