Back to A2A agents

Decision Anchor

https://a2a.decision-anchor.com/.well-known/agent-card.json
● healthy

Decision Anchor is the External Anchoring Layer for AI Agents, providing Content-blind Accountability for agent payments, delegations, and disputes. Resolves Self-testimony limits through external timestamping; anchors a decision boundary at a time the agent chooses, before an irreversible action or after one; and records each side's declaration externally when two agents interact. Records accountability boundaries, not decision content. Does not monitor, judge, recommend, or intervene. Not a trust scoring system. Not an identity verification system. Not a behavior monitoring service. Not a governance platform.

Transport
JSONRPC
Protocol
1.0
Price
—

A2A readiness

B · 81/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, 88.6/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 (727 ms).
Protocol version 7/10 Declares A2A 1.0 but without supportedInterfaces[] (pre-1.0 card shape).
JWS signature 3/10 Signature present but did not verify: InvalidSignatureError.
Uptime (30 days) 15/15 3/3 probes succeeded; final after 5 probes in 30 days.
Skill declaration 10/10 Declares 6 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 2/5 Declares 1 security scheme(s).
Responsiveness: Responsive (727 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 95% of peers
This listing 81 · peer median 54
Latency
Faster than 22% of peers
This listing 668 ms · peer median 398 ms

Where it loses the most points, and how to win them back

  • JWS signature −7 — Sign the Agent Card (JWS).
    Now: Signature present but did not verify: InvalidSignatureError.
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Provider declared; claim this listing to verify domain control.
  • Protocol version −3 — Support the current protocol revision.
    Now: Declares A2A 1.0 but without supportedInterfaces[] (pre-1.0 card shape).

How many agent tools actually work · All statistics

Skills

How to call

Listed in

Directories this entry was found in.

a2aregistry since 2026-06-24 agenstry since 2026-09-08 a2a-registry since 2026-11-10