Overview

What Epoche does

The CLI packages your source, checks it locally, and encrypts it for a reviewer running in a confidential container. A passing review produces a signed credential tied to the exact source bundle, and a description of your endpoints written by the reviewer from the code it just read. Deployment adds evidence connecting that bundle to the image and the live runtime.

Building something other than an investment strategy? Explore Beyond investing for private apps, general agent services, and future certification domains.

Certification domains

A review answers one question well rather than every question vaguely. Each domain is its own review with its own rules, and you ask for the ones that fit what your agent does. Most agents want one. An agent that holds other people’s money wants several.

• 01

  Execution Integrity

  What the code is allowed to do. Dependencies are pinned and reproducible, secrets are not baked in, network destinations are declared, and nothing downloads and runs code at runtime. Start here: it is the review every other domain assumes.

  epoche register execution
• 02

  Privacy Integrity

  What happens to the data people send you. Whether input ends up in logs, whether it is written to disk, and whether every outbound destination is one you declared.

  epoche register privacy
• 03

  Capital Integrity

  Where the money can go. Every asset, venue and operation is named in a mandate the investor agreed to, proceeds land where that mandate says, spending limits survive a restart, and the owner can withdraw without anyone’s help.

  epoche register capital
• 04

  Accreditation Integrity

  Who is allowed to fund you. Every path that admits capital checks the investor first, and a check that cannot be completed admits nothing.

  epoche register accreditation
• 05

  Strategy Substance

  Whether the strategy you describe is the strategy you built. You declare the signals, the decision procedure and the risk controls; the review looks for each one in the code.

  epoche register strategy
• 06

  Historical Robustness

  Whether your reported numbers came from the code that trades. The backtest is part of the submission, and the review checks it evaluates the same decision procedure your agent runs.

  epoche register historical
• 07

  Accredited Custody

  Whether the capital you hold came from investors whose accreditation was checked. Reported alongside Accreditation Integrity, with the block it was measured at.

  Coming soon
• 08

  Vault Integrity

  For pooled, accredited-only strategies. Deposits admit only attested addresses, a stated fund-movement floor is enforced on chain, and the strategy’s logic is reviewed under an expanded rubric. A different claim from Capital Integrity, and named differently so it cannot be read as the same one. See Building for accredited investors.

  Coming soon

The workflow

1. 01

   Describe the agent

   epoche init creates a config file describing your agent and which review to run.

2. 02

   Check before submission

   epoche check runs deterministic policy checks locally, without uploading source.

3. 03

   Register for review

   epoche register safety sends your code for a confidential review.

4. 04

   Deploy to your own Azure

   epoche deploy self-hosted builds the reviewed source into an image, runs it in your Azure subscription, and registers the live runtime on Base.

5. 05

   Get found, and find others

   The reviewer’s description of your endpoints is published and indexed, so other agents can find you. epoche search searches the same index from your side.

Two deployment plans

Both plans run in your Azure subscription through your local Azure CLI session. Epoche never receives those credentials. Azure bills the subscription. Epoche charges service credit for the review.

Discovery

A passing review does two things. It gives you a credential, and it publishes a description of your endpoints — written by the reviewer from the code it just read, checked by a second pass against that same code, and bound by hash to the release. Other agents search those descriptions.

epoche search "mean reversion on USDC/WETH with hourly cadence" \
  --certified capital --live

import { findCapability } from "@epoche/agent-sdk";

const candidates = await findCapability("momentum strategy on Base, weekly redemption", {
  requireCertifications: ["capital", "strategy-substance"],
  requireLiveRuntime: true,
});

Fetch the description document, hash it, and compare: it either matches what the release committed to or it does not. The index runs that same check before it indexes anything, and repeating it means not having to trust the index. The CLI guide covers both sides in full.

Install

The CLI is an npm package. It needs Node 22 or later. Install it once, then run it from the folder that holds your agent.

npm install -g @epoche/agent-sdk
epoche init
epoche check

Continue with the CLI guide for sign-in, review, results, deployment, and billing.