router is live · try it

ampere

A compute market for AI agents on Robinhood Chain. Agents pay for answers in amps; strangers' machines produce them; the router bills and audits every job.

agents here have no computers of their own. sell them yours.

enter the floor
checking the router… mechanics router x

Playground

one click — a real job through the router to a stranger's machine
try one:
the answer appears here — with what it cost and how long it took
live · —

— nodes delivered work in 24h

—amps sold this hour
—agent jobs this hour
—canary fails in 24h
—duplicate disagreements in 24h
—nodes registered right now

Delivered work is a measurement. Registered is a claim — registration is free until the phase-2 stake contract (why).

What an amp buys

An amp is 1 000 output tokens, weighted by the class that produced them. The class is what a node serves and what an agent asks for; which weights sit behind it is the node's business, and the audits are what keep that honest.

classweight1 amp buystypically runs on
amp-s0.25×4 000 output tokensa laptop
amp-m0.5×2 000 output tokensa desktop with a gaming GPU
amp-l1×1 000 output tokensa workstation or one datacenter GPU
amp-xl1.5×667 output tokensseveral datacenter GPUs

Recent jobs

jobclassnodemstokensstatus
—

Nodes

The first 100 addresses to deliver a paid answer are recorded here as founding nodes, in order. What founding is worth is set in public before phase 2, not after.

foundingnodeclassjobs 24hokfail
—

Run a node

no open port, no static IP — the node pulls · founding slots open
  1. 01

    Ollama on your machine

    Local mode burns your own cycles. You pick a compute class, not a model — the client pulls the right weights for it on first start. amp-s runs on a laptop.

    brew install ollama
# linux: curl -fsSL https://ollama.com/install.sh | sh
ollama serve
  2. 02

    The client

    Node 24, one small package served from this site. The node signs every request with an address of its own — that is the address phase 2 pays.

    curl -L https://ampereprotocol.xyz/ampere-node.tgz | tar xz
cd ampere-ops && npm ci --omit=dev
  3. 03

    Join the floor

    Any fresh EVM key works — its address is the node's name on the board and the address phase 2 pays, so make a new one and keep it. The client long-polls the router for 25 s at a time, runs what it gets, posts the text back. Behind NAT is the normal case.

    export AMPERE_PRIVATE_KEY=$(node -e \
  "import('viem/accounts').then(m=>console.log(m.generatePrivateKey()))")
AMPERE_ROUTER=https://router.ampereprotocol.xyz \
AMPERE_MODELS=amp-s npm run node

$ampere

phase 3 · not launched

AMPERE / ETH on Pons

Compute is priced in the chain's own money: sell amps of your machine, get paid in ETH. The token is the unit agents pay in and the collateral nodes post to be routed.

40% to holders, in ETH, hourly Merkle claim40% node payout pool20% buy back & burn

Fair launch on the Pons curve: no presale, no team allocation, nothing minted outside the curve. The one privileged wallet is the creator wallet, and it is the reserve that pays the split above. Creator fee on Pons is 0.7% of every trade in the pair; until the distributor contract ships the split is policy v0 — a keeper with a key.

  • Agents burn it. Amps are paid for in AMPERE only, and what agents pay is burned. Usage is supply leaving.
  • Nodes lock it. Phase 2 routes by stake: more AMPERE posted, more jobs; a failed audit slashes it.
  • Fees buy it. A fifth of every hour's creator fee buys AMPERE on the market and burns it.
  • Holders get ETH. Not more of the token — the chain's money. Hold AMPERE, claim ETH every hour the pair earned anything.

There is no contract address yet. Any $AMPERE you are shown today is somebody else's. The launch is announced here and on the router first.

Roadmap

what is live, what is not
  1. phase 1 · live · you are here

    The floor

    • Router, node client, metering — running
    • Playground, starter keys, live board — this page
    • Founding nodes recorded from the first paid answer
  2. phase 2 · next

    Stake and payout

    • Stake-and-slash contract: routing weighted by AMPERE posted
    • Hourly Merkle claim in ETH for holders
    • Founding terms published before the contract, not after
  3. phase 3

    The pair

    • AMPERE / ETH on Pons, creator wallet = reserve wallet
    • Agents pay in AMPERE; what they pay is burned
    • Contract address published here first

Burned cycles cannot be proven. So the network checks behaviour and says so.

  • Signatures and uptime; canaries on 3% of jobs; duplicates on 5%. Detection, not proof.
  • A node that proxies to a cheaper model of the same family is not always caught.
  • Phase-1 balances and payouts are policy v0: a keeper with a key, not a contract.
read the mechanics