AI Readiness AuditRef. APM-5F3B113C · Confidential
Centtrip.PublicApi
An independent assessment of whether the Centtrip.PublicApi specification is ready for AI-assisted integration and autonomous agents, prepared for Centtrip Ltd.
56/100
Significant gaps
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
F
D
C
B
A
56
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
2
Critical blockers stopping entire operation groups for agents
10471
Total instances: 2 critical, 1534 high, 4382 medium, 4553 low
60
Rule groups across 4 pillars: 2 critical, 1534 high sev. instances
Executive summary
Centtrip.PublicApi scores 56.2/100: Significant gaps · Grade D. The weakest pillar is MCP readiness at 49; the strongest is SDK readiness for AI at 71. We recorded 10471 finding instances: 2 critical, 1534 high, 4382 medium, and 4553 low. Gaps 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
56 / 100
FoundationThe spec itself
54/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
54Not ready
Build Time ReadinessAI writes the code
62/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
52Not 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
71Needs work
Runtime ReadinessAgents make the calls
49/100
MCP Readinesscapped · open criticals
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
Phase 1fix criticals
Phase 2+ fix highs
Phase 3+ fix mediums & lows
About this report. We evaluated the Centtrip.PublicApi 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
54 / 100
Active risk · Standards compliance
Your spec breaks before code is even written
6 critical/high finding group(s) in this area. Score: 54/100.
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
62 / 100
Active risk · Documentation readiness for AI
AI readers can't learn the truth of your API
3 critical/high finding group(s) in this area. Score: 52/100.
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
AI-built integrations ship with guessed assumptions
1 critical/high finding group(s) in this area. Score: 71/100.
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 can't safely operate your API
5 critical/high finding group(s) in this area. Score: 49/100.
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