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

Recover sessions, turns, and generated files.

Use session endpoints after saving `response.metadata.session_id` from the stream.

Endpoints

  • GET /v1/sessions?harness={id}&limit=20
  • GET /v1/sessions/{session_id}
  • GET /v1/sessions/{session_id}/turns
  • GET /v1/sessions/{session_id}/files
  • GET /v1/sessions/{session_id}/files?changed=true
  • GET /v1/containers/{session_id}/files/{file_id}/content
  • GET /v1/sessions/{session_id}/files/archive

Archive

The archive endpoint returns generated artifacts as one zip while preserving folder hierarchy. Use ?changed=true for only the latest turn, or ?files=fid1,fid2 for an explicit file set.

Open standard

Listing sessions and reading turns after a dropped stream uses the inspection endpoints — GET /v1/sessions, /{id}, and /{id}/turns — that UHP defines at conformance class Extended. See the UHP Sessions chapter.

Create API Key

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