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

Integration pattern

Put HarnessRouter behind your own server.

Your backend validates the product user, maps the feature to a configured agent, calls HarnessRouter, and returns a product-shaped result.

Flow

Server-side proxy
Browser
  -> POST /api/product-feature
  -> validate product user and tenant
  -> map feature_key to harness_id
  -> call HarnessRouter with HR_API_KEY
  -> return product-shaped stream or JSON

Why

  • Keeps the HarnessRouter API key out of the browser.
  • Lets the product enforce user and tenant ownership.
  • Allows the product to sanitize progress events and generated previews.
  • Preserves one stable UI contract even if the configured agent changes.
Open standard

Putting your backend between the browser and HarnessRouter places it in the Client role of UHP's architecture — the application that wants work done, which the spec itself says can be a product backend. See roles in the UHP Architecture chapter.

Create API Key

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