Agent readiness · Notification infrastructure
pusher.com
7 of 16 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.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- FAILllms.txt publishedNo llms.txt at any of the 4 locations probed
- PASSDocs readable without JavaScript7,155 characters of text without JS, on https://pusher.com/docs/channels/getting_started/ios/ rather than on https://pusher.com/docs/
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceNo MCP surface: nothing answered at mcp.pusher.com, mcp.pusher.com/mcp, mcp.pusher.com/v1/mcp, api.pusher.com/mcp, /mcp or /api/mcp, and no file mentions MCP
C · Registration
- FAILNo CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML
- PASSSignup reachable without a browserForm renders in server HTML at https://dashboard.pusher.com/accounts/sign_up
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 4 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://pusher.com/channels/pricing/: "Sandbox Free"
E · Integration
- PASSTyped SDK on the registrypusher@5.3.4 ships types, matched from the registry by who publishes it rather than by a link on your site
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://pusher.com/docs/, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
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 pusher.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.