AI Readiness Audit
Ref. APM-196F52F4 · Confidential

HealthSherpa Public API

An independent assessment of whether the HealthSherpa Public API specification is ready for AI-assisted integration and autonomous agents, prepared for HealthSherpa.

Prepared for
HealthSherpa
Subject
HealthSherpa Public API v0.1.0
Scope
17 operations · 4 pillars · 3 groups
Date
October 2026
41/100
Not ready
Functional for AI-assisted builds.
Ready for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Reference could not be resolved.. Import tools reject the specification outright until it is fixed, so nothing downstream can be generated regardless of the other pillar scores. While this gate is open, the Standards Compliance score is capped at 40 and every AI pillar weights standards at 60% (normally 30%). Fixing the blocker in Phase 1 lifts the caps; the score projection below shows what that unlocks.

3
Critical blockers stopping entire operation groups for agents
1417
Total instances: 3 critical, 9 high, 604 medium, 801 low
29
Rule groups across 4 pillars: 3 critical, 9 high sev. instances
Executive summary

Your API contains one blocking violation that prevents any SDK, documentation, or MCP generators from importing it, which is the most critical issue to address. The overall composite score of 41 out of 100 indicates that your API is not ready, with particularly low scores in standards compliance at 26.7 and documentation readiness for AI at 42.1. While the API is functional for AI-assisted builds, it is not ready for full integration due to 29 rule groups and 1417 instances of findings, including three critical and nine high findings. Fixing the blocking violation is essential for moving forward.

Readiness by pillar
Not ready 41 / 100
FoundationThe spec itself
27/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
27Not ready
Build Time ReadinessAI writes the code
47/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
42Not ready
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
51Not ready
Runtime ReadinessAgents make the calls
51/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
51Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
41
Not ready
Phase 1fix criticals
75
Needs work
Phase 2+ fix highs
96
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the HealthSherpa Public 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

What these gaps cost you in production

4 failure modes across 3 groups, each driven by your audit scores. Several are active risks today.

Foundation The spec itself 27 / 100
Active risk · Standards compliance
Spec Violations Disrupt API Functionality
You must resolve reference paths and define required schema properties to prevent toolchain failures and integration issues.
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 47 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret HealthSherpa API details
Sparse and generic documentation leads to incorrect assumptions, risking integration failures.
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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
You must clarify the schema layer to prevent integration issues in health data handling.
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 51 / 100
Active risk · MCP readiness
Autonomous Agents Struggle with API Execution
Autonomous agents misinterpret tool names and lack safety semantics, which jeopardizes effective API execution in health services.
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

What's inside the full report

Unlock the full report

Book a free call to view the full report and the roadmap our team recommends to upgrade your developer and agentic experience.

Book a free call to view the full report