epho spins up claude code, codex, or opencode in the cloud. you POST a message, the work streams back. no sdk, no daemon, no infra on your side.
POST /v1/chat { "harness": "codex", "message": "Write a haiku about the ocean.", "provider_api_key": "sk-proj-••••••••" }
$ epho explain --how-it-works
one request boots a fresh cloud environment with the harness you picked, hands it your message, and pipes everything back to you as it happens.
┌───────┐ │ you │ └───────┘
┌────────┐ │ epho │ └────────┘
┌─────────────┐ │ claude code │ ├─────────────┤ │ codex │ ├─────────────┤ │ opencode │ └─────────────┘
01
one endpoint, one json body. pick a harness, write a message, pass your provider_api_key.
02
epho spins up a fresh cloud environment with your harness installed and drops the message in.
03
the response streams back over sse — tool calls, edits, the final answer. like stdout over http.
$ epho features --why
the whole product is one endpoint and good defaults. everything below falls out of that.
that's the api. if you can write json, you've finished the docs.
swap harnesses with one field. same request shape, different brain.
your provider key goes with the request. your tokens, your provider bill — epho never sits between you and the model.
pass -N and watch. server-sent events from first byte to done.
agents run on our boxes. close your lid, board your flight — it keeps typing.
it's just http. pipe it into github actions, cron, a discord bot, five lines of bash.
$ epho compare raw-sandbox
you can absolutely run claude code yourself on a raw sandbox — e2b, daytona, a vm you rent. people do. here's what you sign up for.
need full machine control? use a sandbox. need work done? use epho.
$ epho pricing --per-second
you pay what the sandbox underneath costs — epho adds nothing on top while in beta. the meter runs from boot to teardown and stops when the run does. nothing idles, nothing is stored, nothing keeps billing.
default instance: 2 vCPU · 4 GiB · 10 GiB ≈ $0.0000543/s · a one-minute run ≈ $0.0033
starting credit: $20 on signup — roughly 100 hours of the default instance
model tokens: never billed by epho. they ride on your provider_api_key, at your provider's price.
$ epho api --spec
copy it, swap in your key, change the message. you're now running coding agents in the cloud.
$ epho faq
you don't need one — it's a single POST. if you really want typed helpers, paste the curl into your favorite llm and ask. it'll manage.
you do. the request carries your provider_api_key, so tokens land on your provider bill at your provider's price. no markup, no middleman.
sandbox time, at cost — metered from boot to teardown. size the box yourself with the instance key. every run reports its own cost_usd in the final event.
whatever the harness does on your machine: read repos, write code, run tests, iterate on failures. it just does it in the cloud, on demand, in parallel.
sure — fire off as many requests as you want. each one gets its own isolated environment. fan out as wide as your keys allow.
it's used for the run and nothing else. each environment is torn down when the agent finishes.
$ epho keys create
two minutes from now you could be watching an agent work from your terminal.