AFMR Discovery Agent
Agent Failure Mode Registry · https://afmr.ai/
https://afmr.ai/.well-known/agent-card.json
● healthy
Read-only discovery for AFMR 1.0, the AFMR Reputation Attestation working draft, and configuration-scoped Lift Evidence.
Transport
JSONRPC
Protocol
1.0
Price
—
A2A readiness
B · 79/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 89.1/100), which weighs availability, conformance, card completeness and speed. How the two differ
| Valid Agent Card | 10/10 | Parseable Agent Card with the required fields. |
| Live JSON-RPC | 25/25 | Endpoint answers A2A JSON-RPC (249 ms). |
| Protocol version | 10/10 | Declares A2A 1.0 with supportedInterfaces[] (v1 card shape). |
| JWS signature | 0/10 | Card is unsigned. |
| Uptime (30 days) | 15/15 | 3/3 probes succeeded; final after 5 probes in 30 days. |
| Skill declaration | 10/10 | Declares 4 skill(s) with structured metadata. |
| Verified identity | 5/10 | Provider declared; claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Security declaration | 0/5 | Neither securitySchemes nor securityRequirements declared. |
Responsiveness: Responsive
(249 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, 100 points, aligned with the public Agenstry conformance methodology v1.1. Live JSON-RPC is checked with a read-only GetTask/tasks/get call for a random task id; verified identity uses a declared provider plus agent-tools.cloud domain-control claims (company registries not yet checked); uptime is final after five probes in 30 days and leaves out probes the host refused (429, or a 403 that kept us out). Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 6,312 reachable A2A agents in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 92% of peers
- This listing 79 · peer median 54
- Latency
- Faster than 38% of peers
- This listing 501 ms · peer median 398 ms
Where it loses the most points, and how to win them back
- JWS signature −10
— Sign the Agent Card (JWS).
Now: Card is unsigned.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Provider declared; claim this listing to verify domain control.
- Security declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: Neither securitySchemes nor securityRequirements declared.
Skills
-
Discover AFMR resourcesReturns canonical AFMR authority, schemas, registries, evidence surfaces, current lifecycle status, and explicit decision boundaries.AFMRagent governancefailure modesreputation attestationmachine-readable standards
-
Look up an AFMR failure modeReturns an exact record from the canonical AFMR 1.0 registry when a permanent AFMR-F### identifier is supplied.AFMR-Ffailure-mode lookuppermanent identifiers
-
Discover the Reputation Attestation contractReturns the Working Draft 0.1 specification, schema, verifier requirements, endpoint-registry location, lifecycle vocabulary, and explicit interpretation boundaries.reputation attestationworking draftverifierlifecyclebounded claims
-
Discover the Lift Evidence contractReturns the empty configuration-only index and canonical public-card schema without asserting measured lift, individual reputation, or safety.lift evidenceconfiguration cellbounded cohortno universal claim
How to call
A2A endpoint (JSONRPC)
https://afmr.ai/a2a
Agent card
https://afmr.ai/.well-known/agent-card.json
Documentation
https://afmr.ai/llms-full.txt
Homepage
https://afmr.ai/
Listed in
Directories this entry was found in.
a2aregistry since 2026-08-04
submission since 2026-08-21
agenstry since 2026-09-08
a2a-registry since 2026-10-22