AI Readiness AuditRef. APM-7D7DCF1A · Confidential
GrabFood
An independent assessment of whether the GrabFood specification is ready for AI-assisted integration and autonomous agents, prepared for Grab.
51/100
Not ready
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
51
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
1322
Total instances: 0 critical, 206 high, 490 medium, 626 low
51
Rule groups across 4 pillars: 0 critical, 206 high sev. instances
Executive summary
GrabFood scores 51.2/100: Not ready · Grade F. The weakest pillar is Standards compliance at 36; the strongest is SDK readiness for AI at 63. We recorded 1322 finding instances: 0 critical, 206 high, 490 medium, and 626 low. Gaps for AI-assisted builds. Partially 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
Not ready
51 / 100
FoundationThe spec itself
36/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
36Not ready
Build Time ReadinessAI writes the code
57/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
51Not 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
63Significant gaps
Runtime ReadinessAgents make the calls
62/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
62Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the GrabFood 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
36 / 100
Active risk · Standards compliance
Spec Violations Disrupt Toolchains and Integrations
You must address six high-severity spec violations that break SDK generation and downstream integrations in the GrabFood 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
57 / 100
Active 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 the GrabFood API.
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 clarify the schema layer to prevent integration issues in the GrabFood 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
62 / 100
Elevated risk · MCP readiness
Confusing Operations and Request Body Issues
Autonomous agents struggle to select and execute the GrabFood API due to confusing operation names and improper request body formats. These issues hinder effective API interactions and could lead to execution failures.
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