AgentRuntime meters usage in credits. Workflows, memory indexing, and other billable actions debit your workspace balance. Manage billing from Settings (/settings) in the Console:
- Billing Overview — subscription status, payment method, top-up entry points
- Plans — plan catalog and checkout
- Usage & History — credit balances, metered usage, payment history
Plans
Self-serve plan codes (monthly and annual variants):
| Plan | Best for | Trial | Notes |
|---|
| free | PAYG-only usage | No | Buy credits as needed; up to 3 members |
| pro | Teams getting started | 14 days, 5 credits | Default plan in onboarding; card optional for trial |
| plus | Higher-volume teams | No | Paid subscription required |
| max | Power users | No | Paid subscription required |
| enterprise | Custom contracts | Sales-provisioned | Contact sales — not self-serve checkout |
pro_annual, plus_annual, etc.) follow the same tier rules with yearly Stripe billing.
View live plan details and prices in the Console Plans tab — catalog syncs from Stripe.
Plans are scoped to the AgentRuntime product (product_code = agentruntime). The Console shows tier names (pro, plus, …) only. See Multi-product billing for how product lines share one platform kernel.
How credits work
1 credit = 1,000,000 microcredits. The Console displays credits; APIs and ledgers often use microcredits internally.
Credit buckets
Usage draws from buckets in this order:
- Trial — Granted during an active trial (for example, 5 credits on pro)
- Included — Credits bundled with your subscription
- PAYG — Pay-as-you-go balance from top-ups
PAYG balance persists across plan changes, trial expiry, and subscription cancellation.
When credits are required
Most platform actions require a positive balance. Workflows fail to start when credits are exhausted unless your plan allows overdraft (disabled by default).
Check balance and breakdown at Settings → Usage & History or GET /v1/billing/usage:
{
"trial_remaining": 2000000,
"included_remaining": 0,
"payg_remaining": 15000000
}
What consumes credits
| Action | Typical cost | Notes |
|---|
workflow.step.execute | ~5 credits per step | Charged when a workflow run executes steps |
memory_extract_interactive | ~10 credits per job | Interactive memory extraction |
memory_extract_bulk | ~2 credits per job | Bulk memory indexing |
memory_index_file_mb | ~1 credit per MiB | File indexing |
GET /v1/billing/action-pricing. Enterprise tenants may have custom pricing overrides.
LLM token and per-MCP-call metering are on the roadmap. Today, LLM costs may also flow through your provider API keys directly.
Trials
New workspaces on pro can receive an automatic 14-day trial with 5 credits. Card is optional during trial signup.
Tenant admins can also start trials via the API:
Convert trial to paid early:
POST /v1/billing/subscription/convert-trial-now
Subscriptions
Tenant admins manage subscriptions:
| Action | Endpoint |
|---|
| Activate paid plan | POST /v1/billing/subscription |
| Change plan | POST /v1/billing/subscription/change-plan |
| Cancel | POST /v1/billing/subscription/cancel |
PAYG top-ups
When included or trial credits run low, buy more credits without changing plans.
Open billing
Go to Settings → Billing Overview and select Top up (or use the PAYG flow on Usage & History).
Choose amount
Select a credit package. Payment processes through Stripe.
Confirm balance
PAYG credits appear in your usage breakdown immediately after payment succeeds.
POST /v1/billing/topups/payg/intent
amount_cents, microcredits, currency, and an idempotency_key.
Usage history
Review metered events at Settings → Usage & History or:
GET /v1/billing/usage-history
GET /v1/billing/payment-history
/analytics) also shows credits consumed alongside run metrics.
Discount codes
Tenant admins can apply billing or discount codes:
POST /v1/billing/codes/apply
POST /v1/billing/discounts/validate
Roles
| Action | Required role |
|---|
| View usage and plans | project_contributor |
| View usage dimensions | project_viewer |
| Change plan, top up, apply codes | tenant_admin |
Multi-product billing
Wheelhouse scopes the plan catalog by (product_code, plan_code). The AgentRuntime Console (console.agentruntime.io) is wired to product_code = agentruntime — you see only AgentRuntime tiers in Settings → Plans.
| What | Scope |
|---|
| Plan catalog | Per product_code (BFF filters by deployment config) |
| Workspace subscription & credits | Per workspace — one plan and ledger per workspace |
| Stripe sync | Each price carries product_code + plan_code metadata |
product_code = agentruntime; plan codes and balances are unchanged. Full architecture: Multi-product billing.
