dokimo verify

    1

    Verify Dokimo revenue evidence packages by recomputing Merkle proofs and checking on-chain anchors on Base.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    dokimo verify

    Example session with this skill installed

    Verify this Dokimo package: {"leaf": "0xabc...", "proof_path": [["0xdef...", "L"]], "root": "0x123...", "rule_version_commitment": "0x789...", "summary": "...", "binding": "..."}

    • Read your context and instructions
    • Compiled the dokimo verify

    I have processed the Dokimo evidence package provided. I first performed a local recomputation of the Merkle root to ensure internal consistency and then queried the Dokimo anchor service for the Base blockchain status.

    Verification Result

    CheckStatusDetails
    Local RecomputePASSRecomputed root matches the package root.
    On-chain AnchorPASSCommitment (root, rule version, and summary) is anchored on Base.
    Close Versionv2Summary and binding fields present; checked as a v2 close.
    IntegrityConsistent (this record)The record is consistent with the provided proof path.

    This record's proof reaches the root, and Dokimo reports that the commitment is anchored on Base. This verdict covers this one specific record. Note that this is Dokimo's unsigned answer. To avoid relying solely on the endpoint, you can check the anchor yourself at https://dokimo.augaster.com/verify.html. This verification does not confirm the close's total revenue or that all records were included in the set.

    Next steps

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Check whether one AI agent revenue record in a Dokimo evidence package matches its committed root and on-chain anchor, without hand-written hashing or blockchain indexing. This skill provides a technical bridge to the Dokimo protocol, allowing an agent to validate Merkle proofs and on-chain anchors for revenue closes on the Base network. It helps when one agent receives a revenue claim from another; each check covers one record, and the verdict is Dokimo's unsigned answer.

    What it does

    • Structure validation checks for required fields like leaf, proof_path, root, and rule_version_commitment.
    • Local recomputation executes recompute_merkle_root to ensure the record and proof are internally consistent without network calls.
    • Anchor verification queries the Dokimo endpoint to confirm the commitment is recorded on the Base blockchain.
    • Discovery dokimo_agent_card fetches Dokimo's public agent card (what Dokimo can verify).
    • Version handling automatically differentiates between legacy v1 packages and modern v2 closes containing summary and binding fields.

    How it works

    1. The user provides a Dokimo evidence package for a specific revenue record.
    2. The agent validates the presence of all required cryptographic fields for the specific close version.
    3. A local Merkle root recomputation is performed to detect any local tampering or malformed proofs.
    4. With user consent, the agent calls the Dokimo public endpoint to verify the on-chain anchor on Base.

    Frameworks & tools

    This skill requires the dokimo-mcp server installed via pip. It interacts with the Dokimo public API and the Base blockchain.

    Why this beats prompting it yourself

    Writing the logic to correctly recompute Merkle roots and navigate dual-version proof shapes is error-prone. This skill handles the specific cryptographic requirements of the Dokimo protocol, and it asks before sending anything to Dokimo.

    Use cases

    • Validating a revenue record received from a partner agent during a transaction.
    • Detecting tampered evidence packages where the proof path does not match the root.
    • Checking that one record's commitment is anchored on Base.

    Known limitations

    This skill verifies only one record at a time. It does not recompute total close amounts, detect omitted records, or perform a full financial audit.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    • Free with an Agensi account

    Requires

    Dokimo MCP

    Listed2 days ago

    What's inside

    Frequently Asked Questions