AI Readiness Audit
Ref. APM-7C1395EF · Confidential

Fordefi API

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

Prepared for
Fordefi
Subject
Fordefi API v0.2.0
Scope
76 operations · 4 pillars · 3 groups
Date
October 2026
35/100
Not ready
Functional for AI-assisted builds.
Not ready for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Invalid callback key found.. 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
13479
Total instances: 1 critical, 3726 high, 3022 medium, 6730 low
61
Rule groups across 4 pillars: 1 critical, 3726 high sev. instances
Executive summary

Your API cannot generate any SDKs, documentation, or MCPs due to a blocking violation in the specification. The overall composite score of 34.9 out of 100 indicates significant weaknesses, particularly in standards compliance with a score of 22, and documentation readiness for AI at 34.1. While the API is functional for AI-assisted builds, it is not ready for autonomous agents, as evidenced by 3,726 high findings across 61 rule groups. To move forward, you must address the blocking violation to enable any further development.

Readiness by pillar
Not ready 35 / 100
FoundationThe spec itself
22/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
22Not ready
Build Time ReadinessAI writes the code
43/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
34Not 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
52Not ready
Runtime ReadinessAgents make the calls
38/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
38Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
35
Not ready
Phase 1fix criticals
51
Not ready
Phase 2+ fix highs
96
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Fordefi 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 22 / 100
Active risk · Standards compliance
Spec Violations Disrupt Payments API Functionality
You must address critical spec violations that break toolchains and SDK generation, impacting downstream integrations for the Fordefi 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 43 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You must provide detailed parameter descriptions to prevent incorrect assumptions in payment processing.
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
You must clarify the schema layer to prevent integration failures in the payments domain.
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 38 / 100
Active risk · MCP readiness
Autonomous agents cannot execute payments API
The Fordefi API's operation descriptions lack necessary content, causing agents to misinterpret requests and fail to execute transactions safely.
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