Sign documentsyou can prove.

Machine-ready on top. Every Web3 requirement underneath.

• Every user has their own wallet; every transaction is sent and paid from it
• Gas is funded automatically from a treasury, so no one ever holds crypto
• Passkeys follow the WebAuthn standard, with the PRF extension for key unlock
• Documents are encrypted end to end; keys never leave the browser unencrypted
• Zero-knowledge proofs are Groth16, verified on zkVerify mainnet
• Compliance proofs run on the Hubz VCE security-scan circuit
• Records are anchored on Base mainnet, and each anchor names its wallet
• Proof Cards are W3C Verifiable Credentials and SD-JWT VCs, delivered to wallets over OpenID4VCI
• Time locks use drand, randomness published by a threshold of independent operators
• Keys are split with Shamir's secret sharing, so fewer than the set number can't open
• Anonymous answers use Semaphore proofs, each also verified on zkVerify

Everything in the dashboard, as an API.

Receipts, agreements, zero-knowledge proofs, Proof Cards, certificates, sealed calls, releases, vaults, verified forms, and verification. Hash locally, send the fingerprint, get permanent proof. Batched anchoring keeps it at a fraction of a cent.

# create a receipt for an AI agent action
POST /api/v1/receipts
  { "kind": "agent_action", "sha256": "9f86d0…" }

# send an end-to-end encrypted agreement
POST /api/v1/agreements

# prove a fact about it in zero knowledge
POST /api/v1/agreement-proofs

# issue a Proof Card to a person
POST /api/v1/credentials

# certify that a company passed an assessment
POST /api/v1/certificates

# anyone verifies, no key needed
POST /api/v1/verify