AI Readiness AuditRef. APM-6AB0867F · Confidential
0x API
An independent assessment of whether the 0x API specification is ready for AI-assisted integration and autonomous agents, prepared for 0x.
79/100
Needs work
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
79
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
3906
Total instances: 0 critical, 20 high, 1920 medium, 1966 low
32
Rule groups across 4 pillars: 0 critical, 20 high sev. instances
Executive summary
Your API scored 79.3 out of 100, reflecting solid standards compliance at 91 but significant weaknesses in documentation readiness for AI at 68 and SDK readiness at 77.5. Agents encounter 20 high findings among a total of 32 rule groups and 3,906 instances, which limits your API's readiness for AI-assisted builds and prevents autonomous agents from making calls. Addressing the documentation gaps is the most important action to improve overall readiness.
Readiness by pillar
Needs work
79 / 100
FoundationThe spec itself
91/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
91AI-ready
Build Time ReadinessAI writes the code
73/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
78Needs work
Runtime ReadinessAgents make the calls
75/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
75Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the 0x 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
91 / 100
Managed · Standards compliance
Address Spec Violations for Toolchains
We found some spec violations that may affect toolchains and SDK generation; addressing these will improve downstream 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
73 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API parameters' intent
You must provide detailed descriptions for parameters to prevent incorrect assumptions in payments processing.
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 ensure accurate integration code for the payments API.
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
75 / 100
Elevated risk · MCP readiness
Inconsistent Error Responses Confuse Agents
The error responses contain multiple incompatible shapes, which complicates the agents' ability to call the payments 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