AI Readiness AuditRef. APM-D2E8C321 · Confidential
Open Targets Platform REST API
An independent assessment of whether the Open Targets Platform REST API specification is ready for AI-assisted integration and autonomous agents, prepared for Open Targets.
85/100
Mostly ready
Functional for AI-assisted builds.
Broken for autonomous agents.
Broken for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
85
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
326
Total instances: 0 critical, 47 high, 150 medium, 129 low
20
Rule groups across 4 pillars: 0 critical, 47 high sev. instances
Executive summary
Open Targets Platform REST API scores 84.7/100: Mostly ready · Grade B. The weakest pillar is MCP readiness at 62; the strongest is Standards compliance at 100. We recorded 326 finding instances: 0 critical, 47 high, 150 medium, and 129 low. Functional for AI-assisted builds. Broken 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
Mostly ready
85 / 100
FoundationThe spec itself
100/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
100AI-ready
Build Time ReadinessAI writes the code
85/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
78Needs work
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
91AI-ready
Runtime ReadinessAgents make the calls
62/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
62Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Open Targets Platform REST 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
Residual risks to monitor
No active failures, but elevated risks remain. Continued improvement will bring these into the managed band.
Foundation
The spec itself
100 / 100
Managed · Standards compliance
Your spec holds up where toolchains depend on it
No significant findings in this area. Score: 100/100.
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
85 / 100
Elevated risk · Documentation readiness for AI
AI readers can't learn the truth of your API
1 critical/high finding group(s) in this area. Score: 78/100.
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
Your schemas support trustworthy generated code
1 critical/high finding group(s) in this area. Score: 91/100.
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
62 / 100
Elevated risk · MCP readiness
Autonomous agents can't safely operate your API
2 critical/high finding group(s) in this area. Score: 62/100.
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