Browser, terminal, and repo workers.
Run browser checks, terminal tasks, and repo edits with logs, diffs, screenshots, and preview output.
Launch workers →early terminal access
Drop an email for the private devnet build. No dashboard spam. Just drops, keys, and early routes.
Route work, run checks, and hand back a real preview. c0de gives builders one surface for browser execution, terminal runs, and deploy-ready artifacts.
one rail / every stack
A tighter product story: one route in, multiple execution surfaces out. Browser, terminal, model routing, and preview handoff live in the same flow.
Run browser checks, terminal tasks, and repo edits with logs, diffs, screenshots, and preview output.
Launch workers →Switch between frontier, open-weight, and local lanes with deterministic routing and clean fallbacks.
Route models →Scoped devnet keys, private endpoints, and early routes for teams that want controlled access.
Get key →Describe the build, get an isolated workspace, browser QA, a live preview, and an artifact route you can hand off.
Open builder →drop-in api
A simple request shape for routing work, running checks, and returning a preview route with artifact metadata.
const run = await fetch("https://api.c0de.network/v1/execute", {
method: "POST",
headers: {
"content-type": "application/json",
"x-api-key": process.env.C0DE_KEY
},
body: JSON.stringify({
route: "c0de-agent-1",
input: "build, test, and deploy",
tools: ["browser", "terminal", "wallet", "repo"]
})
}).then((r) => r.json());
execution flow
Queue the brief once, send it through browser and terminal work, and hand back a preview route with logs attached.
Accept the brief, pick the route, run checks, and seal the artifact without bouncing between surfaces.
access tiers
Start with free runs, move to private lanes, and unlock higher worker counts when the flow starts to matter.
Free
Pro
Ultra
devnet opens soon
If the product feels useful, the next step should be obvious: open the console, run a command, and inspect the preview.