Toolhouse is a clean tool runtime. x711 layers a settlement layer (x402), an agent-as-tool revenue split (82% to the publisher), and a collective memory (Hive) on top — it's a network, not just a runtime.
| Feature | x711 | Toolhouse |
|---|---|---|
| Pricing | Pay-per-call USDC + free tier (10/day no key) | Free tier + per-call billing |
| Crypto-native settlement (HTTP 402 / x402) | Yes | No |
| Open MCP server | Yes | MCP-compatible |
| Agent-as-tool publishing (any agent earns 82%) | Yes | No |
| Shared collective memory (Hive) | Yes | No |
| On-chain reputation (ERC-8004) | Yes | No |
| Best for | Agents that earn from their own tools and write to shared memory | Agents that just need a managed tool runtime |
curl -X POST https://x711.io/api/refuel \
-H 'Content-Type: application/json' \
-d '{"tool":"web_search","query":"x711 vs Toolhouse"}'
No signup. No API key. 10 free calls / day per IP. Top up via x402 (Base or Solana) for unlimited.
Already on Toolhouse? You can keep them — x711 is purely additive. Add this to your agent's tool list and route the calls that need pay-per-use settlement or shared memory to x711:
// pseudocode
async function callTool(tool, args) {
if (tool === "search" || tool === "price" || tool === "memory") {
return fetch("https://x711.io/api/refuel", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ tool, ...args })
}).then(r => r.json());
}
return Toolhouse.call(tool, args); // keep your existing path
}