Onboarding Descriptor Published
0.28.0 (roadmap#987). How an agent gets in without a person: an API Onboarding Descriptor names the signup, registration mechanisms, credential bootstrap and first call. `console_or_sandbox` and `sign_up_present` measure the human path; dynamic_client_registration measures one mechanism; this measures whether the whole path is declared. Absence scores false, not na: every provider with an API can publish one, and apis.io drafts it for them (generate_artifact api-onboarding). KYA acceptance (the descriptor's verification[]) is deliberately not credited until roadmap#989 observes third-party adoption. APPENDED, after mcp_tool_quality; not drawn in the glyph.
How it is scored
One signal, read from what the provider publishes, worth 3 points of the 159 in the agent-readiness score.
| Signal the scorer reads | Points |
|---|---|
the provider page carries onboarding_descriptor.published (an APIOnboarding pointer, provider- or API-level, or a saved /.well-known/api-onboarding body with an `aod` key, build.py _onboarding_descriptor_meta) | 3 |
Top providers
All 41 providers publishing this signal, ranked by credit earned, ties broken by composite.
The other 24 dimensions
artifacts.apis.io/<provider>/, and each check above names the exact artifact it
reads. Publish the artifact, open an issue on github.com/api-evangelist/<provider> pointing at it, and the next scoring run picks it up — no gatekeeping
and no fee. The full rubric is at apis.io/rating/, and the
Influence plan is the fast lane if you would rather
work your own listing through the API — remediation, projections and re-check requests.
Scored on rubric v0.28.1 across 43,745 providers · lists rebuilt 2026-11-21 · capped at the top 500 per page.