Gumloop Pricing: Pro Credits, Overage, and Enterprise

Buying path

Start with the card-required trial and build one representative agent before accepting the recurring subscription. The useful test covers a complete business cycle with the real model, connectors, tools, and trigger frequency expected in production. The resulting credit breakdown shows whether the entry allowance is a realistic baseline.

The self-serve route is also the normal starting point for a shared organization. Seats and teams do not create separate bills, but every member draws from one organization credit pool. Decide who owns the subscription, connected credentials, production automations, and spend alerts before inviting a broad group, because collaboration can increase usage without changing the headline seat count.

Upgrade triggers

Move from trial to paid access when repeated agent runs produce enough durable value to justify the recurring account. Credit consumption is only one signal. Production triggers, shared credentials, team ownership, API access, and the need to keep automations running after an individual builder steps away can make the paid boundary operationally necessary.

A sales-assisted agreement becomes relevant when the published self-serve concurrency regularly blocks work or when skipped triggers and rejected API requests are unacceptable. Automatic queuing, custom capacity, rollover, company-wide analytics, identity provisioning, auditability, model governance, private-network connectivity, support, and procurement controls should each solve a named requirement rather than act as generic insurance.

API and team boundaries

The REST API, SDKs, CLI, webhooks, and Gumloop MCP are ways to create, invoke, or control the same platform. They do not have a separate public developer tariff. Work started programmatically still consumes organization credits and competes for the same workflow or agent concurrency, so an integration owner must handle rate-limit responses and avoid assuming the API creates extra capacity.

Teams are access and ownership spaces inside an organization, not separate subscriptions or independent credit wallets. The organization pays for work launched from personal spaces and teams alike. Personal credentials, shared team credentials, and organization-level controls also have different scopes, so the account used by a node or agent should be chosen deliberately.

Bringing a model provider key creates another commercial boundary. For agent runs, the Credits documentation says supported BYOK model calls use zero Gumloop credits while the provider bills tokens directly; tool calls and compute still cost credits, and the orchestration fee rises from 8% to 16%. The chat completions API instead gives BYOK users a 50% discount, so budget that surface separately.

Final pricing check

Before paying, verify the card and automatic-renewal terms, billing cycle, included credit allocation, overage setting and ceiling, rollover rule, and the concurrency behavior for both workflows and agents. Model long-context rates, paid tool calls, enrichment, scraping, custom code, MCP calls, image generation, transcription, and interactive artifacts can each change consumption in ways a simple run count will not capture.

For an enterprise order, put the credit allocation, orchestration rate, rollover, overage or uncapped-use policy, concurrency and queue limits, support level, VPC responsibility, data retention, identity lifecycle, audit access, model and connector policies, and renewal terms into the reviewed agreement. Keep separately billed model-provider accounts and any external service charges assigned to named owners.