CERTEN docs

Build on CERTEN

Proof-gated cross-chain execution on Accumulate. One API key, one hierarchy of authorities, and cryptographic evidence your counterparty can check without trusting you.

What this is

CERTEN is a control plane, not a chain you connect a wallet to. You call an API; it coordinates identity, multi-party authorization, proof generation, and execution across Accumulate and 13 target chains. There is no node to run and no IP address to point at — the surface is https://gateway.kompendium.co and a client library.

Five minutes, start to finish

  1. Get an API key — sign in at gateway.kompendium.co/portal. Self-service, no ticket.
  2. Install the client — npm install -g @certen.io/cli or npm install @certen.io/sdk
  3. Make a signing key — certen keys generate --name dev. It never leaves your machine.
  4. Create an identity you control — certen identity create --name my-org --sign-with dev
npm install -g @certen.io/cli
certen keys generate --name dev
certen auth login --api-key ck_live_...
certen identity create --name my-org --sign-with dev
certen identity get <id>        # wait for status=active AND can_sign=true

Drive it from an AI agent

There is a Model Context Protocol server, so an agent can read and act on CERTEN through the same API. It is read-only by default — write tools are not registered at all unless you set CERTEN_MCP_ALLOW_WRITES=1 — and it never holds a signing key.

npm install -g @certen.io/mcp
CERTEN_API_KEY=ck_live_... certen-mcp        # 8 read tools
CERTEN_MCP_ALLOW_WRITES=1 certen-mcp         # adds the write tools, deliberately

Your key never reaches us

Identities are controlled by an Ed25519 key you generate and hold. The SDK takes a sign callback; the CLI keeps an encrypted keystore in ~/.certen/keys. Both send signatures, never private keys — which is why nobody here can act on your behalf.

Verify without trusting us

Every execution produces a proof. Deployed contract addresses are published at GET /v1/chains (public, no key), and a proof holder can mint a revocable share link so a counterparty with no CERTEN account can fetch and check the evidence themselves.

Start here

Getting started

Key, identity, first transaction.

Authentication

API keys, scopes, OAuth.

Idempotency

Why every POST needs a key.

Errors

What the codes mean.

Guides

Onboard an identity

The ADI that signs and holds. Everything needs one.

Sign while holding your own key

The pattern almost every integration uses.

Proof-gate a contract call

Escrow, settlement, anything past a transfer.

M-of-N panels

Arbitration, dual control, break-glass.

Verify a proof

Evidence for someone who should not have to trust you.

Reference

Agent quickstart

Driving Certen from an autonomous agent.

Proof-gated enforcement

What the on-chain gate actually checks.

Webhooks

Events, delivery, retries.

Verify a webhook

Checking the signature.