The world's first unified interface for agent harnessesBacked by Y Combinator
Bring the world's best AI agents into your app, with one API.
Run Codex, Claude Code, Hermes, and more in isolated sandboxes as your product backend. Ship faster, scale reliably, and save costs.
Plus 500 free credits at launch. Limited time.
Launch Partner:
Used by
The problem
Building AI agent backend for takes months.
- sandbox per run
- agent runtime
- tool orchestration
- files & artifacts
- sessions & streaming
- retries & timeouts
- permissions
- cost controls
And the upgrades, fixes, and maintenance never stop.
The solution
We run the AI agent backend. You ship it in minutes.
- Codex
- Claude Code
- Hermes
We take care of the upgrades, fixes, and maintenance for you.
The steps
Build it in three steps.
HR_KEY=sk-hr-••••••••Your user gets work, not words. Start with one harness-powered feature.
Build demo
See it in action.
A Cursor-style coding app, built with the same three steps. Watch the full run from AGENTS.md to a working product.
Use cases
Some AI features your app can ship, and more.
Every one of these is a real request-to-artifact workflow: your user asks inside your product, a harness does the work, and the finished result comes back.
One API- CodexCode, apps and images
- Claude CodeCode, files and documents
- HermesAutonomous, any frontier model
- PiSoonCoding agentSoon
Every harness ready, one API
Scale
Scale without operating the infrastructure.
Run concurrent agent workloads in isolated sandboxes. HarnessRouter provisions and operates the serverless execution infrastructure for you.
Every session runs in its own isolated sandbox. HarnessRouter provisions the runtime on demand, streams events as the run progresses, and returns the finished artifact to your app.
Optimize
Improve performance and control costs.
Trace and compare harness × model combinations across quality, cost, and latency to identify the best setup for each workload.
Same task, same input · Harness × model comparisons
Task benchmark
The lowest-cost successful run saved 99.8% in credits against the costliest configuration, on the same task with the same input. Scores and success rates differ by setup, and results vary by workload.
“We can go from a problem and a plan to an agent in product within 24 hours.”
Readily uses HarnessRouter to bring domain expertise into production agents without rebuilding the agent runtime.
Q&A
The question everyone asks first.
What exactly is a harness?
An LLM returns tokens. A harness gives it a sandbox, tools, and a loop, so it returns the actual file. GPT-5.2 and Claude Opus 4.8 are LLMs. Codex and Claude Code are harnesses. A harness also carries the agent's configuration: its instructions, which model it runs, and what it is allowed to do.
Why not just use Codex or Claude directly?
You should. Use them to build your app or tools. But they work for you, at your desk, not for your users. HarnessRouter puts them to work for your users, inside your product. Your app sends a task through one API and gets back finished work: videos, games, codebases, docs, and more. Your users never touch a terminal.
How much does it cost?
Create an account, add a card, and get 500 free credits. When you need more capacity, choose Developer, Production, or Scale. Additional usage can draw from purchased top-up credits.
Do I need to understand agents to use this?
No. Drop our AGENTS.md into Cursor or Claude Code, describe your feature, and your coding agent wires everything: the endpoint, the config, the UI. The demos above were built exactly this way.
Am I locked into one harness?
The opposite. That is the point. Your config names the harness: claude-code today, codex tomorrow, or back again, swapped anytime with one line. Your integration code and output schema never change. When a better harness ships next quarter, your product gets better with a config change.
What exactly comes back to my app?
Structured, renderable results: code changes as reviewable diffs, generated files and documents, images, and confirmations of real tool actions like GitHub, Slack, Notion, or internal APIs. Your UI decides how to show them and when the user accepts.
Put agent harnesses to work in your product.
Start with one API. Scale and optimize as your workloads grow.






