AI Readiness AuditRef. APM-8343CD20 · Confidential
Signicat
An independent assessment of whether the Signicat specification is ready for AI-assisted integration and autonomous agents, prepared for Signicat.
71/100
Needs work
Functional for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach Mostly ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
71
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
435
Total instances: 0 critical, 5 high, 209 medium, 221 low
28
Rule groups across 4 pillars: 0 critical, 5 high sev. instances
Executive summary
Signicat scores 70.9/100: Needs work · Grade C. The weakest pillar is Documentation readiness for AI at 64; the strongest is SDK readiness for AI at 87. We recorded 435 finding instances: 0 critical, 5 high, 209 medium, and 221 low. Functional for AI-assisted builds. Not ready for autonomous agents. Every finding lives in the specification, and the roadmap in this report orders the fixes by impact; resolving them projects the score to 100/100.
Readiness by pillar
Needs work
71 / 100
FoundationThe spec itself
67/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
67Significant gaps
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
64Significant 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
87AI-ready
Runtime ReadinessAgents make the calls
68/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
68Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Signicat 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
67 / 100
Elevated risk · Standards compliance
Property Type Violations Disrupt Integrations
You must address property value mismatches in the OpenAPI specification, as they break toolchains and hinder SDK generation.
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 due to gaps
The missing or insufficient parameter descriptions prevent coding assistants from accurately understanding the identity API, leading to flawed assumptions in 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
Managed · SDK readiness for AI
SDKs generate incorrect types occasionally
You should refine the schema layer to improve accuracy in 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
68 / 100
Elevated risk · MCP readiness
Autonomous agents cannot execute API calls
The Signicat identity API lacks JSON request/response formats and has non-object request body roots, which confuses agents.
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