Registration Without a Human
RFC 7591. Section 10.9.3 — if every new agent needs a developer to fill in a portal form and paste a key, the provider has no agent onboarding path regardless of what its docs claim. `console_or_sandbox` and `sign_up_present` measure the HUMAN onboarding path only; this is the machine one. Costs ONE JSON KEY rather than a probe: `registration_endpoint` is a field of the discovery document the pipeline already fetches and saves on 889 providers. APPENDED AT SLOT 18. Dimension order is positional in DIM_ORDER and the glyph.
How it is scored
One signal, read from what the provider publishes, worth 6 points of the 139 in the agent-readiness score.
| Signal the scorer reads | Points |
|---|---|
a `registration_endpoint` in the served RFC 8414 / OIDC discovery document | 6 |
Top providers
The top 500 of 752 providers publishing this signal, ranked by credit earned, ties broken by composite.
The other 18 dimensions
github.com/api-evangelist/<provider>, and each check above names the exact artifact it
reads. Publish the artifact, open a pull request, and the next scoring run picks it up — no gatekeeping
and no fee. The full rubric is at apis.io/rating/, and
prioritized profiling
is the fast lane if you would rather have it done for you.
Scored on rubric v0.17.2 across 27,504 providers · lists rebuilt 2026-09-01 · capped at the top 500 per page.