HarnessRouter

Navigate HarnessRouter

Search the site

  • HarnessRouter Community EditionOpen-source agent harness infrastructure and the Unified Harness Protocol.Product
  • Harness catalogSupported harness IDs and source-backed integration references.Harnesses
  • Care Prep BenchmarkThe same task compared across Codex, Claude Code, and Hermes configurations.Benchmarks
  • Harness rankingsPublic attributed usage across reviewed agent harnesses.Product
  • ExamplesSee how agent-backed features return finished work inside a product.Product
  • PricingPlans and usage pricing for HarnessRouter.Product
  • Hermes AgentAn open-source, persistent AI agent with memory, reusable skills, built-in tools, browser automation, scheduled tasks, and subagents.Harnesses
↑↓ Navigate↵ OpenEsc Close
Sign up

API reference

Handle retries without starting duplicate agent work.

Every initial runtime request should include an idempotency key. Reuse it only when retrying the exact same request.

Idempotency

  • Generate a fresh UUID for each new runtime task.
  • Reuse the same key only for transport retries of that same request.
  • If a stream drops after response.created, recover from the session instead of sending a new task.

HTTP errors

Errors are JSON responses shaped like { "detail": "..." } with standard HTTP codes. Common cases include 400 for invalid body, 401 for bad or missing key, and 404 for missing or inaccessible resources.

Open standard

The JSON detail bodies and standard HTTP codes described here correspond to UHP's Errors chapter, which specifies the error envelope, a closed set of codes, and which failures are worth retrying. See the UHP Errors chapter.

Create API Key

Ready to run this against a live workspace? Keys take under a minute.