How are credits counted?

By the work actually done · tokens and tool calls per run. Short tasks use few credits; multi-system runs use more. Every run's cost shows in the Console.

What happens when credits run out?

Top up instantly in the Console or enable auto top-up. No penalties, no lock-in contract.

How does this differ from the monthly ERP plan?

The monthly ERP plan already bundles a credit allowance; Platform credits cover the API/agent work you build yourself, topped up by usage beyond that.

Per-credit pricing

Pay for the work the agents do no hidden fees

API credits · cost shown per run

Credits track the work actually done · tokens and tool calls per run. Short tasks cost little; multi-system runs cost more. Top up instantly in the Console, no lock-in, with the cost of every run visible before and after.

per credit: by real work, not guesswork
every run: transparent cost in the Console
no lock-in: top up as you go, cancel anytime

Get an API key Read the docs

billingcost per run

run r_8f2a  ·  เสมอ + 3 น้อง
  tokens     18,420
  tool calls 14  (express-mcp, company-erp)
  ────────────────────────────
  credits    142     ≈ ฿4.26

balance: 4,858 / 5,000 credits

Every run shows exactly how many credits it used

How credits work

Transparent, usage-based

01 · What countsCredits

tokens + tool calls = credits

The reasoning the agents do plus the tool calls they make into real systems add up to credits per run · itemized every time, no guessing.

Tokens processed
MCP tool calls
Per-run breakdown
No hidden fees

02 · vs the ERP planPlans

The ERP plan bundles credits

The monthly ERP plan already includes a credit allowance; Platform credits are for the API/agent work you build yourself, topped up by usage beyond that.