Let Agents In

Agent readiness · Notification infrastructure

onesignal.com

10 of 15 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.

A · Discovery

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • PASS
    llms.txt publishedllms.txt and llms-full.txt present at https://onesignal.com/llms.txt and https://onesignal.com/llms-full.txt and https://documentation.onesignal.com/llms.txt and https://documentation.onesignal.com/llms-full.txt, and the 12 links we sampled across both files all answer
  • PASS
    Docs readable without JavaScript22,133 characters of text without JS
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • N/A
    Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
  • PASS
    OAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
  • FAIL
    MCP surfaceMCP mentioned 2x in your own files, but nothing answered at mcp.onesignal.com, mcp.onesignal.com/mcp, mcp.onesignal.com/v1/mcp, api.onesignal.com/mcp, /mcp or /api/mcp

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://dashboard.onesignal.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
  • FAIL
    Signup reachable without a browserhttps://dashboard.onesignal.com/signup is reachable, but its form needs JavaScript

D · Provisioning

  • PART
    Programmatic key provisioning1 of 7 provisioning phrases across the 8 documents we read: "service account"
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://onesignal.com/pricing: "Free Plan", "$0", "Developer Friendly Pricing Free"

E · Integration

  • PASS
    Typed SDK on the registry@onesignal/onesignal-vue3@2.5.4 ships types, matched from the registry by who publishes it rather than by a link on your site
  • PASS
    Machine-readable API descriptionDocs serve markdown to machines, at https://documentation.onesignal.com/docs/en/android-sdk-setup

Tell me when this changes

The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.

This page is the newest scan we hold for onesignal.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.

Scan a domain yourself