Credits, billing and limits

Sim Cloud measures billable usage in credits: 1 credit = $0.005, or $1 = 200 credits. For example, $10 of usage is 2,000 credits.

The plan and execution tables below describe Cloud defaults. Enterprise agreements and deployment configuration can change them. Billing-disabled self-hosted deployments do not apply Sim plan-based usage billing; provider and infrastructure costs still apply. See Self-hosted limits.

What a workflow run costs

A billable workflow run can include:

With your own provider keys, you pay the provider directly for those calls. The workflow base charge and unrelated hosted-tool or sandbox usage still apply. Local Ollama or vLLM inference avoids an external model API charge, but still needs infrastructure and any enabled Sim run charge.

For a simple uncached model call, with prices in USD per million tokens:

modelCostUSD = (inputTokens × inputPrice + outputTokens × outputPrice) / 1,000,000
runCredits = 1 + billableModelCostUSD × 200 + hostedToolCostUSD × 200 + sandboxCostUSD × 200

Cached input, cache writes, model routing, and provider-specific usage can change the calculation. Use the recorded run cost to compare configurations. Internal child executions that share their parent's base charge do not add another base fee.

Inspect recorded usage

Open a run in Logs → Overview to inspect its cost rows, Total, and available input/output token counts. Current runs list ledger items such as Base Run and model or tool charges. Older runs may contain only a total. Displayed credit rows are apportioned so they add up to the displayed total.

Chat, Knowledge Base processing, and dictation also record usage outside ordinary workflow runs. The Agent block source label in organization Insights refers to the Sim Chat workflow block, whose usage is metered separately from its containing workflow. Ordinary Agent model calls are part of Workflow usage. See Usage monitoring for attribution.

Hosted tool rates

These are configured hosted-tool base rates in USD, not a provider's retail subscription price. Actual usage is recorded per operation. A provider credit, such as a Firecrawl credit, is a different unit from a Sim credit.

Supported providers can use your own keys instead. A workflow containing a no-charge tool still has its base run charge.

Bring your own key (BYOK)

Store your provider keys under Settings → BYOK to use them instead of Sim-hosted keys. BYOK avoids Sim's model or tool usage charge for the provider calls it covers; you pay that provider directly.

Key scope and precedence

Saved-key precedence is resolved separately for each provider:

1. Use that provider's workspace key pool when one is configured.
2. Otherwise, use its eligible organization key pool.
3. Otherwise, use the next available configured source, including a Sim-hosted key where supported.

A workspace OpenAI key does not override the organization's Anthropic key. The settings page marks inherited providers so you can inspect inheritance before adding an override. A nonempty workspace pool is exclusive; a corrupt workspace key is not a reason to borrow an organization key.

Add or remove keys

1. Open Settings → BYOK.
2. Choose Workspace, or Organization if you are an organization administrator.
3. Select Add Key for the provider, enter the key, and save.

You can store several keys for a provider in each scope. Requests rotate across the keys in the selected pool. Keys are encrypted at rest; the browser receives a masked display value, not the full saved key.

Deleting the last workspace key lets that provider inherit an eligible organization key or use its next available configured source. Deleting an organization key affects workspaces that inherited it. Key deletion takes effect on subsequent resolution.

If the organization's plan lapses, its keys stop applying and workspaces use their next available source. Saved organization keys remain, and organization administrators can delete them; adding or updating them requires an active organization plan.

Provider catalog

The settings page groups keys into Models, Search & web, and Enrichment. It is the current catalog; the following lists describe the supported uses.

Cloud plans and credit allowances

Current monthly pricing and allocations are:

Pro and Max are available for individuals or teams. Team subscriptions pool credits across internal seats. For example, Max for Teams with three seats has a 75,000-credit monthly allocation and a 12,000-credit weekly refresh allowance. External collaborators do not add seats, but their work in an organization-owned workspace is billed to that organization.

See current pricing and Settings → Subscription for the plan available to your account. Internal membership, external eligibility, and workspace migration are explained in Roles and permissions.

Weekly refresh

Each seven-day window from the billing period's start excludes usage up to the weekly refresh allowance from billable usage. It is an allowance against that week's usage, not an accumulating wallet balance. Unused allowance does not carry forward. Team allowances scale with seats.

Annual billing

Pro and Max annual subscriptions have a 15% discount while retaining their advertised included credits. Team pricing uses the same per-seat rate.

Use subscription settings to choose the billing interval. The usage display names the current billing period; check it when comparing usage across an interval change.

Control spending

By default, paid usage is capped at the included allowance and any applied credit balance. Under Settings → Subscription, either:

• Turn on Allow usage to go past included usage under Enable on-demand usage to remove the normal usage cap.
• Set a higher Usage limit to allow overage up to a specific ceiling.

Applied credit balance increases the covered allowance. A balance grant alone does not enable on-demand billing. Disabling on-demand returns the limit to the covered amount; the control is disabled while current usage is already above that amount, until usage falls back or the period resets.

Organization owners and admins manage organization billing and spend limits. Workspace Admin access alone does not grant that authority. Organization Manage credits controls a member's usage cap; it is not a credit-purchase control.

Subscription and overage example

If a Pro account has 7,000 billable credits after weekly-refresh deductions and applied credits, its charge is $25 for the subscription plus $5 for the 1,000-credit overage. Continuing beyond the allowance requires on-demand usage or a higher limit.

For team plans, overage is calculated against the organization's pooled allowance. Usage in organization-owned workspaces is billed to that organization, including external collaborators' work. Attributed human usage can also count toward the person's organization member cap. The organization receives one bill. Enterprise usage and limits follow the agreement rather than ordinary Pro/Max overage billing.

Threshold billing

The default incremental billing threshold is $100 of unbilled overage, equivalent to 20,000 credits. Sim automatically settles eligible overage during the billing period instead of waiting for one large period-end bill.

Any remaining eligible overage is settled at period end. Applied balances and billing eligibility affect the amount charged.

Cloud limits

These defaults follow the paid tier: Pro and Pro for Teams share Pro limits; Max and Max for Teams share Max limits. Enterprise values may be customized. Request rate, concurrent runs, storage, and run duration are separate limits.

Workspaces

Free accounts have one personal workspace by default and Pro accounts up to three. Organization workspaces are uncapped for eligible organization owners and admins. For Max and other current account limits, check the workspace creation controls and pricing, rather than assuming a personal-workspace cap from another deployment.

Accepting internal membership moves owned personal workspaces into the organization. See Joining an organization for the ownership and seat consequences.

Rate limits

Execution rate buckets can burst above the sustained per-minute rate. General API endpoint requests have a separate request bucket; these run rates do not describe every API call. See API usage and limits.

Concurrent executions

The limit applies per billing account. An organization's workspaces, members, and API keys share its concurrency pool. An admitted async run holds a slot while queued and running; a synchronous run holds one while running. Workflow-in-workflow blocks execute within the parent run and do not consume another slot.

File storage

Organization storage is pooled across its workspaces. Storage limits are independent of the credit allowance.

Run time limits

Synchronous execution waits for the workflow to finish and returns its result, or streams it when streaming is selected. Asynchronous API calls, webhooks, schedules, polling triggers, and table workflow columns run in the background.

A direct async API request can shorten the account's timeout for that request; it cannot extend it. A run exceeding its limit fails with a timeout error. Individual blocks, remote sandboxes, and providers can have shorter independent limits. See How workflows run.

Self-hosted limits

Billing-disabled deployments have no default plan-based workspace cap, workflow timeout, or storage enforcement. Operators can opt into rate, storage, and workflow timeout enforcement with the corresponding free-tier environment settings. The hosted billing-account concurrency reservation applies only when hosting and billing are enabled.

This does not remove protocol, provider, block, sandbox, or deployment resource limits. See Self-hosting configuration for exact settings.

Monitor usage through the UI or API

Use Settings → Subscription to inspect the current allowance, usage limit, billing period, on-demand setting, and plan. Organization administrators can inspect Usage monitoring for source, workspace, and member attribution.

For workspace billing information, use Get billing status. List billing logs exposes billable events. Billing and run-resource responses use credits, while Logs endpoints explicitly report USD; use each endpoint's documented unit.

The legacy GET /api/users/me/usage-limits endpoint accepts an API key in X-API-Key. It reports the authenticated account or key owner's usage and subscription, which can differ from a workflow's workspace payer. Its usage.currentPeriodCost and usage.limit are in USD. It also returns storage usedBytes, limitBytes, and percentUsed.

Its rate fields are:

See API authentication before selecting a personal or workspace key for monitoring.

Voice dictation usage

Chat dictation uses ElevenLabs Scribe v2 Realtime. A workspace or organization dictation session has a three-minute maximum and records its charge when the token is issued, even if you stop speaking earlier. Its configured base cost is $0.024 per session, before the deployment's applicable cost policy.

The deployment must configure ELEVENLABS_API_KEY; dictation controls are hidden when the service is unavailable. Deployed-chat voice mode is a separate surface; see Chat deployments for its setup rather than applying the dictation session limit to it.

Related docs

• Secrets
• Logs
• API getting started