# OneSignal — API Agent Score

> Score: 67/100 (Grade: C) | Domain: onesignal.com | Rubric: 1.0.0 | Checked: July 24, 2026

OneSignal scored 67/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/onesignal)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 67/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 44/100 (F)
- Agent Discovery: 98/100 (A+)
- Agent Understanding: 71/100 (B)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — 2/2 enums are named types (not bare strings). Investigated: sdk 100%.
- [pass] Security & governance hygiene — security.txt valid at https://onesignal.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Changelog published — Newest official SDK activity 3 day(s) ago. Investigated: sdk 100%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt is 80,560 characters (between 50,000 and 100,000; consider splitting). Investigated: docs 94%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/onesignal, 7532 snippets). Investigated: docs 100%, cli 100%, sdk 67%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 50 sampled pages convert to over 100K chars (max 4047K HTML → 100K markdown (96% boilerplate)). Investigated: docs 80%.
- [pass] Docs structured data — JSON-LD Article markup on 19/19 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

OneSignal's API design is a clear strength — the contract is well-structured and machine-readable, giving partners a solid foundation to build against. However, the partner program is held back by two critical gaps: partners have no self-service path to a first working call (no portal, no quickstart, no inline code samples), and AI agents lack the runnable examples and idempotency guidance they need to execute reliable workflows without human intervention. Closing the onboarding and agent-usability gaps should be the immediate priority to make the program genuinely self-serve for both human developers and the agents they deploy.