$HEADLESS SYSTEMS
03 / Scorecard / Communications

OneSignal

D
Headless Index
38/100
denominator 80
JAIRF
74.2/100
AI-Aware
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
OneSignal remains a dashboard-first product with a limited programmatic surface. The Headless Index thesis-fit score of 38/100 sits in the lower band of the index, and JAIRF v1.0.0 puts it at 74.2/100 (Level 2, AI-Aware). In practice, vendors at this tier ship enough API to be useful but not enough to be operated end to end by agents without a human in the loop, and the rest of this verdict explains where OneSignal lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. OneSignal is push notification, email, SMS, and in-app messaging platform. The REST API covers apps, devices, notifications, segments, templates, and subscriptions. SDKs in Node, Python, Java, PHP, Ruby, .NET, plus most mobile platforms.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at documentation.onesignal.com. OpenAPI references exist; schema discoverability is solid.[2] An agent cannot drive this product end to end today: the headless surface covers basic CRUD but tapers out before reaching the workflows that matter most. On headless operability: Apps, players (devices), notifications, segments, templates, and outcome tracking are programmable through REST. The OneSignal dashboard handles marketing workflows.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party OneSignal MCP server. The product is well-suited to MCP wrapping given its straightforward REST surface.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: OneSignal is not a strong target for agent-driven workflows today. The weakest link is MCP posture[5], and the broader surface gives agents too little to operate against. Pick it only when the rest of your stack already mandates it. Use only when locked in.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent5/20
scored

OneSignal is push notification, email, SMS, and in-app messaging platform. The REST API covers apps, devices, notifications, segments, templates, and subscriptions. SDKs in Node, Python, Java, PHP, Ruby, .NET, plus most mobile platforms.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 55 operations
  • ·GraphQL endpointDiscovered at https://onesignal.com/api/graphql, introspection disabled or scoped
  • SDKs maintainedNone detected in vendor org
cite (3)
  • openapi.url@2026-05-21
  • graphql.url@2026-05-21
  • github.sdks@2026-05-21
Headless operation10/20
scored

Apps, players (devices), notifications, segments, templates, and outcome tracking are programmable through REST. The OneSignal dashboard handles marketing workflows.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·API operations exposed55 operations in OpenAPI spec
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-21
  • docs.pages_crawled@2026-05-21
  • docs.pages_crawled@2026-05-21
  • docs.topics_found.setup@2026-05-21
  • docs.topics_found.billing@2026-05-21
  • docs.topics_found.teams@2026-05-21
  • docs.topics_found.cli@2026-05-21
  • docs.topics_found.schema@2026-05-21
MCP & agent posture0/20
scored

No first-party OneSignal MCP server. The product is well-suited to MCP wrapping given its straightforward REST surface.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • Community MCP serversNone found
  • Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (3)
  • mcp.registry_query@2026-05-21
  • mcp.github_search_query@2026-05-21
  • github.sdks@2026-05-21
Schema observability15/20
scored

REST documented at documentation.onesignal.com. OpenAPI references exist; schema discoverability is solid.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://documentation.onesignal.com/openapi.json (OpenAPI 3.1.0, 55 operations)
  • ·GraphQL introspectionGraphQL endpoint at https://onesignal.com/api/graphql but introspection is disabled, scoped, or behind authentication
cite (2)
  • openapi.url@2026-05-21
  • graphql.url@2026-05-21
Webhooks & eventsUnknown
Unknown

Notification clicked, displayed, and dismissed webhooks. Catalog matches push-first engagement.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-21
JAIRF · 6 dimensions
FCFoundational Compliance
55/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
90.1/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
90.9/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
50/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
39.6/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:D band triggered: HeadlessIndex=38

04 / Embed

Show OneSignal's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Scorenot foundDocumentation completeness and SDK shape (~22 checks)
CLIRank Agent Friendliness64 · FairCLI readiness, docs quality, and overall agent affordances
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL
Jentic ScorecardJAIRF-based scorecard requiring a public OpenAPI specification
THI 38 vs external median 64, delta -26Methodology delta noted — see verdict

THI display 38 vs external median 64 (delta -26). Deviation > 25 points: editor should review whether THI methodology is over-strict or external scorers are over-generous for this vendor.