AI Readiness AuditRef. APM-B98628A0 · Confidential
They Said So Quotes API
An independent assessment of whether the They Said So Quotes API specification is ready for AI-assisted integration and autonomous agents, prepared for They Said So Quotes.
69/100
Significant gaps
Gaps 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
69
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
775
Total instances: 0 critical, 317 high, 227 medium, 231 low
33
Rule groups across 4 pillars: 0 critical, 317 high sev. instances
Executive summary
They Said So Quotes API scores 68.7/100: Significant gaps · Grade D. The weakest pillar is MCP readiness at 57; the strongest is SDK readiness for AI at 83. We recorded 775 finding instances: 0 critical, 317 high, 227 medium, and 231 low. Gaps 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
Significant gaps
69 / 100
FoundationThe spec itself
74/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
74Needs work
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
58Significant 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
83Mostly ready
Runtime ReadinessAgents make the calls
57/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
57Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the They Said So Quotes 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
74 / 100
Elevated risk · Standards compliance
Spec Violations Disrupt API Integrations
You must address three high-severity spec violations that break toolchains and hinder SDK generation for the Quotes API.
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 parameters
You must provide detailed descriptions for parameters to prevent coding assistants from making 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 return incorrect types and formats
We found that the success response lacks a body schema, which may lead to integration issues.
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
57 / 100
Elevated risk · MCP readiness
MCP Tools Fail to Execute Safely
Autonomous agents cannot select or call the API due to missing operation identifiers and unclear server environments, risking execution errors.
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