> ## Documentation Index > Fetch the complete documentation index at: https://docs.getswan.com/llms.txt > Use this file to discover all available pages before exploring further. # Credits > How Swan's org-wide credit pool works — what costs what, batching, rollover, and running out. 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 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. 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. Firing a trigger also carries a flat trigger fee, separate from whatever it does once it runs — 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). That fee is charged even if the rest of the run costs nothing. ## 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. * Searching for companies or people to get a preview list (before you enrich any of them) is free. * 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 an 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 run starts, Swan checks that your org has at least one credit remaining. If you're at zero, new runs are blocked outright. Once a run is underway, though, it's allowed to finish even if its own cost pushes your balance below zero — you won't have a run cut off mid-way for running out of credits. The actual charge is applied to your balance after the run completes. ## 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](https://agent.getswan.com/settings/usage). ## Running out of credits Once your balance hits zero, Swan blocks new chat runs, new trigger-driven runs, and delegating work to sub-agents — you'll see an insufficient-credits message instead. Triggers themselves are not paused or disabled; they simply fail to run (with a clear reason) until 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](https://agent.getswan.com/settings/subscription) — see [plans and billing](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's allowed to finish. Swan only blocks a run from starting when you're already at zero; it won't cut off in-progress work. **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](https://agent.getswan.com/settings/usage), which you can use to see which triggers or users are the heaviest consumers.