Plans, credits and limits

What it costs to run thermal and CFD simulations through Gradient Dynamics, from Studio, the REST API or an AI agent over MCP. All entry points draw on the same balance and are metered the same way.

Prices are in credits, the only unit you pay in. A typical simulation, a steady CFD run at 5 million cells, uses about one credit (see what a credit buys).

Rollout status:

  • Live today: the Core plan.

  • Being enabled in stages: no-sign-in discovery, the free trial, Developer, and per-connection budgets for OAuth connections.

Where something says “when enabled”, it may not be on for your account yet.

Plans

Discover

Free trial (when enabled)

Developer (when enabled)

Core

Who

Any agent, no account

New account with a verified email, on Core or Developer

Individuals, agent builders, API use

Teams

Price

Free

£0 for 30 days; you add a card to start, and nothing is charged during the trial

£10 a credit: billed monthly to your card, or bought up front

£1,500 a month, or £1,275 a month billed annually (£15,300 a year)

Credits

None (read-only)

30 (about 25 typical simulations), expiring at the end of the trial

Billed after use, or bought up front (2 to 100 per purchase, valid 12 months)

300 a month (about 250 typical simulations), reset monthly

Beyond that

—

Core starts on your card (£1,500 a month) when the trial’s 30 days or credits run out, unless you cancel first; Developer goes on to pay after use

Billed monthly, or as soon as unbilled use reaches £100

Extra credits at £7.50 each, billed after use, up to your organisation’s monthly limit

Seats

—

1

1

3

Mesh size

—

Up to 10 million cells

Up to 20 million cells

Up to 20 million cells

Concurrent jobs

—

1

2

4

Notes:

  • Discover means listing tools and templates, reading schemas and getting cost estimates without an account.

  • The free trial comes with either plan, for any verified email, once per person and once per card. You add a card to start it; nothing is charged during the trial, and cancelling before it ends (on the billing page) means nothing is charged at all.

  • Choosing a plan: at sign-up, choose Core or Developer. You can subscribe to Core or switch to Developer later on the billing page.

  • How credits are used: trial credits first, then Core’s credits for the month, then credits you bought, then credits billed after use (Core’s extra credits, or Developer with a card). Owners can set a monthly limit on those.

  • API and MCP ceiling: 20 million cells for every plan today.

  • Prices and VAT: prices are in GBP. Any tax is shown at checkout.

  • Metering: meshing and simulation are charged for the compute a run actually uses, so a larger or longer run uses proportionally more credits.

  • Uncharged work: geometry, design-engine and PhysicsAI calls are recorded at 0 credits and rate-limited, but not charged.

Budgets set by people, spent by agents

Every API key and every OAuth connection carries its own budget, in credits:

  • Default: 20 credits a month.

  • Optional caps: per job and per day.

  • Optional restriction: a single project.

The person who approves a connection sets its budget on the consent screen. Keys and connected apps are managed in Studio → Developer, where you can raise a budget or revoke a connection; revocation takes effect on the next request. Several agents can share an organisation’s credits without any one of them spending them all.

What a credit buys

Rough figures for typical jobs. A run’s own estimate, shown before it starts, is the figure to go by.

Job

Credits

Mesh a 5-million-cell model

about ½

Steady CFD at 5 million cells

about 1

Conjugate heat transfer at 5 million cells

about 3

Steady CFD at 20 million cells

about 5

A 10-design study at 5 million cells

about 12

How a run is charged

  1. Estimate. estimate_cost (MCP) or POST /v1/estimates (REST) returns credits and wall time as a low/expected/high range. It’s free and needs no account. Signed in, it also tells you whether the run would be admitted.

  2. Reserve. On submission, the high end of the estimate is reserved against your credits and the credential’s budget.

  3. Settle. When the job finishes, you’re charged for the compute it actually used, and the rest of the reservation is released. Each job is charged exactly once.

Failed runs:

  • A run that diverges, doesn’t converge, or is cancelled while running is charged for the compute it used.

  • Nothing is charged if the job never reached a GPU: it was refused, rejected on submission, or cancelled while queued.

When a run isn’t funded

The API returns HTTP 402, and MCP returns the same body as a tool error:

{
  "error": "insufficient_allowance",
  "message": "This simulation needs up to 1.60 credits; you have 0.50 left. Buy credits, or subscribe to Core.",
  "estimate": {"credits": 1.6, "credits_low": 0.9},
  "remaining": {"credits": 0.5},
  "actions": {
    "top_up_url": "https://studio.gradient-dynamics.com/billing?top_up=1",
    "upgrade_url": "https://studio.gradient-dynamics.com/billing?upgrade=core",
    "auto_top_up_allowed_credits": 0
  },
  "retryable": false
}

error

Meaning

What a person does

insufficient_allowance

Not enough credits for this run

Buy credits (top_up_url) or subscribe to Core (upgrade_url)

key_budget_exhausted

This key’s or connection’s own budget is used up; more credits won’t help

Raise the budget in Studio → Developer

overage_cap_reached

Core’s monthly limit on extra credits is reached

An owner raises the limit

plan_limit_exceeded

The request exceeds a plan limit, such as cells

Make the job smaller, or move to the plan named in the error

retryable: false means retrying won’t help. Agents should stop, show the message and link to a person, and never retry with another key.

create_topup_link returns a Stripe Checkout link to buy Developer credits, for a person to open; agents never see or enter payment details. Core doesn’t buy credits: its extra credits are billed automatically.

Responses also carry X-GD-Credits-Remaining and X-GD-Key-Budget-Remaining. You get an email when your credits cross 20%.

More: quick-start · data handling · tool reference