Skip to main content
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

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

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.

​
Data API

The Data API is priced by the usage plan on the key that calls it, not by the tables on this page. GET /business/data/pricing lists the credits of each endpoint on your key’s plan.

​
Agents, research and website intent

​
Campaigns and accounts

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 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. You can poll as often as your 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, scanning for and merging duplicate 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 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.
  • A Data API job that runs the balance down ends as stopped with stoppedReason: "INSUFFICIENT_CREDITS", keeping the rows it finished. It does not resume: start a new job for the rest.
  • 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.

​
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.