AI Readiness AuditRef. APM-B73E37D9 · Confidential
Nomos API
An independent assessment of whether the Nomos API specification is ready for AI-assisted integration and autonomous agents, prepared for Nomos.
79/100
Needs work
Gaps 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
79
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
107
Total instances: 0 critical, 7 high, 56 medium, 44 low
29
Rule groups across 4 pillars: 0 critical, 7 high sev. instances
Executive summary
Your Nomos API scores 78.8 out of 100, reflecting a solid foundation but significant areas for improvement. Standards compliance stands strong at 92.9, while documentation readiness for AI reveals significant gaps with a score of 64.4. SDK readiness for AI is promising at 87.9, but MCP readiness also shows significant gaps at 63.1. Addressing the documentation and MCP readiness issues is essential for enabling AI-assisted builds and ensuring autonomous agents can effectively make calls.
Readiness by pillar
Needs work
79 / 100
FoundationThe spec itself
93/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
93AI-ready
Build Time ReadinessAI writes the code
76/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
64Significant 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
88AI-ready
Runtime ReadinessAgents make the calls
63/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
63Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Nomos 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
93 / 100
Managed · Standards compliance
Missing operation IDs affect integrations
You should add unique operation IDs to the operation objects to ensure smooth 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
76 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret Nomos API details
You must provide clear descriptions for parameters to prevent 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
Managed · 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
63 / 100
Elevated risk · MCP readiness
MCP Tools Cannot Execute API Safely
Autonomous agents cannot select or call the Nomos API due to missing operation identifiers and unclear response documentation. This confusion risks improper execution and degraded 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