A2A Agent Card
The provider serves a machine-readable agent discovery manifest at the A2A well-known path (/.well-known/agent-card.json, RFC 8615), advertising its identity, capabilities, skills, endpoint and auth. Weighted above agent_skills despite low adoption for a structural reason: an agent card is the only agent surface in this rubric that CANNOT be derived on a provider's behalf — it is served from the provider's own host or it does not exist. Where mcp_server, agent_skills and agentic_access can all credit an artifact API Evangelist authored, this one is provider-published by construction, and so is immune to the provenance defect that distorts the others.
How it is scored
One signal, read from what the provider publishes, worth 8 points of the 139 in the agent-readiness score.
| Signal the scorer reads | Points |
|---|---|
a2a/<slug>-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 | 8 |
Grades and what each earns
This dimension is graded rather than pass/fail: how the signal was evidenced decides what fraction of the points it earns.
| Grade | Credit | Points | Providers |
|---|---|---|---|
| conformant | 1.0× | 8.0 | 26 |
| near-conformant | 0.6× | 4.8 | 17 |
| flavored | 0.25× | 2.0 | 53 |
| invalid | 0.0× | 0.0 | 0 |
Top providers
All 96 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.