Skip to main content
Credits are the currency that powers Gumloop. Every agent conversation spends credits based on the AI model it uses, the tools it calls, and how long it runs.
Agent credit costs are variable. The same agent might cost 2 credits for a quick question and 200 for a deep research task. You pay for what the agent actually does, not a fixed per-message price.

What a credit is worth

1 credit = $0.005

$1 buys 200 credits.

Model calls bill at cost

Divide the model cost by $0.005: a $0.03 model call is 6 credits.
Everything else on this page is priced in credits directly. Charges are rounded up to whole credits.

What you pay for

An agent chat is billed in real time, and its total is the sum of five things.
Priced on the tokens each message uses, converted from the model’s cost at $0.005 per credit. Three things drive it:
  • The model you pick. Faster, smaller models cost less per token than frontier models. See AI Models.
  • Conversation length. Every message carries the earlier conversation as context, so longer chats cost more per message.
  • How many tools are connected. Each tool adds its definition to the prompt, which adds tokens.
One message can also trigger several AI steps: when an agent uses tools it loops — decide which tool to call, read the result, then respond — and each step is billed separately.
Every successful tool call costs at least 1 credit. Failed calls are not charged.
  • Reading and writing to apps like Slack, Google Sheets, and Gmail costs that 1 credit and nothing more.
  • Tools that enrich or fetch external data, such as Apollo lead enrichment or Firecrawl web scraping, add their own charge on top.
Each tool’s MCP catalog page lists its cost.
5 credits per session-minute of active processing, with a minimum of 1 credit per response.Waiting on you to reply costs nothing — only the time the agent spends working counts. Enterprise customers running Gumloop in their own VPC are not charged for compute at all, since it runs on their infrastructure.
A chat that spent 400 credits on Chat & Reasoning, 10 on Compute, and 15 on Tool Calls pays a 34 credit fee (8% of 425, rounded up), for 459 credits in total.Enterprise plans can negotiate a different orchestration fee. If your organization has a negotiated rate, that rate applies instead of the 8% default everywhere it appears on this page.
When an agent runs a workflow, the workflow’s cost is added to the chat as a separate line. Workflows are billed on node costs alone — no compute, no orchestration fee. See Workflow Credits.

Example: researching a lead

You ask an agent to research a sales lead with Apollo, then summarize whether they are a good fit: Had the agent only read a Google Sheet and summarized it, the tool side would be just the 1 base credit, since Google Sheets charges nothing extra.
To lower this chat’s cost, run the agent on a cheaper model or add your own API key (BYOK). Both reduce the Chat & Reasoning portion. The Apollo charge stays the same, since it is a third-party cost passed straight through.

Plans and included credits

Every new account starts with a 14-day free trial of Pro. The trial requires a card, is a one-time offer per customer, and rolls into a paid Pro subscription when it ends unless you cancel first.
There is no free plan. Accounts created on the old free tier keep whatever credit balance they had left, but that balance no longer renews each month. To keep running agents, start a Pro trial or subscribe from the pricing page.
Credits don’t roll over month to month, except on Enterprise plans.

Running out of credits

Enable credit overage on your Subscription page to keep running past your monthly credits, billed at $0.005 per credit. Pro overage is always capped. The default ceiling is 1,000,000 overage credits per billing period ($5,000), and you can set a lower cap on your subscription page. Agents stop once the cap is reached, so overage can never run away unbounded. Enterprise plans set their own cap, or can choose to run uncapped. Need consistently more? Upgrade from the pricing page or talk to us about Enterprise.

Where to see what a chat cost

The running cost of a conversation appears as a badge with a coins icon in the chat header, next to the agent’s name, and updates live. For the full breakdown, open the Chat Details panel from the chat header. It lists one row per credit type the chat was actually charged for — Chat & Reasoning, Tool Calls, Workflows, Compute, Orchestration Fee, Evaluation & Self-Improvement, Subagents, or Other — alongside the model and source of the chat.
Credits that were waived rather than charged (BYOK model calls, and compute for VPC organizations) still appear, struck through and labelled Free, so you can see what the run would have cost.
Chat Details panel showing source, model, participants, and a credit breakdown split into Chat and Reasoning and Tool Calls

Tracking usage over time

Insights dashboard

The Insights dashboard (Settings > Organization > Insights) is the best place to see credit spend across all your agents and workflows. It shows total credits spent for the selected period, a credit spend and volume chart, and leaderboards of your top agents, models, and workflows.The tabs let you dig deeper: Models breaks spend down by AI model, and Credit Explorer lets you slice usage.
The Insights dashboard is an Enterprise feature.
Insights dashboard showing total credits spent, a credit spend and volume chart, and leaderboards for top agents, models, and workflows
For a transaction-level view, open Settings > Profile > Usage & Limits:
  • Grouped view (default): one row per agent conversation or workflow run, showing its total. Expand a row to see the individual charges inside it.
  • Detailed view: one row per individual charge, with the exact type and amount.
Filter by category to focus on Agent Chats or Workflow Runs. Many rows include a View link that jumps to the source conversation or run. Organization admins and managers can see usage across all users at Settings > Organization > Usage & Limits, which adds a User column.
You can also ask about credit usage in plain language. The analytics agent answers questions like “how many credits did we spend in the last 30 days, broken down by user?” and returns tables, charts, or CSV exports. It is available on the Insights page (Settings > Organization > Insights) and in Slack.
Export credit logs as CSV from Settings > Organization > Data Export for external analysis or compliance.

Reducing credit costs

  • Pick the right model. Start with the Recommended preset in Agent Preferences. Use Fastest for simple, high-volume tasks, and only reach for Smartest when a task needs deep reasoning. See AI Models.
  • Bring your own key (BYOK). Run model calls on your own provider key and the Chat & Reasoning portion drops to 0 credits (Pro plan or higher).
  • Start fresh conversations. A new chat for a new topic avoids carrying old context that inflates token costs.
  • Stay inside the short context window. GPT-5.6 and Grok 4.5/4.6 charge higher long-context rates once a request’s input tokens pass the short-window boundary (272K and 200K), and the higher rates apply to the whole request. Picking the smaller Context Window in AI Advanced Settings keeps chats on those models under the boundary.
  • Connect only the tools you need. Every tool definition adds tokens to the prompt.

How BYOK works

Gumloop runs your model calls on your key and charges you 0 credits for them — you pay your provider directly for the tokens instead.Because the model spend leaves your credit balance entirely, agent chats on BYOK carry a 16% orchestration fee instead of 8% (your Enterprise rate plus 8 points, if you have one), calculated on what the run would have been worth. Workflows have no orchestration fee at all, so a BYOK AI node costs nothing.In practice BYOK is still far cheaper. Taking the chat from the example above — 400 credits of model usage, 10 of compute, 15 of tool calls:You cover the model tokens directly with your provider instead.Requires Pro plan or higher and your own OpenAI, Anthropic, Google AI, Perplexity, SpaceXAI, or Fireworks AI account. Each key only waives the models that provider serves — a Fireworks key covers the open models Gumloop runs on Fireworks (DeepSeek V4 Flash and Pro, Kimi K3, Kimi K2.7 Code, GLM-5.2, MiniMax M3, Qwen3.8 Max).Add a key under personal credentials at Connectors, or add a shared team key for the whole team. Enterprise admins can set organization-level keys. See AI Models.

Credit Notification Preferences

Gumloop can email you when your organization’s credit usage crosses key thresholds. Manage these on your Subscription page.
  • Out of Credits Notification: an email when credits reach zero. On by default.
  • Credit Usage Notifications: an email when usage crosses a threshold. Defaults to 75% and 90%. Add, remove, or reset thresholds as needed.
Credit Notification Preferences showing Out of Credits Notification toggle and Credit Usage Notifications with configurable thresholds at 75% and 90%
Set these up early so you have time to top up before running out.

Per-Chat Credit Warnings

Admins and Security role holders can also set per-chat credit warnings through Custom Roles. When a single chat’s spend crosses a configured threshold (e.g. 5,000 or 10,000 credits), the agent pauses and creates an Action Request for approval before continuing, so no single conversation can consume an unexpected amount of credits.

Workflow Credits

Workflows are billed differently from agent chats:
Most nodes are free. AI nodes are the exception — like agents, they are billed by token usage, so a short prompt costs far less than a long-context one.
Compute and the orchestration fee apply to agent chats only. Workflow runs are billed on node costs alone, whether the workflow runs on its own or is called by an agent.

Node credit costs

Most native Gumloop nodes cost nothing:
  • Text manipulation (Combine Text, Text Formatter, Find & Replace)
  • Logic (If/Else, Switch, Router)
  • Loops (For Each, Loop Mode)
  • Data transformation (Filter, Join, Split)
  • Most integrations (Google Sheets, Slack, Gmail, Airtable, Salesforce, etc.)
  • Input/Output nodes
Hover over any node’s ’?’ icon in the builder to see its credit cost.
Enrichment nodes get expensive in loops. Enriching 100 contacts costs 6,001 credits (1 + 60 x 100).
Failed workflows: if a workflow stops partway, you are only charged for the nodes that ran before the failure.Loop mode: nodes in loop mode run once per item, so multiply the node cost by the number of items (a 60 credit Enrich Contact node over 10 contacts = 600 credits).

Interactive artifact costs

When you open an interactive artifact that pulls live data, a Python script runs in a secure sandbox. This is billed at roughly 1 credit per 55 seconds of runtime, with a minimum of 1 credit per run. The viewer pays, not the creator. Most scripts finish in seconds, so the typical cost is 1 credit per load.

Learn more

AI Models

Choose the right model and set up BYOK

Pricing plans

Current plans, included credits, and overage

Why we moved to credits

The reasoning behind the model