AI Readiness AuditRef. APM-06AE33C0 · Confidential
Agentcard API
An independent assessment of whether the Agentcard API specification is ready for AI-assisted integration and autonomous agents, prepared for Agentcard.
82/100
Mostly 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
82
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
833
Total instances: 0 critical, 14 high, 331 medium, 488 low
35
Rule groups across 4 pillars: 0 critical, 14 high sev. instances
Executive summary
Your Agentcard API scored 81.5 out of 100, reflecting a mostly ready status. The API meets standards compliance well at 89.2 but shows weaknesses in documentation readiness for AI at 70.4 and SDK readiness for AI at 79.8. With 14 high findings among 35 rule groups and 833 instances, the API has gaps for AI-assisted builds and is partially ready for autonomous agents. Addressing the documentation and SDK readiness will significantly improve your API's performance.
Readiness by pillar
Mostly ready
82 / 100
FoundationThe spec itself
89/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
89AI-ready
Build Time ReadinessAI writes the code
75/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
70Needs work
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
80Needs work
Runtime ReadinessAgents make the calls
83/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
83Mostly ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Agentcard 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
Residual risks to monitor
No active failures, but elevated risks remain. Continued improvement will bring these into the managed band.
Foundation
The spec itself
89 / 100
Managed · Standards compliance
Address Empty Enumeration Items and References
We found empty enumeration items and undefined schema properties, which may disrupt SDK generation and 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
75 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API details due to gaps
You must provide complete parameter descriptions to improve understanding and reduce 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 improve accuracy in AI-generated integration code.
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
83 / 100
Managed · MCP readiness
Clarify API Operations and Error Responses
You should refine the naming of operations and standardize error response formats to improve agent execution and reduce confusion.
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