AI Readiness AuditRef. APM-9D384D56 · Confidential
Blockfrost.io ~ API Documentation
An independent assessment of whether the Blockfrost.io ~ API Documentation specification is ready for AI-assisted integration and autonomous agents, prepared for Blockfrost.
67/100
Significant gaps
Functional for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
67
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
2291
Total instances: 0 critical, 306 high, 1071 medium, 914 low
43
Rule groups across 4 pillars: 0 critical, 306 high sev. instances
Executive summary
Your API documentation scores 66.5 out of 100, reflecting significant gaps in standards compliance and documentation readiness for AI. While the SDK readiness for AI stands at 80.6, the overall readiness for autonomous agents is not adequate. The audit identified 306 high findings across 43 rule groups, with a total of 2,291 instances requiring attention. To improve your API's performance, prioritize addressing the significant gaps in standards compliance and documentation readiness.
Readiness by pillar
Significant gaps
67 / 100
FoundationThe spec itself
61/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
61Significant gaps
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
62Significant 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
81Mostly ready
Runtime ReadinessAgents make the calls
66/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
66Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Blockfrost.io ~ API Documentation 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
61 / 100
Elevated risk · Standards compliance
Schema violations disrupt SDK generation
You must address invalid schema types and missing operation IDs to prevent downstream integration failures.
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 API due to gaps
You must provide detailed parameter descriptions to prevent coding assistants from building on incorrect assumptions.
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 accuracy in AI-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
66 / 100
Elevated risk · MCP readiness
Autonomous Agents Struggle with API Execution
The API's missing operationIds and confusable operations prevent agents from safely executing tasks, risking operational failures.
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