What each endpoint costs in USD
Pricing
Pricing, at a glance
What each endpoint costs in USD
GET /v1/models + /machines/pricing- 01Discovereffective rate card
- 02Estimatebase + surcharges
- 03Reservefunds before work
- 04Settlecharge or refund header
Requests are billed in US dollars from your prepaid API wallet. The charge is taken before the model runs. On a conclusive server-side failure, the API submits a refund; treat it as complete only when X-Credits-Refunded is present. Ambiguous provider mutations may retain the debit until reconciliation. Internally each request unit is $0.01 (the granularity behind every price below), but everything you pay and see is dollars. The table shows published base prices and defaults; test keys (sk-coasty-test-) always bill $0.00. The effective deployed CUA and task-step rate card is returned in the pricing object from GET /v1/models, so deployment probes can detect an operator override before sending billable work. Effective machine runtime prices come from GET /v1/machines/pricing.
Surcharges
Predict and session-predict can incur all four fixed surcharges below. Ground can incur only the current-image HD fee, and session create has none. Each is an exact USD amount:
Machines
Managed-machine runtime is metered per minute and rounded down: $0.05/hr for a running Linux machine, $0.09/hr for a running Windows machine, and $0.01/hr while stopped or suspended. The starting, stopping, and restarting transitions bill at the running rate; the creating, error, and terminated states bill nothing, and TTL auto-destroy is free. Snapshots are a one-time $0.01 each, and every per-call operation (actions, batch, browser, terminal, files, screenshot, connection) is free. Provisioning requires a $0.20 wallet minimum, which is a gate, not a charge. If the wallet empties mid-flight the machine is automatically stopped, never destroyed, and resumes after you top up. The live rate card is always at GET /v1/machines/pricing.
External-machine enrollment and its heartbeat, observation, command-poll, and result transport are free and do not incur a VM runtime rate. Managed Task and Workflow inference keeps normal per-step pricing. Live-key BYOK records provider tokens and charges zero Coasty credits; test-key Task and Workflow execution remains deterministic sandbox and makes no provider call.
Schedule billing
Schedules have no per-fire fee. Managed schedules use the published API-wallet gate; BYOK schedules bypass create, run-now, and webhook wallet gates. For managed non-Unlimited accounts, execution is billed differently from everything else on this page: the published default charges scheduled agent runtime to your subscription credit balance at 10 consumer subscription credits per minute, with 20 credits required to start and a 6-hour timeout, not to this USD API wallet. Consumer subscription credits are quota units and do not inherit the Developer API wallet's fixed one-cent conversion. Unlimited bypasses the managed consumer-credit meter but retains managed API-wallet eligibility. BYOK opens no Coasty billing session and has no API-wallet eligibility gate. It reports credits_charged: 0; concurrency, persistent-machine, schedule, token, and abuse safeguards still apply. Live-key schedule execution can call and bill the selected provider. Managed-mode test-key schedule execution stays deterministic sandbox and makes no provider call; BYOK headers or provider metadata return 422 LLM_PROVIDER_UNSUPPORTED before execution without reading a stored provider key. Operator-effective gates, rates, timeouts, replay/dedup windows, body cap, and default webhook rate limit are exposed by GET /v1/models under pricing.schedules; use them in budget and signing guards. In schedule run-history records, credits_charged means consumer subscription-credit quota units, not API-wallet cents; it is zero for test, Unlimited-bypass, BYOK, and other non-billable runs and has no fixed USD conversion. Non-Unlimited managed schedules should keep both balances funded.