AI Readiness Audit
Ref. APM-25A296F3 · Confidential

Cargo API

An independent assessment of whether the Cargo API specification is ready for AI-assisted integration and autonomous agents, prepared for Rappi Cargo.

Prepared for
Rappi Cargo
Subject
Cargo API v3.0
Scope
22 operations · 4 pillars · 3 groups
Date
October 2026
41/100
Not ready
Gaps for AI-assisted builds.
Partially ready for autonomous agents.
Resolve all findings (through Phase 3) → score reaches 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 2 blocking violations: Invalid callback key found., The definition for path parameter used in the path URL does not exist.. Import tools reject the specification outright until they are fixed, so nothing downstream can be generated regardless of the other pillar scores. While this gate is open, the Standards Compliance score is capped at 40 and every AI pillar weights standards at 60% (normally 30%). Fixing the blockers in Phase 1 lifts the caps; the score projection below shows what that unlocks.

2
Critical blockers stopping entire operation groups for agents
802
Total instances: 2 critical, 42 high, 477 medium, 281 low
47
Rule groups across 4 pillars: 2 critical, 42 high sev. instances
Executive summary

Your Cargo API cannot generate SDKs, documentation, or MCPs due to two blocking violations in the specification. The overall composite score of 40.8 out of 100 indicates significant weaknesses, particularly in standards compliance at 31.4 and documentation readiness for AI at 40.3. While the API shows partial readiness for autonomous agents, the 47 findings, including 42 high-severity issues, highlight critical gaps that must be addressed. Fixing the blocking violations is the single most important action to take for any further development.

Readiness by pillar
Not ready 41 / 100
FoundationThe spec itself
31/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
31Not ready
Build Time ReadinessAI writes the code
44/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
40Not ready
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
48Not ready
Runtime ReadinessAgents make the calls
49/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
49Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
41
Not ready
Phase 1fix criticals
58
Significant gaps
Phase 2+ fix highs
70
Needs work
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Cargo 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

What these gaps cost you in production

4 failure modes across 3 groups, each driven by your audit scores. Several are active risks today.

Foundation The spec itself 31 / 100
Active risk · Standards compliance
Critical Spec Violations Disrupt Integrations
The Cargo API contains invalid callback keys and undefined path parameters, breaking toolchains and SDK generation before AI processing.
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 44 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You risk building on incorrect assumptions as parameter descriptions are often missing or too brief.
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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
The Cargo API's ambiguous schema leads to integration code shipping wrong types, risking data integrity and functionality.
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 49 / 100
Active risk · MCP readiness
Autonomous Agents Misidentify Cargo Operations
The Cargo API's operations confuse autonomous agents, risking incorrect execution and compromising safety during runtime.
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

What's inside the full report

Unlock the full report

Book a free call to view the full report and the roadmap our team recommends to upgrade your developer and agentic experience.

Book a free call to view the full report