Dokimo Verify
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://dokimo.augaster.com/a2a
· transport JSONRPC
Verify a dokimo-merkle-v1 evidence package verify-evidence-package
Send an evidence package { leaf, proof_path, root, rule_version_commitment } (plus summary and binding for a dokimo-anchor-v2 close). Dokimo re-computes the Merkle path from leaf to root and reads the anchor commitment (v2: H("dokimo.anchor.v2" ‖ root ‖ rule_version_commitment ‖ summary_hash)) on the DokimoAnchorRegistry (Base mainnet). Returns Dokimo's unsigned verdict { verified, checks:{recompute, onchain_anchor, rule_version_bound, close_summary}, merkle_scheme, anchor_scheme }: verified is true only if the path recomputes AND the commitment is anchored. To check it yourself, use /verify.html or the reference code at /merkle-spec.html.
verificationauditmerkleon-chainasc-606proof-of-reserves2026-11-02 from https://dokimo.augaster.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.