Livepeer Agent · For orchestrators

Put your orchestrator on the Livepeer Agent

If you run a go-livepeer orchestrator, you can offer your capabilities to the Livepeer Agent and earn from agent traffic. It's four steps, all on your side — no code from us, no meetings. Here's exactly what to do.

You need a staked go-livepeer orchestrator on Arbitrum mainnetTime ~30 min if your node already serves the capability

The four steps

  1. Run go-livepeer v0.9.0 as an orchestrator

    On -network=arbitrum-one-mainnet, with a staked on-chain identity (your ethOrchAddr). This is the community / live-runner plane — the same one the currently-live orchestrators use.

  2. Serve each capability at POST /<capability-name>

    One route per capability, named exactly after the capability (e.g. POST /kokoro-tts). Follow the input convention:

    InputHow it arrives
    Text (prompts)prompt in the JSON body
    Media in (image / audio / video)source_url — a public https URL
    Outputa media URL (or an inline data: URL); JSON/text for analysis caps

    Not /generate — that's a different (fal-app) convention. The route name must equal the capability name.

  3. Advertise on /discovery — clean names, capacity, and a price

    Expose https://<your-host>:<port>/discovery. For every capability it must show:

    • a clean app name = the capability name — never a livepeer-example/* scaffold name;
    • capacity_available > 0;
    • a wei price_info — a real number. null means we can't settle payment, so we can't route to you.

  4. Self-test each runner

    Before you announce, run each capability once with the app-examples live-runner client and confirm it returns a real result. An advertised-but-unhealthy runner is the single most common reason onboarding stalls — it passes discovery but errors on the real call. Clear this and the rest is instant.

Announce it

In the Livepeer Discord's orchestrator-onboarding channel, run /announce and fill in the form. Have these ready (copy, replace with your details):

Discovery URL: https://YOUR-HOST:PORT/discovery
Contact email: you@example.com
Note: caps = cap-a, cap-b, cap-c · on-chain 0xYOUR_ORCH_ADDRESS · arbitrum-one-mainnet

Your healthy capabilities are registered on the agent within seconds and become routable via merit (price + capacity + latency). A per-capability admission list keeps a shared capability serving only vetted nodes — yours included, once you're in.

No Discord? Send the same four values (discovery URL, contact email, capability list, on-chain address) to a Livepeer Agent admin and they'll onboard you directly.

What "healthy" means

CheckPass looks like
Discovery reachableGET /discovery returns 200 with your runners
Priced + has capacityevery runner: wei price_info set, capacity_available > 0
Serves for reala paid call returns a real result (not a 502 / empty)
First render is a little slower. A cold node's first request spends a moment on the payment handshake before rendering — that's normal and has generous headroom now. If a first call ever cancels quickly, warm the runner and retry.
Once you're live, the onboarding channel posts a weekly digest of who's serving and who just joined. Questions? Ask in the orchestrator-onboarding channel.