> ## Documentation Index > Fetch the complete documentation index at: https://docs.fuseai.com/llms.txt > Use this file to discover all available pages before exploring further. # Credits & billing > What every API operation costs in credits, what is free, when the balance is checked, and how to avoid paying for the same search twice. Credits are your workspace's currency for data operations. Every search result, saved row, and enrichment draws from a single workspace-level balance — the same one your team spends in the app, so API usage and in-app usage debit the same pool. ## Check your balance ```bash theme={null} curl https://api.tryfuse.ai/api/v1/business/credits -u "af_YOUR_KEY:" ``` ```json theme={null} { "balance": 8250 } ``` Check it before large operations — a `save-to-list` of thousands of rows debits per row saved. `POST /business/credits/usage` returns the spend ledger by product and day. ## What debits credits ### Search, saving and enrichment | Operation | Billing | | - | - | | `POST /business/prospects/search` | 2 credits per profile returned. The balance must cover `size` × 2 first. | | `POST /business/prospects/search/save-to-list` with `enrich: "none"` | 2 per profile saved, including people already on the list. The balance must cover `limit` × 2 first. | | `POST /business/prospects/search/save-to-list` with `email`, `phone` or `phone_and_email` | No charge for the save itself. Each email or phone found is billed at the finding prices below. | | `POST /business/companies/search` | 2 per company returned. The balance must cover `size` × 2 first. | | `POST /business/companies/search/save-to-list` | 2 per company saved, charged as it saves. | | Finding emails and phones, on a [list](/guides/working-with-lists#enrich-the-contacts-you-have), an import or a save | Work email: 20 when Fuse's data finds it, 50 when a partner provider does. Personal email: 100, only when personal emails are prioritised and one is found. Phone: 200. 5 instead of the data price when your own provider key found it. Nothing when nothing is found. | | `validate_emails` on a list | 10 per address checked | | `demographics` on a list or an import | 2 per contact matched | | `POST /business/imports/{importId}/commit` | Free with `enrich: "none"`. With a finding mode, 2 per row matched to the database, plus the finding prices. | | [Smart columns](/guides/smart-columns) | 20 per row answered with `standard`, 100 with `deep_research`, charged as each row is answered. Failed rows are free. The column's `creditsPerRow` shows its rate. | Before a finding job starts, the balance must cover every contact at the highest price it could cost: 50 per email (100 when personal emails are prioritised), 200 per phone, 250 for both. Most contacts then cost less, because you pay only for what is found and Fuse's own data costs 20 per email. ### Agents, research and website intent | Operation | Billing | | - | - | | Discovery [agents](/guides/create-an-agent) (new job starters, posts, job postings, headcount, funding, people matching filters) | 100 per contact or company delivered, plus the finding prices when `enrichEmail` or `enrichPhone` finds something. Starting the agent is free. | | Web monitors | 50 per result saved to the list. Setup and runs are free. | | People and companies watchers | 50 per watched contact or company on every check, daily unless you set `frequency`. No setup fee. | | Job-changes watcher | 50 per job change delivered | | LinkedIn profile and post scrapes | 50 per profile added | | Deep Research runs | 20 per successful provider step on Fuse's keys, 5 per step on your own provider key. Steps on Fuse's keys stop at the `effort` cap: 1,000, 2,000 or 5,000. Steps on your own key are billed on top of it. | | Website visitor identification | 10 when the tracking tag resolves a new visitor's IP to a company, and 5 per identified visit, up to your monthly cap (`monthlyCreditLimit` on `PATCH /business/website-tracking`) | ### Campaigns and accounts | Operation | Billing | | - | - | | Campaign email sends | 10 per AI-written email and 5 per template email. Included, so free, on the Free, Solo and Team plans. | | Re-verifying emails before send | 2 per address each time it is checked before a send, when `validateEmailsBeforeSendEnabledAt` is set on the campaign. If the balance runs out, the campaign is deactivated. | | LinkedIn accounts | 2,500 per connected account when it is connected and every 30 days after. Included on the Solo and Team plans. LinkedIn messages and connection requests are not charged per send. | | Renting a phone number | 2,500 when you rent it. See [Your phone numbers](/dialer/phone-numbers). | `POST /business/prospects/search/save-to-list` does **not** reuse a prior `POST /prospects/search` — passing the same filters runs the search again, so previewing first and then saving pays for the search twice. Preview with small `size` values to tune filters, then call `save-to-list` once. Saving a hand-picked subset of results is not supported; narrow filters instead. This design exists because saving is a server-side pipeline: the search, the save, and the follow-on enrichment run as one job, which is what lets a single call populate a fully enriched list. The [build-a-list guide](/guides/build-a-list-from-search) shows the cheap preview-then-save workflow end to end. ## What never debits credits Reads are free: listing lists, reading rows, checking campaign status, polling and downloading [exports](/guides/export-a-list). You can poll as often as your [rate limits](/concepts/rate-limits) allow — rate limits are a separate mechanism and always apply, whether or not a request costs credits. Uploading contacts with `POST /business/lists/{listId}/contacts`, parsing an import, committing one with `enrich: "none"`, copying rows between lists, building a [knowledge hub](/guides/knowledge-hubs), scanning for and merging [duplicate contacts](/guides/deduplicate-contacts), and pushing a list to your CRM cost nothing either. ## Insufficient balance Searches, saves of people, finding emails and phones, smart columns, watchers and scrapes check the balance before they start. If it is short, the request fails with [`402 INSUFFICIENT_CREDITS`](/concepts/errors#insufficient_credits) before any work runs, so nothing is billed. Top up or reduce the request size, then retry. Other work is charged as it runs, and stops or pauses when the balance runs out, keeping what it already did: * A company save, `validate_emails` and `demographics` stop partway. * An enrichment job that runs the balance down pauses as `stopped` until you top up and resume it in the app. * Deep Research checks the balance before each provider step. * Agents pause themselves when a delivery or a watcher's check cannot be covered. See [Agents](/signals/agents#what-it-costs). ## Plans and pricing Credit allowances and top-up pricing vary by plan, so this page quotes credits rather than prices. Your plan's details and top-up options live on the **Billing** page in the app. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.