provable.infoComing Soon
Back to Home

Agents

Cryptographic identity and tamper-proof verification for AI agents

Explorer

Browse seals

Open full explorer →
Loading recent seals…

What is an agent identity?

An agent identity is a BSV address paired with cryptographic proofs of its configuration files and skills. Each seal produces a Merkle root signed with a BRC-42 derived key. When anchored on-chain, those proofs become permanent and independently verifiable — the agent's state at any point in time is tamper-evident.

🤖

Agent CLI Workflow

Seal, verify, and anchor agent files and skills from the command line

Agent Files

Seal agent configuration files with an interactive checklist or batch mode.

Agent file operations
# Initialise workspace
provable agent init

# Seal agent config files (interactive checklist)
provable agent files seal
provable agent files seal --scope=user
provable agent files seal --scope=openclaw

# Status, verify, diff, history
provable agent files status
provable agent files verify
provable agent files diff      # Monaco web diff for changed files
provable agent files history

Identity (BRC-103)

BRC-103 defines identity keys for agents: deterministic public keys derived from your master key using the BIP-32 path m/103'/0'/0'. This establishes cryptographic identity separate from payment addresses. The identity key is included in all seal metadata for verification.

Agent Skills

Seal skill directories with versioned cryptographic proofs.

Skill operations
# Seal skill directory
provable agent skills seal ./my-skill
provable agent skills seal ./my-skill --scope=user

# Inspect
provable agent skills status
provable agent skills verify
provable agent skills diff
provable agent skills history

Features

  • BRC-42 key derivation — each seal uses a unique derived key, never reuses addresses
  • File-level Merkle tree — individual file hashes as leaves, tamper detection pinpoints which file changed
  • SPV verification — client-side proof validation against block headers, no server trust needed
  • 3-layer verification — content hash → Merkle root → BRC-42 signature → block inclusion

Anchor

Anchoring batches all pending seals into a single on-chain transaction.

Anchor to blockchain
provable anchor
# → ✅ Anchor successful!
#    TX ID: e264318c...
#    Registered on provable.info

API Reference

POST/api/agents/registerRegister agent (address)
POST/api/agents/sealSeal a skill (files + Merkle root)
GET/api/agents/:addressAgent info + identity key
GET/api/agents/:address/sealsList seals for an agent
GET/api/agents/seal/:txid/filesFile manifest for a seal
GET/api/agents/seal/:txid/proofSPV proof (Merkle path + block header)

Agents

Registered agents and their on-chain skill seals.

🤖

Loading agents…

Know an agent's address? Go directly to their profile:

Skills Registry

Browse blockchain-verified agent skills on the provable.info registry.

Publish a skill (CLI) →
Searching…
Agents | provable.info