Solutions

Three ways into amerc.

Consumer, Donor and Hotline: what each is, who it is for, how it works, and how to start.

Consumer Donor amerc-dialog API relay Outpost

Consumer

For people with more work than machines

You bring the work; the network brings the hardware. Start coding-agent sessions on donated machines or your own Outposts, watch the live terminal, take over at any time, and publish what the agent builds.

Enable the consumer role and download the packA ZIP on Windows or tar.gz elsewhere, with your credentials already inside.
Run it onceIt opens one outbound connection to your region node. No public IP or inbound firewall rule.
Start a sessionThe node matches you to a free machine that runs the requested agent and bridges both sides.
Watch, take over, publishLive terminal, shared net disk, and one-step publishing for anything the agent builds.

Get access Downloads Access is by invitation code.

A session, end to end

Your machineconsumer pack, outbound only

amerc nodematches and bridges

A donated machineruns the agent and streams its terminal

Nothing runs on the node itself — it only relays. Sessions are scoped to a pool, and pools can be shared with teammates. use, manage or delegate.

Donor

For anyone with a machine that is on anyway

Lend a machine and an installed agent subscription. Consumer sessions run in a dedicated workspace on your computer and pay you for the capacity, while stopping the donor takes the machine out of rotation.

Ask for the donor roleAn administrator approves it and selects the agent configurations you may serve.
Download the pack for that configurationOne per agent — Codex, Claude Code or Antigravity — with a launcher for your platform.
Run it and leave it runningIt dials home, reports health, and updates when the node ships a new build.
Serve sessions and earnRegular patrols measure reliability; a better score brings more sessions.

Become a donor Downloads

What runs on your machine

Donor programlauncher + your agent CLI

One outbound bridgehealth, patrol and sessions

A consumertypes; you are paid per session

Sessions stay inside a workspace created by the pack. Going offline is supported: the node stops routing new work and ends served sessions cleanly.

amerc-dialog

For anyone who would rather ask than click

The front-page box is an agent with tools on your account. It can register machines, build configured Outposts, publish artifacts and report what happened. Anonymous visitors can use it with fewer tools, and the same engine embeds into your own site as reception.

Ask it somethingType or speak into the front-page dock. No setup or installation.
It calls tools, not just wordsServer tools act on your account; browser tools reach the Outpost on your laptop.
Sign in to widen the toolsetMachines, packages, deployments and artifacts become actions instead of instructions.
Put it on your own siteOne script tag and an embed key; your reception pool answers and traffic is metered by bytes.

Try it on the front page Reception guide

One turn of the loop

You askdock, widget or embed

Hotline agentchooses tools and loops until done

Something changeda machine, a package or a URL

Embedding is a single tag: <script src="/hotline/sdk.js?app=YOUR_KEY"></script>

Underneath all three

Two components are shared by every path above, and either can also be used by itself.

API relay

One OpenAI-compatible key. Every model. Routed to the fastest live provider.

An OpenAI-compatible endpoint — point any existing SDK at it and change the base URL.
Health-probed providers, so dead capacity is routed around instead of returned to you.
Or attach your own provider capacity and earn from other people’s calls.

Read the API docs

Outpost

One download. Unzip, run, and the agent takes it from there.

Your token is baked in. There is nothing to copy or paste.
One executable. Outbound connections only — no public IP, no inbound firewall rule.
It sees the Outpost come online, opens a terminal, and works.

Get the Outpost