AI Readiness AuditRef. APM-E352AB69 · Confidential
Bastion APIs
An independent assessment of whether the Bastion APIs specification is ready for AI-assisted integration and autonomous agents, prepared for Bastion.
78/100
Needs work
Gaps 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
78
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
3247
Total instances: 0 critical, 581 high, 833 medium, 1833 low
45
Rule groups across 4 pillars: 0 critical, 581 high sev. instances
Executive summary
Bastion APIs scores 77.7/100: Needs work · Grade C. The weakest pillar is Documentation readiness for AI at 66; the strongest is Standards compliance at 86. We recorded 3247 finding instances: 0 critical, 581 high, 833 medium, and 1833 low. Gaps 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
Needs work
78 / 100
FoundationThe spec itself
86/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
86AI-ready
Build Time ReadinessAI writes the code
71/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
76Needs work
Runtime ReadinessAgents make the calls
79/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
79Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Bastion APIs 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
86 / 100
Managed · Standards compliance
Address duplicate schema titles now
You have duplicate schema titles and undefined properties in the required list, which can confuse toolchains and 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
71 / 100
Elevated risk · Documentation readiness for AI
AI Readers Misinterpret Sparse API Descriptions
The documentation for Bastion APIs lacks detailed parameter descriptions, causing AI readers to build on incorrect assumptions. This issue can lead to significant errors in payment processing.
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 ensure accurate integration code for payments.
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
79 / 100
Elevated risk · MCP readiness
Agents misinterpret operation names and descriptions
The Bastion APIs' operation names and descriptions confuse agents, risking incorrect payment processing.
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