Free to start, $19 per seat
Every plan includes the whole product: the gateway, the marketplace, custom tools, access policies, the project sandbox and the audit log. Free renews 5,000 credits every 30 days. Pro grants 50,000 per seat.
What each plan includes
Free renews 5,000 credits every 30 days. Pro grants 50,000 for every billed seat on each paid invoice. Credits belong to the workspace rather than to a person, so one teammate's busy week does not strand anyone else.
In every plan
- Every marketplace and custom tool
- Per-user policies on every action
- Complete request and response audit logs
Free
Run real agents on the complete gateway, free every month.
$0
forever
- 5,000 credits every month
- Self-host with Docker Compose
- Up to 2 workspace seats
Pro
Most teamsFor teams running agents in production.
$19
per seat, per month
- 50,000 credits per seat each month
- Self-host with Docker Compose
Enterprise
Managed hosting, SSO, extended retention and an SLA.
Custom
annual agreement
- Credit volume to match your usage
- Managed hosting, SSO, extended retention, and an SLA
Seats follow your active member count. Adding or removing a teammate adjusts the subscription quantity and prorates the difference.
What one credit actually buys
A direct call costs one credit. A sandboxed call costs 5, because it queues, boots a container and holds memory for as long as it runs. Toolspoke prices on the path a call resolves to.
1credit
A direct call
Toolspoke reaches the provider from its own process. Most REST and streamable MCP integrations resolve this way, so most calls cost one credit.
5credits
A sandboxed call
The call queues, boots a container in your project sandbox and holds memory for its duration. CLIs and stdio MCP servers run here, and so does any action a connector marks as sandboxed.
10credits per interface
A toolkit build
Turning an OpenAPI document, an MCP server or a CLI into an installable toolkit. Charged per interface the build reads, so a toolkit built from one source costs 10 and one built from three costs 30. Several model passes over a large specification, charged once per build and not per retry.
The install dialog states which path a tool takes before you install it, and every call records its path in the audit log. Searching the catalog, listing toolkits and reading a usage guide cost nothing.
Buy more credits at any time
A top-up is a one-time purchase that lands in the same workspace pool as your monthly grant. Purchased credits do not expire, so a quiet month is not a loss and a spike does not need a plan change.
Top-ups work on every plan, including Free.
- Add 25,000 credits
25,000credits
$15 one time · $0.60 per 1,000
- Add 100,000 credits
100,000credits
$50 one time · $0.50 per 1,000
- Add 500,000 credits
500,000creditsbest rate
$200 one time · $0.40 per 1,000
Questions about credits and seats
What uses a credit?
One tool attempt that reaches the provider is charged, whether or not it returns successfully. A direct call costs one credit and a sandbox-backed call costs 5, decided by the execution path the call resolves to rather than by the integration type. Building a toolkit costs 10 per interface it reads, so a three-interface build costs 30. Requests refused by policy, and requests that never leave Toolspoke, are not charged.
How do I know whether a tool runs direct or sandboxed?
The install dialog tells you before you install it, and the audit log records the execution path for every call that has already happened. You never have to find out from an invoice.
Do agents pay to browse the catalog?
No. Searching for a tool, listing toolkits and reading a usage guide are free. Only the call that reaches the provider is charged, and it is charged once even if the client retries it.
Are credits per user?
No. Your workspace has one shared balance, so teammates and their agents draw from the same pool. The seat count follows your active member count and decides how many credits each paid invoice grants, not who may spend them.
Do free credits run out for good?
No. Free is topped back up to 5,000 credits every 30 days, so a heavy week costs you the rest of that month and nothing more. It tops up to that figure rather than adding to it, which means an idle workspace does not quietly accumulate a year of credits, and a top-up you paid for is never reduced to make room for a free grant.
Why one paid plan instead of two?
Because the second one was sorting people by how much they call rather than by what they need, and every plan already includes the whole product. Pro is $19 per seat with 50,000 credits, which covers heavy daily agent use several times over. Past that, top-ups cost less than a second subscription would, and Enterprise exists for the things that are genuinely different: managed hosting, SSO, extended retention and an SLA.
What happens when we add a teammate?
The Stripe subscription quantity follows your active member count, with prorations. The next paid invoice grants the plan's credits for each billed seat, keyed to the invoice so a redelivered webhook cannot grant them twice.
Can two people use different credentials for the same tool?
Not on the same install. An install holds exactly one credential, and that is deliberate: which of two stored values a call used should never depend on who owned the agent key. When you genuinely need two, give each its own project. Projects are already the line agent keys, policies and the sandbox are drawn on, and they cost nothing extra.
Can we run this without Stripe?
Yes. Toolspoke runs with billing entirely unconfigured, which is the normal shape of an internal deployment. Every workspace starts on Free and nothing asks for a card.
Running this inside your own infrastructure? Stripe is optional. Toolspoke starts with billing unconfigured, every workspace on Free, and no card prompt anywhere.
Self-hosting guideStart with the free plan
5,000 credits every 30 days, renewed. No card required, and nothing held back for a higher tier.