AI Readiness Audit
Ref. APM-4B6B15D9 · Confidential

Togai Apis

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

Prepared for
Togai
Subject
Togai Apis v1.0
Scope
121 operations · 4 pillars · 3 groups
Date
October 2026
48/100
Not ready
Functional for AI-assisted builds.
Not 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 1 blocking violation: The definition for path parameter used in the path URL does not exist.. Import tools reject the specification outright until it is 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 blocker in Phase 1 lifts the caps; the score projection below shows what that unlocks.

1
Critical blocker stopping entire operation groups for agents
3042
Total instances: 1 critical, 58 high, 1480 medium, 1503 low
62
Rule groups across 4 pillars: 1 critical, 58 high sev. instances
Executive summary

Your API, Togai APIs for payments, cannot generate SDKs, documentation, or MCPs due to one blocking violation in the specification. The overall composite score of 47.5 out of 100 indicates significant weaknesses, particularly in standards compliance at 38.3 and documentation readiness for AI at 47.3. While the SDK readiness for AI shows some promise at 59.7, the runtime readiness for autonomous agents remains unprepared. To move forward, you must address the blocking violation to enable any generation from the current spec.

Readiness by pillar
Not ready 48 / 100
FoundationThe spec itself
38/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
38Not ready
Build Time ReadinessAI writes the code
54/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
47Not 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
60Significant gaps
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
48
Not ready
Phase 1fix criticals
65
Significant gaps
Phase 2+ fix highs
70
Significant gaps
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Togai 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

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 38 / 100
Active risk · Standards compliance
Path parameter definitions are missing
You must define all path parameters in the Operation Object to prevent toolchain failures and integration issues.
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 54 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You must provide detailed parameter descriptions to prevent coding assistants from building on incorrect assumptions.
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 ensure accurate integration code for payments.
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 struggle with API execution
Agents cannot select or call the Togai APIs due to missing operation identifiers and confusing operation names, risking payment processing 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

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