Skip to main content
Credits are a single org-wide pool, shared by everyone in your org — they aren’t split up per seat or per person. Every trigger run and chat conversation draws from the same balance.

​
What costs credits

Most of Swan’s paid actions cost 1 credit each: web research, scraping a URL, building a sequence, generating a presentation, writing to your CRM, running code, and calling a custom tool (including tools from an MCP server you’ve connected). A few actions cost more because they call more expensive third-party data providers:
  • Enriching a full contact or company profile costs 1 credit, charged only when enrichment data is returned.
  • Enriching an email address or phone number costs 2 credits each, charged only on a successful match.
  • Fetching business/intent events costs 1 credit per event returned.
  • Fetching latest website changes costs 1 credit per new provider date for each company. Repeated same-date results, unmatched companies, and no-data companies are free.
  • Finding similar companies costs 1 credit per 5 results returned, rounded up; no matches cost nothing.
Costs for tools from other connected apps (HubSpot, Salesforce, and so on) vary by the specific action — most simple writes cost 1 credit, but check the tool’s own description for anything unusual. Most trigger sources also carry a processing fee, separate from whatever the run does — this ranges from 1 to 2 credits depending on the trigger type (for example, a scheduled or LinkedIn-engagement trigger costs 1 credit to fire; a business-event or intent-signal trigger costs 2). Website Changes costs 1 credit when a new provider-reported change is classified, even when the filter rejects it; unchanged, missing-data, and excluded-company checks are free.

​
What’s free

  • Using Swan’s underlying AI (including its reasoning/thinking) doesn’t cost credits by itself — you’re only charged for the actions it takes.
  • Filter-based company or people search previews are free. Similar-company lookup is a separate paid data action.
  • Reading your own existing data in Swan doesn’t cost credits.

​
Batch discounting

If a single run performs the same non-data action many times — for example, updating ten CRM records with the same tool — you’re charged once for that batch, not once per record. Actions that pull in new external data per record (like enriching a contact, company, email, or phone number, or fetching a URL) are the exception: those are charged per record, since each one is a separate lookup against a paid data provider.

​
When credits are charged

Before a new run starts, Swan checks that your org has at least 10 credits remaining. Long-running trigger executions can span multiple work slices; after they start, later slices only require one remaining credit. Credits are applied as execution work is persisted, so a run that reaches zero can be stopped at its next slice boundary.

​
Rollover

On monthly plans, unused credits carry over into your next billing cycle, up to a cap of twice your plan’s monthly allotment — anything beyond that cap doesn’t carry forward. On annual plans the cap is lifted: unused credits keep rolling forward without limit within your 12-month term.

​
Usage alerts

Your org gets a notification when you cross 50% and 90% of your monthly credit allotment, and again once you’ve used it all. Check current usage any time at Settings → Usage.

​
Running out of credits

Once your balance drops below 10, Swan blocks new chat runs and new trigger-driven runs — you’ll see an insufficient-credits message instead. Delegating work requires at least 10 credits overall and five available credits per delegated task, whichever is greater. Triggers themselves are not paused or disabled; they simply fail to start until enough credits are available again. Your dashboard, history, and existing data all stay fully accessible either way. If you need more credits before your next renewal, you can buy a one-time top-up from Settings → Subscription — see plans and billing.

​
Common questions

Does Swan tell me how many credits a run will use before I start it? No, there’s no upfront estimate — credits are deducted based on what the run actually does. You can use the cost breakdown above to estimate roughly, and check usage after the fact in your execution history. If I run a batch of 50 identical CRM updates, am I charged 50 credits? No — identical, non-data actions in the same run are coalesced into a single charge. Per-record data lookups (enrichment, business events, URL scrapes) are still charged per record. What happens if a run goes over my remaining balance mid-way? It can finish its current work slice. If it reaches zero and needs another slice, Swan stops it before more work begins. Are trigger runs paused automatically when I run out of credits? No. The trigger stays enabled, but each firing will fail with an insufficient-credits message until you have credits again. Do unused credits roll over indefinitely? On monthly plans, no — rollover is capped at twice your plan’s monthly credit allotment. On annual plans, credits roll over without a cap for the duration of your term. Can I see which user or trigger is using the most credits? Yes, credit usage is broken down by execution at Settings → Usage, which you can use to see which triggers or users are the heaviest consumers.