AI Readiness AuditRef. APM-E56F8B45 · Confidential
1Kosmos BlockID Platform API
An independent assessment of whether the 1Kosmos BlockID Platform API specification is ready for AI-assisted integration and autonomous agents, prepared for 1Kosmos.
84/100
Mostly ready
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
84
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
645
Total instances: 0 critical, 83 high, 367 medium, 195 low
26
Rule groups across 4 pillars: 0 critical, 83 high sev. instances
Executive summary
Your API, the 1Kosmos BlockID Platform API, scored 83.7 out of 100, reflecting a mostly ready status with a grade of B. The API excels in standards compliance with a score of 99.3, but documentation readiness for AI, SDK readiness for AI, and MCP readiness all require significant improvement. The audit identified 83 high findings across 26 rule groups and 645 instances, revealing gaps for AI-assisted builds and confirming that the API is not ready for autonomous agents. Prioritizing improvements in documentation and SDK readiness will be essential for achieving full readiness.
Readiness by pillar
Mostly ready
84 / 100
FoundationThe spec itself
99/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
99AI-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
71Needs 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
79Needs work
Runtime ReadinessAgents make the calls
78/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
78Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the 1Kosmos BlockID Platform 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
99 / 100
Managed · Standards compliance
Address Spec Violations for Toolchains
We found minor spec violations that may affect SDK generation and downstream integrations; addressing these will ensure smoother operations.
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 documentation gaps
You must provide detailed 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 return incorrect types and formats
You should address the ambiguous schema layer to ensure accurate responses in identity integrations.
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
78 / 100
Elevated risk · MCP readiness
Agents struggle to execute API calls
The operation descriptions lack essential content, which confuses agents and degrades their ability to execute identity functions effectively.
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