How much it costs

Credits are the assistant's fuel. The simpler the work, the less it costs: an hour in which nobody wrote costs zero.

Talking to the builder is free

Everything you do in the dashboard — asking questions, creating an agent, changing its personality, asking it to read your site — spends no credits. You pay only for the work of your own agents: their replies to customers and their scheduled runs.

Plans

The plan decides two things: how many assistants you can have and how many credits arrive each month.

Plan	Price per month	Agents	Credits per month
Free	0	1	10,000
Starter	$129	1	100,000
Pro	$649	3	500,000
Business	$999	unlimited	unlimited

"Unlimited" in Business is about the plan: there's also a separate monthly spending cap — a safeguard against failures, not a plan limit. And each assistant can be given its own cap, so one agent doesn't use up everyone's supply.

No card is needed for the Free plan. It's worth switching to another plan when the monthly supply has actually run short, not in advance.

Credit packs

You can buy extra supply without changing your plan. Credits bought in packs don't expire at the end of the month — they stay until next time and are spent when the monthly supply has already run out.

Pack	Price
10,000 credits	$13
50,000 credits	$65
200,000 credits	$249

Where to buy it

In the dashboard, in the Plan section. It shows which plan is active and how much of it has been spent, and that's where you buy plans and packs: the button leads to the payment gateway, and after payment the dashboard brings you back to the same screen.

A few things worth knowing in advance:

• The workspace owner changes the plan and payment. Colleagues can see which plan is active and how much supply is left, but they don't buy — the subscription is charged to whoever pressed the button.
• You can switch to another plan without cancelling the current one. The old subscription is stopped the moment the new one is paid — in exactly this order, so you're never left without a plan in between. If the payment doesn't go through, your current plan simply stays active.
• The same plan isn't sold twice. There's no point buying what you already have — the payment gateway would charge twice for the same thing.
• A credit pack doesn't change your plan — you can buy one any time on top of your current plan.
• The Free plan isn't bought. The workspace returns to it by itself when a paid subscription ends.

The same in words

You can buy a plan without opening the section — just tell the builder:

Say	And it
"what plans are there?" / "how much is Pro?"	shows plans and packs with prices — the same as in the Plan section
"I want Pro" / "buy more credits"	opens a payment and gives you a "Payment page" link — it goes straight to the payment gateway
"how many credits are left?" / "what were the credits spent on?"	names the balance for the month, the extra supply bought and spending by agent
"I paid, but my plan didn't change"	checks the payment with the payment service
"cancel this payment"	cancels an unfinished attempt; if someone pays it anyway, the money comes back by itself
"cancel my subscription"	cancels auto-renewal after your "yes"; the plan stays active until the end of the paid period
"show my payments"	lists payments with the status of each

The builder doesn't take money: it opens a payment, and you pay yourself, on the gateway page. The rules are the same as on screen: if a payment is already open, the link leads to the same one, there won't be a second invoice; the same pack right after the previous one — only after your "yes, another one". The builder doesn't do refunds — write to support.

This works only for the workspace owner signed in to the dashboard: to a colleague or someone else's program with a key, the builder will say nothing about money and open nothing.

You can't pay twice for the same thing

While a payment is started and not finished, there's only one. Opened the payment page, came back to the dashboard with the "back" button, opened the dashboard in a second tab — at the top of the Plan screen there's a "Payment already open" block: what exactly is being paid for, how much and until what time. The button on the plan or pack card then says Continue payment and leads to the same payment page instead of creating a second invoice.

The block has three actions:

• Continue payment — the same payment gateway page.
• Check payment — the dashboard asks the gateway itself how it ended. If the money went through and the dashboard didn't know yet, the plan or credits appear right away.
• Cancel this attempt — the invoice is closed and will no longer be credited. After that you can choose another plan.

A payment stays open for an hour. If nobody pays within an hour, the attempt closes by itself, it becomes "expired" in the history, and the next press of the button starts a new one.

While a payment for one plan is open, you can't choose another — first finish or cancel that attempt. While the bank is confirming the payment (for example, waiting for an SMS code), the block says "Waiting for bank confirmation", and the dashboard won't start a second payment.

You can buy credit packs as many as you like. But if you just bought the same pack, the dashboard will ask again: "You just bought this pack. Buy another one?" — so an accidental second click doesn't become a second purchase.

If the gateway did charge too much

The dashboard can't close a payment gateway page open in your browser. So overpaying is still possible in two ways: paying an attempt you cancelled yourself, or paying an old page after you've already paid a new one. Such a payment isn't credited but refunded automatically:

• in "Payment history" the row becomes "refunding", then "refunded" — with a reason: "refunded automatically: double payment" or "payment for a cancelled attempt";
• the owner gets an email with the amount;
• the money returns to the card within the bank's timeframe — usually up to a few days.

If the payment gateway didn't perform the refund, the row becomes "will refund manually": we already know about it and will return the money ourselves, and you get an email with exactly these words. The dashboard never refunds a single payment — the one for which you received something.

If the money went but the plan didn't change

Sometimes the payment gateway doesn't manage to tell us about the payment. Then on the Plan screen there's the "Payment already open" block with a Check payment button — it asks the gateway again and applies the plan if the money really went through. When you return from the payment page, the dashboard presses it for you.

There's no block when there's nothing to check: if you didn't start paying for anything, there can't be any lost money, and offering to "check" it would hint at a problem that doesn't exist.

Further down is Cancel subscription. Cancelling doesn't switch anything off right away: the plan stays active until the end of the already-paid period, and then the workspace returns to Free. There won't be a next charge.

What's already been paid

At the bottom of the same screen is Payment history: subscriptions and credit packs in one list, newest at the top. Each row shows the plan or pack name, date and time, amount and status.

Statuses are named as they are:

Status	What it means
paid	the money went through, the invoice is closed
in progress	the payment is open, the payment gateway hasn't reported the result yet
failed	the payment didn't happen; the plan stayed as it was
cancelled	you cancelled this payment attempt yourself
expired	the payment was opened and not finished within an hour; no money was taken for it
refunding	the payment turned out to be extra, the money is being returned — the reason is shown next to it
refunded	the extra payment was refunded automatically
will refund manually	it couldn't be refunded automatically; we'll return the money ourselves

Failed attempts and those in progress are shown in the same place, not hidden. These are exactly what you check a bank statement against: when the bank shows a charge but nothing changed in the dashboard, you need to see both rows side by side, not just the successful ones.

The history is visible to the workspace owner: the subscription is charged to their account, so the statement is theirs too.

You can't pay for anything in the conversation with the builder — it has no tools for that, and that's deliberate: it isn't the one who moves money.

The same is available through the API, if payment needs to be built into another process.

What it will come to for you

The product has no exact measurements, and we won't pass off an estimate as a measurement. The order of magnitude is:

• one conversation with several replies — about 70 credits;
• a dozen conversations a day — roughly 700 credits a day, i.e. 21,000 a month;
• one nightly scheduled report — about 300 credits a month.

Your numbers will depend on how long the conversations are and how many actions the assistant performs in each.

You see the price of a change before the change

If you ask for something that makes every conversation more expensive, the builder will say so along with its question — that is, while you can still say no:

This graph is up to 2 model calls per run and up to about 40 s.

Two model calls instead of one is a roughly twice as expensive conversation.

It works both ways: if a change adds nothing to the price, the builder won't bring up money at all.

What spends credits and what doesn't

Spends:

• every agent reply to a customer;
• every scheduled run or run from an outside signal in which the model or the sandbox worked (a run without them is zero, see watching below);
• a trigger test run and an action check — they're real;
• handing work to a neighbouring agent;
• recognising voice messages — 6 credits per minute of audio, prorated by the second (a 0:42 voice message is 5 credits). Only what reached the agent: something too long or unrecognised costs nothing. It's a separate line in the run log.
• images and voice-over — 50 credits per image (drawn from scratch or edited) and 15 credits per 1,000 characters of voiced text, prorated. The spending limit is checked before calling the service; a refusal or a service failure costs nothing. Separate lines with the price in the run log.
• a deep research report — like a long task with several branches; the estimate is 500–1,500 credits per report, and the agent names it before starting.

Doesn't spend:

• the conversation with the builder;
• a page check where nothing changed: the model isn't called at all then. Only the change notification is paid for (and for a page read by the browser — also the browser seconds);
• time when nobody is writing;
• a conversation led by a live person instead of the bot.

When your supply is running out

When 80% of the monthly supply has been spent (that is, a fifth is left), you get a notification — in advance, not after the fact. See When something breaks.

In the dashboard panel the credits bar turns yellow when a fifth is left (that is, at the same time the notification arrives) and red when a tenth is left.

When credits run out:

• new conversations don't start until the next period or a top-up;
• a conversation already in progress is finished.

Separately there's a monthly spending cap — a safeguard against failures, not a product limit: it catches the case when something gets stuck in a loop and burns the budget in an evening. If you hit it, the bot pauses new replies, and the notification will say so: to raise the cap, you need to change your plan.

A cap for a single assistant

Both limits above apply to the whole dashboard — that is, they stop all your assistants at once. Sometimes you need something else.

Imagine a night agent that goes through listings at eleven. It went into a loop. By morning the dashboard's supply is used up — and it's not that agent that goes silent, but the bot in the chat window on your site, the one talking to customers. You find out from a customer.

That's why each assistant can be given its own monthly cap:

Give this agent a cap of 20,000 credits a month

Then:

• an agent that reaches its cap stops until next month — and you get a notification about that agent specifically;
• the other assistants keep working: the cap applies only to it;
• spending is counted from the first of the month — from the same run log you see in the dashboard.

In the panel next to the conversation an "Agent cap" row appears with two numbers: how much has been spent and how much is allowed. One number alone tells you nothing here — whether "20,000" is a lot or a little is clear only together with what's been spent.

Who needs this and who doesn't

A bot that answers customers mostly doesn't need a cap: it spends exactly as much as it's asked. It's for those that work on their own — on a schedule, at night, with nobody around.

The smallest cap is 1,000 credits: below that the assistant would stop before its first reply, and it would look like a problem, not a setting. To remove the cap, say "remove this agent's cap" or set it to 0.

Next

• When something breaks — where notifications about money and problems arrive.