AI Readiness AuditRef. APM-877D54D1 · Confidential
Conversations API v2
An independent assessment of whether the Conversations API v2 specification is ready for AI-assisted integration and autonomous agents, prepared for tyntec.
64/100
Significant gaps
Gaps for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
64
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
758
Total instances: 0 critical, 78 high, 275 medium, 405 low
40
Rule groups across 4 pillars: 0 critical, 78 high sev. instances
Executive summary
Your Conversations API v2 scores 63.9 out of 100, reflecting significant gaps across multiple areas. Standards compliance scored 60.5, documentation readiness for AI scored 63.2, SDK readiness for AI scored 65.6, and MCP readiness scored 68.1, all showing room for improvement. The audit identified 78 high findings across 40 rule groups, with 758 instances needing attention. To address these weaknesses, prioritize closing the gaps for AI-assisted builds to improve overall readiness.
Readiness by pillar
Significant gaps
64 / 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
64/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
63Significant 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
66Significant gaps
Runtime ReadinessAgents make the calls
68/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
68Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Conversations API v2 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
Specification violations disrupt toolchains and integrations
You must address invalid HTTP status codes and undefined schema properties to ensure proper functionality.
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
64 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret Conversations API details
You must improve 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
Elevated risk · SDK readiness for AI
SDKs generate incorrect types and formats
You must address the ambiguous schema layer to ensure accurate responses in the Conversations API.
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
68 / 100
Elevated risk · MCP readiness
Autonomous agents misinterpret API operations
You must address confusable operation names and missing JSON media types to ensure safe execution.
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