Agentic Index
Toolhouse vs xpander.ai (2026)
Both vendors last verified
Choose Toolhouse for the fastest path from prompt to running agent with tools and RAG included. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Choose xpander.ai for a governed runtime with approvals, audit and memory around the agents you already run. Toolhouse's Business plan costs $500 monthly following a 14 day trial, and xpander.ai offers no free tier, charging Team usage at $0.01 a credit. Both are young platforms, and the split is simplicity versus governed depth.
On the Agentic Index MCP platform ranking, xpander.ai clears the bar and Toolhouse does not. xpander.ai documents all three interoperability capabilities in full; Toolhouse does not document model flexibility and routing in full. 142 of the 554 platforms it grades clear it. See the MCP platform ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Toolhouse and xpander.ai are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Toolhouse if
- Shipping a working agent this week matters more than orchestration depth
- Tools and RAG arriving with the runtime save the assembly work
- One link MCP connectivity covers your integration surface
Choose xpander.ai if
- Persistent memory and multi agent coordination are structural to your product
- Approvals and audit on agents your teams already built are the requirement
- Governed deployment options anticipate your enterprise requirements
| Feature | T Toolhouse |
x xpander.ai |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
ToolhouseIntegrations & Tool Calling Workers connect to more than a thousand services through built in integrations Toolhouse maintains and through integrations that need a connection, 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 |
||
|
xpander.aiIntegrations & Tool Calling Agents hold skills of four kinds, including API connectors from a built-in catalog, connectors generated from the customer's own OpenAPI spec, and remote or local MCP connectors, each governed with actions that can be held for approval. Sourcexpander, docs.xpander.ai/connectors and connectors/add-a-skillread 2026-09-21 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
ToolhouseWorkflow Orchestration 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 customer configures that routing across steps. SourceToolhouse, docs.toolhouse.ai capabilites/worker-orchestrationread 2026-09-21 |
||
|
xpander.aiWorkflow Orchestration A workflow is an agent whose behavior is a graph of nodes instead of a single loop, with node types, branching and human steps. Agents can also call other agents as skills. Sourcexpander, docs.xpander.ai/use/agents/workflowsread 2026-09-21 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
ToolhouseTriggers & Channel Coverage 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 |
||
|
xpander.aiTriggers & Channel Coverage Recurring cron schedules start agents automatically, and agents can book their own one-off re-checks. Work also reaches agents through Slack and Microsoft Teams threads, email, WhatsApp, the API and MCP clients. Sourcexpander, docs.xpander.ai/use/agents/schedules and use/agents/channelsread 2026-09-21 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
ToolhouseKnowledge Grounding & RAG 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 for each task. There is no index, graph or embeddings layer over the customer's knowledge that scales past the context window and stays queryable. SourceToolhouse, docs.toolhouse.ai capabilites/skills-and-knowledge and capabilites/document-parserread 2026-09-21 |
||
|
xpander.aiKnowledge Grounding & RAG Agents attach RAG knowledge bases over the customer's own documents. Documents are added, listed and removed programmatically through the REST API and Python SDK, and the knowledge bases are queried by semantic search. Sourcexpander, docs.xpander.ai/developers/knowledge/document-management and developers/knowledge/semantic-searchread 2026-09-21 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
ToolhouseMemory & State Persistence 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. Toolhouse states no lifetime for stored memories and offers no surface to review, edit or delete them. SourceToolhouse, docs.toolhouse.ai capabilites/memory and developers/worker-statefulnessread 2026-09-21 |
||
|
xpander.aiMemory & State Persistence Memory comes in three scopes. Agent memories are facts the agent always carries across the organization, user memories hold per-user facts that persist across sessions, and session storage keeps conversation history within a thread in Postgres. Sourcexpander, docs.xpander.ai/developers/memory pagesread 2026-09-21 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
ToolhouseHuman Oversight & Guardrails 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, not in a gate the platform enforces before an action runs, so the boundary is stated, not enforced. SourceToolhouse, docs.toolhouse.ai introduction-to-ai-workers and toolhouse/worker-emailsread 2026-09-21 |
||
|
xpander.aiHuman Oversight & Guardrails Risky actions wait for a named person's sign-off. Approval rules and gated commands are set per agent, permission modes apply on each run, connector actions can be held for approval, and approval requests and decisions are recorded on the task. Sourcexpander, docs.xpander.ai/use/approvals and use/agents/permissionsread 2026-09-21 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
ToolhouseSecurity, Identity & Governance Workers reach only the services and actions they are given, through OAuth auth connections scoped per worker and action selection per integration, a least privilege model for tool access. 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. There is no identity provider integration such as SSO or SAML and no attestation or trust center, 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 |
||
|
xpander.aiSecurity, Identity & Governance xpander is SOC 2 Type II certified, with the report available under NDA. Users sign in through the customer's OIDC identity provider, such as Okta, Entra ID or Keycloak, scoped permissions control who may use, edit and share each agent, and credentials can be kept in an external vault. Sourcexpander, docs.xpander.ai/resources/security-compliance/certifications-compliance and run/integrations/identity-providersread 2026-09-21 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
ToolhouseObservability & Auditability 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 |
||
|
xpander.aiObservability & Auditability Each task records the agent's reasoning entries and the parameters it chose for every call, so a failure can be traced to the model, the skill or the prompt. A separate organization audit log records governed actions such as agent changes, skill connections, credential use and sign-ins, with filters, download and retention of 90 or 400 days depending on event type. Sourcexpander, docs.xpander.ai/use/agents/auditread 2026-09-21 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
ToolhouseDeployment & Data Residency Toolhouse is a hosted service on every plan, Business, Business Max and Enterprise, with no 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 |
||
|
xpander.aiDeployment & Data Residency xpander runs on xpander cloud, as a Hybrid deployment with the runtime in the customer's own cluster and the control plane on xpander cloud, or fully air-gapped with every component in the customer's environment. An EKS setup guide is available, and each agent can be placed in a cloud or self-hosted location. Sourcexpander, docs.xpander.ai/self-hosted and run/locationsread 2026-09-21 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
ToolhousePrebuilt Agents, Templates & Packs 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 common worker patterns such as briefing, triage and content creation are ones the customer builds from a prompt. Workers an organization has built can be shared with its team. Toolhouse offers no catalog or named set of ready made workers a customer adopts, so these are assets the customer assembles. SourceToolhouse, docs.toolhouse.ai readme and introduction-to-ai-workersread 2026-09-21 |
||
|
xpander.aiPrebuilt Agents, Templates & Packs xpander ships one built-in agent, Omni, plus a skills registry of skill bundles and a way to import existing agent definitions such as Claude Code agents. Beyond Omni, customers assemble their own agents from these assets, as there is no set of separate ready-made agents. Sourcexpander, docs.xpander.ai/use/skills-registry and use/agents/importread 2026-09-21 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
ToolhouseModel Flexibility & Routing Every plan includes model usage, which Toolhouse calls free unlimited tokens. The models or providers workers run on are not named, the customer cannot choose one, and nothing describes 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 |
||
|
xpander.aiModel Flexibility & Routing Each agent's model is chosen in its configuration from the supported model providers, with the customer's own keys on cloud, hybrid and air-gapped installs. Every model call passes through xpander's AI gateway, which enforces the organization's model policy. Sourcexpander, docs.xpander.ai/run/integrations/ai-vendors and run/integrations/ai-gatewayread 2026-09-21 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
ToolhouseAPIs, SDKs & MCP Extensibility 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 |
||
|
xpander.aiAPIs, SDKs & MCP Extensibility A REST API creates and configures agents, starts runs and reads their record, and manages skills, knowledge and workflows. There is also a Python SDK, and an MCP endpoint with OAuth 2.1 lets outside clients reach xpander agents. Sourcexpander, docs.xpander.ai/api-reference/rest-api, api-reference/sdk and api-reference/mcpread 2026-09-21 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
ToolhouseTesting, Debugging & Optimization 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. There are no scored test cases, datasets, evaluation harness or quality gate that returns a verdict. SourceToolhouse, docs.toolhouse.ai toolhouse/quickstart and introduction-to-ai-workersread 2026-09-21 |
||
|
xpander.aiTesting, Debugging & Optimization Quality work centers on debugging. Each task records reasoning entries and call parameters so a failure can be traced to the model, the skill or the prompt, and Omni can review instructions. There is no evaluation harness, scored test cases or quality gate. Sourcexpander, docs.xpander.ai/use/agents/auditread 2026-09-21 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
ToolhouseBrowser & Computer Use 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 says the scraper reads pages and does not fill forms or log in, which is web scraping, not an agent operating a browser. The virtual computer executes Python code and operates no interface. SourceToolhouse, docs.toolhouse.ai capabilites/scraping and capabilites/visionread 2026-09-21 |
||
|
xpander.aiBrowser & Computer Use The agent's runtime environment is a computer with CLIs, packages, config files and scripts for running code, and the agent runs its code there. xpander names no browser or desktop interface that the agent operates itself. Browsing comes only through the Anchor Browser and Browserbase connectors, which are third-party products bought separately. Sourcexpander, docs.xpander.ai/use/agents/runtime-environments and connectors/browserbaseread 2026-09-21 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | T Toolhouse |
x xpander.ai |
|---|---|---|
|
Entry price Lowest public entry point |
Business $500/mo · Business Max $1,200/mo · Enterprise custom | Team is usage based, billed in credits at one cent each, so $100 buys 10,000 credits. Enterprise is an annual contract from 50 agents, with no published price. There is no free tier. |
|
Pricing confidence How public the numbers are |
Public, exact | Public, partial |
|
Billing Primary billing axis |
Subscription tiers with a monthly credit allowance and a worker limit; model usage included | Usage based, in credits worth one cent each. Agents spend 1 credit per wake and 1 credit per tool call, and model tokens bill at each model's published rate. Seats are free, so the bill follows the work agents do, not the number of users. |
|
Variable cost Workload / overage exposure |
Low variable cost | High variable cost |
|
Free tier / trial Try before you buy |
No free tierTrial
|
Free tier
|
|
Buying motion Self-serve vs sales call |
Self-serve | Self-serve |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
xpander.ai
-
· Agent capability
An xpander agent can now build new tools for itself: a SKILL.md skill, a connector generated from an OpenAPI spec with its OAuth2 sign in, or a desktop connector that records the steps of an app with no API.
Source -
· Workflow orchestration
Workflows are now generally available in xpander's new chat interface, with no preview entitlement needed.
Source -
· Human approval / guardrails
xpander.ai added a Secrets section that declares an agent's required credentials, validates personal connections, and resolves secrets on every turn.
Source
More comparisons with Toolhouse or xpander.ai
Other matchups in agent infrastructure platforms
Not the pairing you were after? These compare a different set of agent infrastructure platforms on the same 14 capabilities.