bolthub
PricingBlogDocs
bolthub

Rail-agnostic pay-per-call for MCP tools and APIs. Agents pay per call and you keep custody. Lightning today, more rails next. Built for tool builders and AI teams.

contact@bolthub.ai

Product

All productsbolthub Pay SDKHosted platformToolClientAPI HubNode LauncherPricingFor tool buildersFor agentsCharge for your toolsDocs

Legal

Terms of ServicePrivacy PolicySecurityAcceptable Use

Resources

API HubBlogWhat is L402?L402 vs x402RSS feed

Packages

npm

@bolthub/​payTool-payment SDK@bolthub/​agentL402 payment client@bolthub/​cliCLI@bolthub/​mcp-registryRegistry MCP@bolthub/​mcp-bridgeBridge MCP@bolthub/​verifyWebhook verifier

PyPI

bolthubPython SDKbolthub-verifyPython verifier
bolthub

© 2026 Signal Tech Pty Ltd. All rights reserved.

for agent builders

Let your agent pay for tools.

Give your agent a budget instead of a hundred vendor accounts: a drop-in paying client calls any paid tool, settles per call across rails, and stops at the cap you set. No signups, no API keys, no card on file.

Set up your agentCharge for your own tools
agent.ts
import { PayingClient, l402Payer, x402Payer } from "@bolthub/pay";
const client = new PayingClient({
payers: [l402Payer({ wallet }), x402Payer({ signer })], // tried in order
maxTotal: { sat: 10_000, usdc: 5_000 }, // per-asset budget
});
// callTool handles challenge -> pay -> retry transparently:
const result = await client.callTool(mcpClient, "get_satellite_image", { lat, lon });

Agents can’t fill in signup forms.

The subscribe-and-manage-API-keys model assumes a human at a dashboard. An autonomous agent needs to discover a tool, pay for it, and use it — at runtime, programmatically, within a budget you set. bolthub Pay makes the payment itself the credential, so a single client reaches every paid tool that speaks the profile.

Pays across rails

One client pays a tool's Lightning invoice or signs its stablecoin (x402) transfer — whichever the tool offers. Your payer order is your rail preference.

A budget you set

A per-asset cap bounds spend. The agent pays per call within it and stops at the limit — no surprise bills, no standing authorization.

No API keys

The paid proof is the credential. Nothing to provision, store, or rotate — the agent discovers a tool, pays, and uses it at runtime.

Wire it once.

Add your wallet, set a budget, and the client handles the rest: challenge, payment, and retry are transparent to your agent code.

terminal
bun add @bolthub/pay
Read the buyer SDK quickstart

A budget, not a blank check

The budget is a hard per-asset cap on the client: “spend at most 10,000 sats and 5,000 USDC, total.” Every payment is counted against it before it happens, and the client refuses any offer that would cross the line. Delegating to a sub-agent? Hand it its own client with a smaller cap; it never holds your keys or an open-ended balance.

Curious how settlement works under the hood? Compare L402 vs x402 — bolthub speaks both, so your agent doesn’t have to choose.

start calling

Copy one config. Start calling.

Wire bolthub into Cursor, Claude Desktop, or your own orchestrator. Add your wallet, set a budget, and your agent can discover and call any listed tool. Building in code? Python and TypeScript SDKs call any hub API directly.

Set up your agentBrowse the hub

hub / btc-intel

  • GET /v1/derivatives/cme-basis3 sats/req
  • GET /v1/market/multi_exchange3 sats/req

LIVE32 endpoints · btc-intel.gw.bolthub.ai

browse the hub →