AI Readiness AuditRef. APM-FE453CB3 · Confidential
160.com.au API
An independent assessment of whether the 160.com.au API specification is ready for AI-assisted integration and autonomous agents, prepared for 160.com.au.
84/100
Mostly ready
Gaps for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
84
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
459
Total instances: 0 critical, 19 high, 212 medium, 228 low
33
Rule groups across 4 pillars: 0 critical, 19 high sev. instances
Executive summary
Your API scored 83.5 out of 100, reflecting a mostly ready status with a grade of B. The API excels in standards compliance, achieving a score of 95.3, but shows significant gaps in documentation readiness for AI, with a score of 68.3. Additionally, the API is mostly ready for SDK and MCP with scores of 80.1 and 84.2, respectively. To improve overall readiness, prioritize addressing the documentation gaps for AI.
Readiness by pillar
Mostly ready
84 / 100
FoundationThe spec itself
95/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
95AI-ready
Build Time ReadinessAI writes the code
74/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
68Significant 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
80Mostly ready
Runtime ReadinessAgents make the calls
84/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
84Mostly ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the 160.com.au 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
95 / 100
Managed · Standards compliance
Missing operation IDs disrupt integrations
You should address the missing `operationId` in the operation object to prevent downstream toolchain issues.
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
74 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to 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
Managed · 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
84 / 100
Managed · MCP readiness
MCP Tools Struggle with API Execution
The autonomous agents cannot reliably select or execute operations due to missing operation identifiers and JSON media types.
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