AI Readiness Audit
Ref. APM-63D071E2 · Confidential

OneSignal REST API

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

Prepared for
OneSignal
Subject
OneSignal REST API v1.2.2
Scope
37 operations · 4 pillars · 3 groups
Date
October 2026
40/100
Not ready
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Resolve all findings (through Phase 3) → score reaches 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: The definition for path parameter used in the path URL does not exist.. 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
1533
Total instances: 1 critical, 51 high, 558 medium, 923 low
48
Rule groups across 4 pillars: 1 critical, 51 high sev. instances
Executive summary

Your API cannot generate SDKs, documentation, or MCPs due to one blocking violation in the specification. The overall composite score of 40 out of 100 indicates significant weaknesses, with standards compliance at 32.6 and documentation readiness for AI at 41. The audit identified 51 high findings and 1 critical finding across 48 rule groups, revealing gaps that prevent AI-assisted builds and render the API unready for autonomous agents. Addressing the blocking violation is the most urgent action to take for any further development.

Readiness by pillar
Not ready 40 / 100
FoundationThe spec itself
33/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
33Not ready
Build Time ReadinessAI writes the code
44/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
41Not 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
47Not ready
Runtime ReadinessAgents make the calls
44/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
44Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
40
Not ready
Phase 1fix criticals
60
Significant gaps
Phase 2+ fix highs
66
Significant gaps
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the OneSignal REST 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 33 / 100
Active risk · Standards compliance
Path Parameter Definitions Are Missing
You must define the path parameter in the path URL to prevent toolchain failures and integration issues in the OneSignal 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 44 / 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 during 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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
The OneSignal REST API's ambiguous schema leads to integration code shipping wrong types, risking functionality in client applications.
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 44 / 100
Active risk · MCP readiness
Autonomous agents struggle with API execution
The autonomous agents cannot reliably select or execute operations due to confusing names, inadequate descriptions, and inconsistent error responses.
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