AI Readiness AuditRef. APM-6EF6D96A · Confidential
Zenvia APIs v2
An independent assessment of whether the Zenvia APIs v2 specification is ready for AI-assisted integration and autonomous agents, prepared for Zenvia.
66/100
Significant gaps
Functional for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
66
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
3919
Total instances: 0 critical, 529 high, 1450 medium, 1940 low
61
Rule groups across 4 pillars: 0 critical, 529 high sev. instances
Executive summary
Zenvia APIs v2 scores 66/100: Significant gaps · Grade D. The weakest pillar is MCP readiness at 59; the strongest is SDK readiness for AI at 79. We recorded 3919 finding instances: 0 critical, 529 high, 1450 medium, and 1940 low. Functional for AI-assisted builds. Not ready 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
66 / 100
FoundationThe spec itself
66/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
66Significant gaps
Build Time ReadinessAI writes the code
70/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
61Significant 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
79Needs work
Runtime ReadinessAgents make the calls
59/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
59Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Zenvia APIs 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
66 / 100
Elevated risk · Standards compliance
API specifications violate standards compliance
You must address seven high-severity issues that disrupt toolchains, 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
70 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API parameters due to lack of detail
You must provide comprehensive descriptions for parameters to ensure accurate understanding and prevent assumptions during builds.
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 should refine the schema layer to improve accuracy in AI-generated 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
59 / 100
Elevated risk · MCP readiness
MCP Tools Cannot Execute API Safely
Autonomous agents cannot select or call the Zenvia APIs due to missing operation identifiers and confusing operation names. This limits the agents' ability to execute tasks effectively and safely.
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