AI Readiness AuditRef. APM-ABF729B8 · Confidential
Kaleyra.io SMS APIs
An independent assessment of whether the Kaleyra.io SMS APIs specification is ready for AI-assisted integration and autonomous agents, prepared for Kaleyra.
76/100
Needs work
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
76
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
210
Total instances: 0 critical, 60 high, 80 medium, 70 low
33
Rule groups across 4 pillars: 0 critical, 60 high sev. instances
Executive summary
Your API scores 75.5 out of 100, reflecting a need for improvement. The API meets standards compliance with a score of 87.7, but documentation readiness for AI reveals significant gaps at 68. The SDK shows a mostly ready status at 83.2, while MCP readiness falls short at 56.8. The most pressing action is to address the documentation and MCP gaps to enable autonomous agent functionality.
Readiness by pillar
Needs work
76 / 100
FoundationThe spec itself
88/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
88AI-ready
Build Time ReadinessAI writes the code
76/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
68Significant 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 Kaleyra.io SMS 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
88 / 100
Managed · Standards compliance
Address missing schema and operation IDs
You should define the required schema for each media type and include unique operation IDs to improve API compliance.
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
76 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The missing parameter object descriptions lead to incorrect assumptions, risking integration failures in SMS services.
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
Autonomous agents cannot execute API calls
The absence of operation IDs and usable server URLs prevents agents from safely interacting with the Kaleyra.io SMS APIs.
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