Toolhouse Workers API

The Toolhouse Workers API (historically the "Agents API") enables HTTP execution of any deployed Toolhouse worker. Workers defined via the Agent Editor or as code are reachable at https://agents.toolhouse.ai/{agent_id} with POST to start a new task, PUT /{agent_id}/{run_id} to continue an existing conversation, and GET /{agent_id}/{run_id} to retrieve full history. NDJSON variants under /ndjson/ stream the worker's output plus out-of-band tool-call and debug signals. Conversation continuity is keyed by the X-Toolhouse-Run-ID response header. Attachments are supported via URL (30-second download timeout) or base64-encoded direct upload (10 MB max per attachment). Public workers require no authentication; private workers use HTTPBearer with a Toolhouse API key.

API entry from apis.yml

apis.yml Raw ↑
aid: toolhouse:workers-api
name: Toolhouse Workers API
tags:
- AI Agents
- AI Workers
- Attachments
- Conversations
- Execution
- Statefulness
- Streaming
humanURL: https://docs.toolhouse.ai/toolhouse/developers/workers-api
baseURL: https://agents.toolhouse.ai
properties:
- url: https://docs.toolhouse.ai/toolhouse/developers/workers-api
  type: Documentation
- url: https://docs.toolhouse.ai/toolhouse/developers/authentication
  type: Authentication
- url: https://docs.toolhouse.ai/toolhouse/developers/worker-statefulness
  type: Documentation
- url: https://docs.toolhouse.ai/toolhouse/developers/attachments
  type: Documentation
description: The Toolhouse Workers API (historically the "Agents API") enables HTTP execution of any deployed
  Toolhouse worker. Workers defined via the Agent Editor or as code are reachable at https://agents.toolhouse.ai/{agent_id}
  with POST to start a new task, PUT /{agent_id}/{run_id} to continue an existing conversation, and GET
  /{agent_id}/{run_id} to retrieve full history. NDJSON variants under /ndjson/ stream the worker's output
  plus out-of-band tool-call and debug signals. Conversation continuity is keyed by the X-Toolhouse-Run-ID
  response header. Attachments are supported via URL (30-second download timeout) or base64-encoded direct
  upload (10 MB max per attachment). Public workers require no authentication; private workers use HTTPBearer
  with a Toolhouse API key.