// help/credits/

Credits and plans.

One balance, spent on anything that runs on our servers. This page explains what a credit buys, what your plan includes, what resets and what does not, and exactly what happens the moment you run out.

What a credit is

A credit is one unit of work on our servers. Different actions cost us different amounts to serve, so they are converted to a common unit first and you spend a single balance on any mix of them.

Action (credits)What it is
REST API call (1)One call to one capability from your own code. Arithmetic on our servers, measured in milliseconds.
MCP tool call (1)The same capabilities, called by an AI assistant instead of by your code. Same work, same price.
AI generation (10)Anything that asks a language model on your behalf, including one proposal from the workflow advisor.
Render (25)HTML or a web page turned into a PDF, a screenshot, or a page read as clean text. This starts a real browser on our side, which is why it costs the most.
Agent memory (0)Storing and reading a value between sessions. Free on purpose: it is a database row, and metering it would only discourage the thing that makes agents useful.

You never have to predict the mix in advance. The same balance covers a quiet month of API calls and a busy afternoon of renders.

What costs nothing

Most of ToolForte is not metered at all.

There are 341 tools on the site and you can open any of them without an account. Almost all of them do their work in your own browser, so your files and text never reach us and there is nothing for us to charge for. The exceptions are the ones that cannot work that way: the AI tools, and anything that renders a PDF or a screenshot.

The server-side features have a small taste-test allowance for people without an account: 5 AI generations and 3 renders per day, counted per network address and reset every 24 hours. It is meant for trying the thing out, not for running work on.

What the plans include

Two plans, and the difference is room to work in rather than a different product. Everything is in both.

Each month
Free
€0
1,000 credits, which is 1,000 API or MCP tool calls, or 100 AI generations, or 40 renders, or any mix. Usage history for 7 days, agent memory kept for 30 days.
ToolForte Pro
19 a month, or €190 a year
7,500 credits, which is 7,500 API or MCP tool calls, or 750 AI generations, or 300 renders, or any mix. Usage history for 365 days, about 12 months, agent memory kept for 365 days, about 12 months.

Yearly is priced as 10 months, so paying for a year gets you 2 of them free. The plan itself is identical either way. The full comparison lives on pricing.

What resets, and what does not

Two kinds of credit sit in your account, and they behave differently.

The monthly allowance resets

Your plan credits refill on the first of the month, counted in UTC. They do not roll over: 7,500 credits on ToolForte Pro means that many every month, not a growing pile. Your account page always shows the exact date of the next reset.

Credits you buy never expire

Purchased credits stay on your account until you spend them, including after a subscription ends. They are also spent last: the monthly allowance goes first, and your purchased balance is only touched once the allowance for the month is gone. So buying early never wastes what your plan already gave you.

Buying extra credits

You can buy credits with a free account. There is no plan to subscribe to first, nothing renews afterwards, and the credits are simply yours.

Pick any amount from 100 credits up to 1,000,000, pay once, and the balance is added to your account. Larger amounts get a better rate, and the rate applies to the whole order rather than only to the credits above the threshold.

BuyPriceRate
100 credits€1.001 cent per credit
1,000 credits€5.00 (from 1,000 up)0.5 cent per credit
5,000 credits€20.00 (from 5,000 up)0.4 cent per credit

At the best rate that works out at about €0.10 for a render and €0.04 for an AI generation. The slider on pricing and on your account page shows the price before you commit to anything, and offers you the cheaper deal when the next tier up would actually cost less than the amount you picked.

Topping up automatically

If you would rather not think about it, your account page has an optional automatic top up: choose the balance at which it should trigger, the amount to buy, and a monthly ceiling it will never spend past. It is off unless you switch it on.

What happens when you run out

Nothing silently continues and nothing quietly bills you.

The call is refused, not queued
The REST API answers HTTP 429 and puts your limit, what is left, and the reset date in the response headers. An MCP tool says the same thing in plain words to the assistant. The AI tools on the site show the message on screen. There is no overage charge and no work is done that you have not paid for, so an agent left running overnight fails loudly instead of running up a bill.

A workflow behaves the same way, one step at a time. Each step is paid for just before it runs, so a run that hits an empty balance halfway stops there: the steps that ran were charged, the rest were not, and the run history shows exactly where it stopped.

You get warning before that point: once the balance is running low, the answers carry a notice saying so, and your account page shows what is left against what the month started with. To carry on you can wait for the first of the month, buy credits, or move to ToolForte Pro. With 7,500 credits a month that is 7,500 API or MCP calls before you would think about it again.

Keep reading
Start here
What ToolForte is, and the three ways to use it: in the browser, over the API, and from an AI assistant.
Workflows
Chain capabilities into one job. Steps, inputs, test runs, run history, and how a run behaves when a check fails.
The AI advisor
Describe a job in words and get a workflow built from real capabilities, or an honest no.
API and MCP
For developers: get a key, send the header, call a capability, run a workflow.
Your account
Signing up, confirming your email, resetting your password, usage history, billing and API keys.