Cost calculation

Sim calculates workflow usage from the base run charge, billable model usage, and hosted tool usage.

Credits

Sim uses credits as the unit of measurement for all usage. 1 credit = $0.005.

All plan limits, usage meters, and billing thresholds are displayed in credits throughout the Sim UI. Dollar amounts in this documentation are provided for reference.

How Costs Are Calculated

Workflow runs can include these cost components:

Base Run Charge: 1 credit ($0.005) per run

AI Model Usage: Variable cost based on token consumption.

Hosted Tool Usage: Per-operation charges for tools using Sim-provided keys.

modelCost = (inputTokens × inputPrice + outputTokens × outputPrice) / 1,000,000
totalCredits = baseRunCharge + (billableModelCost + hostedToolCost) × 200

Model Breakdown in Logs

For workflows using AI blocks, you can view detailed cost information in the logs:

The model breakdown shows:

• Token Usage: Input and output token counts for each model
• Cost Breakdown: Individual costs per model and operation
• Model Distribution: Which models were used and how many times
• Total Cost: Aggregate cost for the entire workflow run

Pricing Options

With Sim-provided model keys, model usage is billed through Sim. With your own keys, you pay the provider directly; the workflow base charge still applies. Check the provider's current pricing when estimating a run, and use the run's recorded usage to compare configurations.

Hosted Tool Pricing

When workflows use tool blocks with Sim's hosted API keys, costs are charged per operation. Use your own keys via BYOK to pay providers directly instead.

Bring Your Own Key (BYOK)

Use your own API keys for supported providers instead of Sim's hosted keys to pay base prices with no markup.

Supported Providers

The BYOK settings page groups providers the same way.

Key scopes

A key is stored at one of two scopes.

Organization keys let you set a provider key once instead of repeating it in every workspace. A new workspace added to the organization picks them up automatically.

Which key a run uses

Precedence is resolved per provider, not per workspace:

1. The workspace's own key for that provider, if it has one
2. Otherwise, the organization's key for that provider
3. Otherwise, Sim's hosted key, with the multiplier applied

So a workspace that stores its own OpenAI key still inherits the organization's Anthropic key. A workspace key always wins over the organization key for the same provider — adding one is how you override inheritance for a single workspace.

The BYOK settings page tags every provider your workspace is inheriting, so you can see which keys come from the organization before you override them.

Setup

1. Navigate to Settings → BYOK in your workspace
2. Choose Workspace or Organization (organization admins only)
3. Click Add Key for your provider
4. Enter your API key and save

You can store several keys per provider per scope. Requests are distributed evenly across the keys in whichever scope is in effect.

Deleting a workspace key makes that workspace fall back to the organization key if one exists, and to Sim's hosted keys otherwise. Deleting an organization key makes every workspace that was inheriting it fall back the same way.

If your organization's plan lapses, organization keys stop applying and those workspaces fall back to Sim's hosted keys with the multiplier. The keys are retained, and organization admins can still delete them, but adding or updating them requires an active organization plan.

Voice Input

Voice input uses ElevenLabs Scribe v2 Realtime for speech-to-text transcription. It is available in Chat and in deployed chat voice mode.

Each voice session is billed when it starts. In deployed chat voice mode, each conversation turn (speak → agent responds → speak again) is a separate session. Multi-turn conversations are billed per turn.

Plans

Sim has two paid plan tiers - Pro and Max. Either can be used individually or with a team. Team plans pool credits across all seats in the organization.

To use Pro or Max with a team, select Get For Team in subscription settings and choose the tier and number of seats. Credits are pooled across the organization at the per-seat rate (e.g. Max for Teams with 3 seats = 75,000 credits/mo pooled).

Internal organization members use seats and contribute to the team's pooled credit allocation. External workspace members do not join your organization or count toward its seat total. They appear in the roster with an External label.

Weekly Refresh Credits

Paid plans include a weekly credit allowance that does not count toward your plan limit. Each week, usage up to the weekly refresh amount is excluded from billable usage. This allowance resets every 7 days from your billing period start and does not carry over - use it or lose it.

For team plans, the weekly refresh scales with seats (e.g. Max for Teams with 3 seats = 12,000 credits/week).

Annual Billing

All paid plans are available with annual billing at a 15% discount. Switch between monthly and annual billing in Settings → Subscription.

Team plans follow the same pricing per seat.

On-Demand Billing

By default, your usage is capped at the credits included in your plan. To allow usage beyond your plan's included amount, you can either enable on-demand billing or manually edit your usage limit to any value above your plan's minimum.

• Enable On-Demand: Removes the usage cap entirely. You pay for any overage at the end of the billing period.
• Edit Usage Limit: Set a specific cap above your plan's included amount to control how much overage you're willing to allow.
• Disable On-Demand: Resets your usage limit back to the plan's included amount (only available if your current usage hasn't already exceeded it).

Plan Limits

Workspaces

Team and Enterprise plans unlock shared workspaces that belong to your organization. Every workspace created under a Team or Enterprise plan is organization-owned: Owners and Admins can create unlimited shared workspaces, while organization Members cannot create workspaces. When someone joins the organization as an internal member, personal workspaces they own move into the organization and their usage is billed to it from then on. Internal members count toward your seat total — Enterprise invites require an available seat at invite time, while Team plans add a seat automatically when the invitee accepts. External workspace members get access to specific workspaces without joining your organization or using one of your seats; they must already be on a paid Sim plan (their own Pro or Max subscription, or another organization that seats them), and invitees who already belong to another organization always join this way. When a Team or Enterprise subscription is cancelled or downgraded, existing shared workspaces remain accessible to current members but new invites are disabled until the organization is upgraded again.

Rate Limits

Rate limits follow the paid tier: Pro and Pro for Teams share the Pro limits, while Max and Max for Teams share the Max limits.

Concurrent Executions

The concurrency limit applies per billing account. For organization-based plans, the limit is shared by all workspaces, members, and API keys under that organization. Teams plans follow their tier: Pro for Teams uses the Pro limit and Max for Teams uses the Max limit. An admitted async execution holds a slot while queued and running; synchronous executions hold one while running. Workflow-in-workflow blocks execute inside the parent run and do not consume another concurrency slot.

File Storage

Storage follows the paid tier: Pro and Pro for Teams share the Pro limit, while Max and Max for Teams share the Max limit. Organization storage is pooled across the organization's workspaces.

Run Time Limits

Sync runs complete immediately and return results directly. These are triggered via the API with async: false (default) or through the UI. Async runs (triggered via API with async: true, webhooks, schedules, polling triggers, or table workflow columns) run in the background. A direct async API request can shorten the account policy for that request, but cannot extend it.

Billing Model

Sim uses a base subscription + overage billing model:

How It Works

Pro Plan ($25/month - 6,000 credits):

• Monthly subscription includes 6,000 credits of usage
• Usage under 6,000 credits → No additional charges
• Usage over 6,000 credits (with on-demand enabled) → Pay the overage at month end
• Example: 7,000 credits used = $25 (subscription) + $5 (overage for 1,000 extra credits at $0.005/credit)

Team Plans:

• Usage is pooled across internal team members in the organization
• Usage in an organization-owned workspace is billed to that workspace's organization, including work performed by external collaborators
• Each authenticated actor's usage is also counted toward their member cap for that organization
• Overage is calculated from total team usage against the pooled limit
• Organization owner receives one bill

Enterprise Plans:

• Fixed monthly price, no overages
• Custom usage limits per agreement

Threshold Billing

When on-demand is enabled and unbilled overage reaches $100, Sim automatically bills the full unbilled amount.

Example:

• Day 10: $120 overage → Bill $120 immediately
• Day 15: Additional $60 usage ($180 total) → Already billed, no action
• Day 20: Another $80 usage ($260 total, $140 unbilled) → Bill $140 immediately

This spreads large overage charges throughout the month instead of one large bill at period end.

Usage Monitoring

Monitor your usage and billing in Settings → Subscription:

• Current Usage: Real-time credit usage for the current billing period
• Usage Limits: Plan limits with a visual progress bar
• On-Demand Billing: Toggle on-demand billing to allow usage beyond your plan's included credits
• Plan Management: Upgrade, downgrade, or switch between monthly and annual billing

Programmatic Usage Tracking

You can query your current usage and limits programmatically using the API:

Endpoint:

GET /api/users/me/usage-limits

Authentication:

• Include your API key in the X-API-Key header

Example Request:

curl -X GET -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" https://sim.ai/api/users/me/usage-limits

Example Response:

{
  "success": true,
  "rateLimit": {
    "sync": {
      "isLimited": false,
      "requestsPerMinute": 150,
      "maxBurst": 300,
      "remaining": 300,
      "resetAt": "2025-09-08T22:51:55.999Z"
    },
    "async": {
      "isLimited": false,
      "requestsPerMinute": 1000,
      "maxBurst": 2000,
      "remaining": 2000,
      "resetAt": "2025-09-08T22:51:56.155Z"
    },
    "authType": "api"
  },
  "usage": {
    "currentPeriodCost": 12.34,
    "limit": 100,
    "plan": "pro_6000"
  }
}

Rate Limit Fields:

• requestsPerMinute: Sustained rate limit (tokens refill at this rate)
• maxBurst: Maximum tokens you can accumulate (burst capacity)
• remaining: Current tokens available (can be up to maxBurst)

Response Fields:

• currentPeriodCost reflects usage in the current billing period (in dollars)
• limit is derived from individual limits (Free/Pro/Max) or pooled organization limits (Team/Enterprise)
• plan is the highest-priority active plan associated with your user

Purchasing Additional Credits

Pro and Team plan users can buy additional credits at any time in Settings → Subscription → Credit Balance:

• Range: $10 to $1,000 per purchase
• Conversion: 1 credit = $0.005 (a $10 purchase adds 2,000 credits)
• Availability: Credits are added immediately after payment
• Expiration: Purchased credits do not expire
• Refunds: Purchases are non-refundable
• Team plans: Only organization owners and admins can purchase credits. Purchased credits are added to the team's shared pool.

Cost Optimization Strategies

• Model Selection: Choose models based on task complexity. Simple tasks can use GPT-4.1-nano while complex reasoning might need o1 or Claude Opus.
• Prompt Engineering: Well-structured, concise prompts reduce token usage without sacrificing quality.
• Local Models: Use Ollama or VLLM for non-critical tasks to eliminate API costs entirely.
• Caching and Reuse: Store frequently used results in variables or files to avoid repeated AI model calls.
• Batch Processing: Process multiple items in a single AI request rather than making individual calls.

Next Steps

• Review your current usage in Settings → Subscription
• Learn about Logging to track run details
• Explore the External API for programmatic cost monitoring
• Check out workflow optimization techniques to reduce costs