AI Readiness Audit
Ref. APM-28556A13 · Confidential

PeachPayments - API Documentation

An independent assessment of whether the PeachPayments - API Documentation specification is ready for AI-assisted integration and autonomous agents, prepared for Peach Payments.

Prepared for
Peach Payments
Subject
PeachPayments - API Documentation v0.1.0
Scope
128 operations · 4 pillars · 3 groups
Date
October 2026
40/100
Not ready
Gaps 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.

7
Critical blockers stopping entire operation groups for agents
9690
Total instances: 7 critical, 57 high, 4606 medium, 5020 low
68
Rule groups across 4 pillars: 7 critical, 57 high sev. instances
Executive summary

Your API documentation for PeachPayments contains a critical blocking violation that prevents any SDK, documentation, or MCP generators from importing the spec, which is the most significant issue we identified. The overall composite score of 40 out of 100 indicates that your API is not ready, with particularly low scores in standards compliance at 31.1 and documentation readiness for AI at 42.7. We found 68 rule groups with a total of 9,690 instances of findings, including 7 critical and 57 high severity issues. To move forward, addressing the blocking violation is essential for enabling any further development or automation.

Readiness by pillar
Not ready 40 / 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
45/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
43Not 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
47Not ready
Runtime ReadinessAgents make the calls
43/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
43Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
40
Not ready
Phase 1fix criticals
60
Significant gaps
Phase 2+ fix highs
69
Significant gaps
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the PeachPayments - API Documentation 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
Path parameter definitions are missing
The audit team found that undefined path parameters break toolchains and SDK generation, impacting 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 45 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret payment API details
You must provide clear and detailed parameter descriptions to prevent incorrect 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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
The ambiguous schema layer causes integration code to ship with wrong types, risking payment processing failures.
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 43 / 100
Active risk · MCP readiness
Autonomous Agents Misinterpret API Operations
The audit team found that agents misread operation names and security references, risking incorrect payment processing and security breaches.
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