AI Readiness AuditRef. APM-7441F4AB · Confidential
liquidity-api
An independent assessment of whether the liquidity-api specification is ready for AI-assisted integration and autonomous agents, prepared for M 0.
77/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
77
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
555
Total instances: 0 critical, 11 high, 243 medium, 301 low
34
Rule groups across 4 pillars: 0 critical, 11 high sev. instances
Executive summary
Your liquidity-api scores 77 out of 100, reflecting a solid foundation in standards compliance at 90 out of 100, but significant weaknesses in documentation readiness for AI at 59.6 out of 100 and SDK readiness at 77.7 out of 100. Eleven high findings and a total of 34 rule groups with 555 instances reveal areas needing immediate attention. Your API faces gaps for AI-assisted builds and is not ready for autonomous agents. Prioritizing improvements in documentation will be the most impactful step forward.
Readiness by pillar
Needs work
77 / 100
FoundationThe spec itself
90/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
90AI-ready
Build Time ReadinessAI writes the code
69/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
60Significant 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
74/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
74Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the liquidity-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
90 / 100
Managed · Standards compliance
Missing version impacts SDK generation
You should address the missing `version` property in the OpenAPI specification to ensure proper toolchain functionality.
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
69 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The liquidity API lacks essential parameter descriptions, leading to incorrect assumptions and potential integration failures.
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
74 / 100
Elevated risk · MCP readiness
Autonomous Agents Struggle with API Execution
The audit team found that agents misinterpret tool names and lack safety semantics, which degrades the API's reliability.
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