AI Readiness AuditRef. APM-4A7E963F · Confidential
Neuphonic API
An independent assessment of whether the Neuphonic API specification is ready for AI-assisted integration and autonomous agents, prepared for Neuphonic.
80/100
Needs work
Functional for AI-assisted builds.
Broken for autonomous agents.
Broken for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
80
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
655
Total instances: 0 critical, 103 high, 288 medium, 264 low
29
Rule groups across 4 pillars: 0 critical, 103 high sev. instances
Executive summary
Your Neuphonic API scored 79.6 out of 100, reflecting a grade of C and showing that it is functional for AI-assisted builds but broken for autonomous agents. The API meets standards compliance with a score of 89, while documentation readiness for AI and MCP readiness both show significant gaps, scoring 66.1 and 64.7 respectively. With 103 high findings across 29 rule groups and 655 instances, addressing the documentation and MCP readiness will be essential for improving overall performance.
Readiness by pillar
Needs work
80 / 100
FoundationThe spec itself
89/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
89AI-ready
Build Time ReadinessAI writes the code
80/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
66Significant 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
94AI-ready
Runtime ReadinessAgents make the calls
65/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
65Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Neuphonic 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
89 / 100
Managed · Standards compliance
Duplicate schema titles cause confusion
You should address the 43 instances of duplicate schema titles to prevent conflicts in 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
80 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret Neuphonic API data
The missing parameter object descriptions lead to incorrect assumptions, degrading the API's usability and effectiveness.
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
We observe that the schema layer's ambiguity leads to minor issues in generated SDKs and AI-written 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
65 / 100
Elevated risk · MCP readiness
Autonomous agents cannot execute API calls
The Neuphonic API lacks essential server URLs and clear operation descriptions, hindering agent functionality.
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