AI Readiness AuditRef. APM-7FCE201A · Confidential
Bolt API Reference
An independent assessment of whether the Bolt API Reference specification is ready for AI-assisted integration and autonomous agents, prepared for Bolt Financial.
64/100
Significant gaps
Functional for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Resolve all findings (through Phase 2) → score reaches 100 · AI-ready
F
D
C
B
A
64
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
3086
Total instances: 0 critical, 19 high, 1336 medium, 1731 low
56
Rule groups across 4 pillars: 0 critical, 19 high sev. instances
Executive summary
Bolt API Reference scores 64.1/100: Significant gaps · Grade D. The weakest pillar is Standards compliance at 54; the strongest is SDK readiness for AI at 76. We recorded 3086 finding instances: 0 critical, 19 high, 1336 medium, and 1731 low. Functional for AI-assisted builds. Partially ready for autonomous agents. Every finding lives in the specification, and the roadmap in this report orders the fixes by impact; resolving them projects the score to 100/100.
Readiness by pillar
Significant gaps
64 / 100
FoundationThe spec itself
54/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
54Not ready
Build Time ReadinessAI writes the code
70/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
76Needs work
Runtime ReadinessAgents make the calls
68/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
68Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Bolt API Reference 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
Where you’re exposed – and where you’re not
4 failure modes across 3 groups. Some are active risks; others are under control.
Foundation
The spec itself
54 / 100
Active risk · Standards compliance
Spec Violations Disrupt Payments Integrations
You must address three high-severity spec violations that break toolchains and hinder SDK generation for the Bolt API.
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
70 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You risk coding errors in payment processing because parameter descriptions are missing or too brief.
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 return incorrect types and formats
You should refine the success response to include a body schema to improve integration accuracy.
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
68 / 100
Elevated risk · MCP readiness
Autonomous Agents Struggle with API Execution
Agents cannot select or execute the Bolt API effectively due to unclear operation descriptions and inconsistent error responses. This confusion risks payment processing reliability and user experience.
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