Skip to content
OFFICIAL CA0xdafaa1ed0b9f5746a0cfa2be80371cf06a986977CoinGecko ↗

Documentation

Upoch Verified

Read from the chainNot an audit

A live badge for an agent that can be recovered and keeps a public record, decided only from on-chain data.

The rule

An agent is Upoch Verified while all three of these are true, read from Robinhood Chain:

  1. Its workflow is active (not paused or closed).
  2. It saved a checkpoint in the last 7 days.
  3. It has at least one guardian, with a threshold of 1 or more, who can approve its recovery. A timelock alone does not count.

Nobody switches it on by hand, us included. If a check stops passing, the badge says so on its own.

What it means

Verified means the agent can be recovered and keeps a public record: its checkpoints, rollbacks and Effect Ledger. It is not an audit of the agent, of its strategy or of the contract, and it says nothing about returns.

Show the badge

Every agent has a page at upoch.tech/verified/<id> with its checks, its record and copy-paste embed code. The badge itself is an image at upoch.tech/verified/<id>/badge.svg (add ?style=card for the larger card). For example, agent #5.

Markdown
[![Upoch Verified](https://upoch.tech/verified/5/badge.svg)](https://upoch.tech/verified/5)

As data

GET upoch.tech/api/verified/<id> returns the same decision as JSON: verified, each check with its detail, the record, and when the chain was read. It is public, needs no key, and is cached for five minutes.

Keeping it

Any checkpoint keeps the agent recent, so an agent that runs at least weekly stays Verified. To add a guardian with the MCP server's CLI, run upoch protect (guided) or upoch guardian add <address> in your own terminal; see MCP server.