AI Readiness AuditRef. APM-6EE9396B · Confidential
Perform.AI Public API (v5)
An independent assessment of whether the Perform.AI Public API (v5) specification is ready for AI-assisted integration and autonomous agents, prepared for Parcel Perform.
76/100
Needs work
Functional for AI-assisted builds.
Ready for autonomous agents.
Ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
76
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
1698
Total instances: 0 critical, 15 high, 725 medium, 958 low
35
Rule groups across 4 pillars: 0 critical, 15 high sev. instances
Executive summary
Your API, Perform.AI Public API (v5), functions well for AI-assisted builds and is ready for autonomous agents. The API scores 76.3 out of 100, with significant weaknesses in documentation readiness for AI at 68.3 and standards compliance at 75.3. The audit identified 15 high findings across 35 rule groups, revealing 1,698 instances needing attention. Prioritizing improvements in documentation readiness will have the most significant impact on your API's overall effectiveness.
Readiness by pillar
Needs work
76 / 100
FoundationThe spec itself
75/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
75Needs work
Build Time ReadinessAI writes the code
74/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
68Significant gaps
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
79Needs 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 Perform.AI Public API (v5) 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
75 / 100
Elevated risk · Standards compliance
Fix Spec Violations to Ensure Functionality
You must address three high-severity spec violations that disrupt toolchains, SDK generation, and downstream integrations in the Perform.AI Public 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
74 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API parameters due to sparse descriptions
You risk building on incorrect assumptions, which can lead to significant integration issues.
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
Inconsistent Error Responses Confuse Agents
We found multiple error response shapes in the Perform.AI Public API, which may confuse autonomous agents during execution.
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