AI Readiness AuditRef. APM-C052B364 · Confidential
Refinitiv Eikon Refinitiv Data Platform APIs
An independent assessment of whether the Refinitiv Eikon Refinitiv Data Platform APIs specification is ready for AI-assisted integration and autonomous agents, prepared for London Stock Exchange Group.
92/100
AI-ready
Ready for AI-assisted builds.
Ready for autonomous agents.
Ready for autonomous agents.
Resolve all findings (through Phase 1) → score reaches 100 · AI-ready
F
D
C
B
A
92
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
297
Total instances: 0 critical, 0 high, 63 medium, 234 low
18
Rule groups across 4 pillars: 0 critical, 0 high sev. instances
Executive summary
Your API scores 92 out of 100, demonstrating strong readiness for AI-assisted builds and autonomous agents. The API excels in standards compliance with a score of 96.8, and SDK readiness stands at 94.2. However, documentation readiness for AI needs work, scoring only 78.7. To maximize the API's potential, prioritize improving documentation quality.
Readiness by pillar
AI-ready
92 / 100
FoundationThe spec itself
97/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
97AI-ready
Build Time ReadinessAI writes the code
86/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
79Needs 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
94AI-ready
Runtime ReadinessAgents make the calls
96/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
96AI-ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix mediums & lows
About this report. We evaluated the Refinitiv Eikon Refinitiv Data Platform 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
97 / 100
Managed · Standards compliance
Minor spec violations affect integrations
We found a few instances of spec violations that may disrupt SDK generation and downstream 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
86 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API details due to sparse documentation
You should refine descriptions and examples to improve understanding and accuracy in the payments domain.
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 occasionally
You should refine the schema layer to ensure accurate formats and structures in 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
96 / 100
Managed · MCP readiness
Autonomous Agents Face Minor Execution Issues
We found that autonomous agents occasionally struggle with tool names and context budgets, but overall MCP readiness remains strong.
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