Toolhouse

Workers connect to more than a thousand services through built-in integrations Toolhouse maintains and connection-required integrations authorized per service over OAuth through Auth Connections, with the actions a worker may perform chosen per integration; workers also call tools on remote MCP servers over SSE or streamable HTTP with OAuth, and can call third-party APIs from uploaded API documentation in the virtual computer.

SourceToolhouse, docs.toolhouse.ai toolhouse/integrations, auth-connections and mcp-serversread 2026-09-21

A manager worker coordinates specialized workers through the Call Agent integration, deciding which to involve, running them in sequence, in parallel or mixed according to data dependencies, passing one worker's output to the next, and chaining managers to any depth; workers can also trigger other workers as a pipeline. The buyer configures that routing across steps.

SourceToolhouse, docs.toolhouse.ai capabilites/worker-orchestrationread 2026-09-21

Agent Files attach knowledge to a worker, such as guidelines, templates, skill files and reference documents in text or PDF, and their contents are added directly to the worker's instructions, where they persist for every run; the document parser and file download bring further files in per task. No index, graph or embeddings layer over the customer's knowledge that scales past the context window and stays queryable is documented.

SourceToolhouse, docs.toolhouse.ai capabilites/skills-and-knowledge and capabilites/document-parserread 2026-09-21

Agent Builder writes a governance section into each worker's instructions stating what controls apply and when it should stop and escalate, for example drafting a campaign and requiring approval before sending, and a worker can start autonomously and email its owner for approval before continuing. The approval lives in the worker's prompt rather than as a gate the platform enforces before an action runs, so the boundary is stated rather than enforced.

SourceToolhouse, docs.toolhouse.ai introduction-to-ai-workers and toolhouse/worker-emailsread 2026-09-21

Workers reach only the services and actions they are given, through OAuth auth connections scoped per worker and per-integration action selection, a least-privilege tool access model; a worker can be kept private to its owner, API keys are encrypted in transit and at rest, customer data is encrypted, not used for model training and scoped to the workspace, and Enterprise customers can arrange custom authentication models. No identity provider integration such as SSO or SAML, and no attestation or trust center, is published, and the toolhouse.ai footer links only privacy and terms pages.

SourceToolhouse, docs.toolhouse.ai auth-connections, developers/authentication and toolhouse.ai/pricingread 2026-09-21

The Logs page records every worker execution with status, run and user IDs and duration, a trace of each integration call in order with a timing waterfall and its exact input and output, and a history of the worker's intermediate outputs and any approvals or directions a person gave, with log retention stated by plan: 30 days on Business, one year on Business Max and custom on Enterprise.

SourceToolhouse, docs.toolhouse.ai toolhouse/logs and toolhouse.ai/pricingread 2026-09-21

Workers write memories of data, behavior and past outputs through a Memory Store integration and read the relevant ones back through Semantic Memory Search on later runs, with reading and writing separable so a worker can be read-only, and each run keeps its full conversation history under a run ID across chat, email and the API. The documentation states no lifetime for stored memories and no review, edit or deletion surface.

SourceToolhouse, docs.toolhouse.ai capabilites/memory and developers/worker-statefulnessread 2026-09-21

Toolhouse is offered as a hosted service on every plan, Business, Business Max and Enterprise, and neither the pricing page nor the documentation publishes a self-hosted, private cloud, on-premises or region selection option.

SourceToolhouse, toolhouse.ai/pricing and docs.toolhouse.ai; toolhouse.ai/en/pricingread 2026-09-21

Agent Builder assembles each worker from built-in capabilities Toolhouse maintains, among them scraping, web and social search, memory, image generation, vision, a virtual computer and document parsing, and the documentation describes common worker patterns such as briefing, triage and content creation that the customer builds from a prompt; workers an organization has built can be shared with its team. No catalog or named set of ready made workers a customer adopts is documented, so these are assets the customer assembles.

SourceToolhouse, docs.toolhouse.ai readme and introduction-to-ai-workersread 2026-09-21

Schedules start a worker autonomously on a cadence set in natural language or in the interface, as often as every ten minutes and with several schedules per worker, and workers also start on events such as a webhook notification from another service, so work reaches the agent without a person initiating it; each worker also has its own email inbox, a chat interface and an API endpoint, with an optional completion webhook.

SourceToolhouse, docs.toolhouse.ai toolhouse/schedules and introduction-to-ai-workersread 2026-09-21

Every plan includes model usage, described on the pricing page as free unlimited tokens, and neither the pricing page nor the documentation names the models or providers workers run on or lets the customer choose one, so the provider is undisclosed, and nothing documents working across models, routing between them, or bringing one's own provider and keys.

SourceToolhouse, toolhouse.ai/pricing and docs.toolhouse.ai; toolhouse.ai/en/pricingread 2026-09-21

Every worker is callable as an API at its own endpoint, authenticated with a Toolhouse API key: POST starts a task, PUT continues it under a run ID, GET returns the full history, NDJSON endpoints stream tool calls alongside the output, and long virtual computer jobs run in the background for polling.

SourceToolhouse, docs.toolhouse.ai developers/workers-api and developers/authenticationread 2026-09-21

The Testing Workbench runs a new or edited worker on real test inputs so its builder can check the output before use and correct the worker through Agent Builder. No scored test cases, datasets, evaluation harness or quality gate that returns a verdict is documented.

SourceToolhouse, docs.toolhouse.ai toolhouse/quickstart and introduction-to-ai-workersread 2026-09-21

A built-in scraper that Toolhouse maintains, attached when a task needs it, reads web pages at run time with location selection by country, and Vision can capture and read a page screenshot; Toolhouse states the scraper reads pages and does not fill forms or log in, which is web scraping rather than an agent operating a browser. The virtual computer executes Python code rather than operating an interface.

SourceToolhouse, docs.toolhouse.ai capabilites/scraping and capabilites/visionread 2026-09-21