AI Readiness AuditRef. APM-8F7635F2 · Confidential
RIS::Stations
An independent assessment of whether the RIS::Stations specification is ready for AI-assisted integration and autonomous agents, prepared for Deutsche Bahn API Marketplace.
74/100
Needs work
Ready 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
74
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
776
Total instances: 0 critical, 30 high, 176 medium, 570 low
30
Rule groups across 4 pillars: 0 critical, 30 high sev. instances
Executive summary
Your API, RIS::Stations, scores 73.5 out of 100, which indicates it needs work. The API shows significant gaps in standards compliance and documentation readiness for AI, with scores of 69.7 and 66.5, respectively. While the SDK readiness for AI stands strong at 89.4, the MCP readiness requires attention with a score of 70.4. To improve your API's performance, prioritize addressing the documentation gaps.
Readiness by pillar
Needs work
74 / 100
FoundationThe spec itself
70/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
70Significant gaps
Build Time ReadinessAI writes the code
78/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
67Significant 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
89AI-ready
Runtime ReadinessAgents make the calls
70/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
70Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the RIS::Stations 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
70 / 100
Elevated risk · Standards compliance
Header type violations disrupt SDK generation
You must address the header type issue to prevent downstream integration failures and ensure compliance.
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
78 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
You must improve documentation clarity and detail 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
70 / 100
Elevated risk · MCP readiness
Confusable Operations Impact API Execution
The autonomous agents misidentify two operations, which may lead to incorrect API calls and degraded performance in the stations domain.
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