Credits and costs
What a credit is, what each paid call costs, and how credits are held, spent and given back.
This page explains credits, lists what each paid operation costs, and shows how to check your balance.
What a credit is
Paid work is priced in credits, the same credits the app shows. 1 credit is scoring one person. Everything else is priced against that.
Every operation says what it costs in the API reference. Most reads and changes are free.
Decimals in the API, whole numbers in the app
The API gives credits as decimals rounded to 2 places, so small jobs show their real size. For example, each new person a scout finds costs about 0.06.
The app shows whole numbers instead. Balances are rounded down, and costs are rounded up with a minimum of 1. So a balance of 1240.35 in the API shows as 1240 in the app.
What each paid operation costs
Prices are in credits. The word "about" means the price can differ a little between calls.
| Operation | Cost |
|---|---|
POST /scores | 1, the same as one person in a scoring run |
POST /scoring_runs | 1 per person scored, plus about 1.4 per Sales Navigator page |
POST /customer_profiles | From a website: about 7.6. From pasted text: about 6.1. The first research in an organization is free, from a website or pasted text. By hand: free, plus about 0.35 after the answer when the profile has a product description. |
PATCH /customer_profiles/{id} | free, plus about 0.35 after the answer when the profile part changes and has a product description |
POST /customer_profiles/{id}/research | about 7.6 |
POST /people/lookup | about 0.1 |
POST /people/search | about 1.4 a page |
POST /people/{id}/email | about 0.7, only when an email is found for the first time |
POST /messages/draft | about 3.4 |
POST /voices/learn | about 1 per voice learned, 20 voices a day per workspace |
POST /scouts/{id}/runs | about 0.06 per new person found, about 0.8 per fit check (quick) or 1 (deep), about 1.4 per search page, about 0.1 per page of posts or reactions |
POST /drafts/{id}/rewrite | about 6.9 for a first message, free for a follow-up |
POST /campaigns/{id}/launch | free to launch; 1 credit per person when their fit is checked, charged as they are checked |
POST /goals | free unless a website in the brief must be read; then the price of researching a company |
Creating a scout is free. An active scout spends credits when it runs.
Some operations are not part of the API-only plan, such as people search and lookup. The reference says so on each one.
Held, spent and given back
Credits for a whole job are set aside when it starts. A scoring run holds 1 credit for every person to score. While work is running, credits.held shows what is set aside and credits.spent shows what is used.
When the run ends, credits for people who were left out by the profile's rules, and any unused credits, are given back. A failed call charges nothing.
People scored for the same customer profile in the last 90 days are skipped and not charged, unless you turn skip_already_scored off. Every re-score is charged.
Check your balance
GET /credits shows what the organization can spend. The balance already leaves out credits held for work still running.
curl https://api.done.com/v1/credits \
-H "Authorization: Bearer $DONE_API_KEY"{
"object": "credits",
"balance": 1240.35,
"unlimited": false,
"plan": "growth",
"resets_at": "2026-11-01T00:00:00Z",
"workspace_limit": 300,
"workspace_used": 112.4
}unlimitedistrueon a plan that never charges.balanceisnullthen.workspace_limitandworkspace_usedshow a monthly limit set by an agency, if there is one. A call that would pass it is refused with a 402.resets_atis when the monthly allowance next resets. Top-up credits do not reset.
GET /credits/usage lists what credits were used for, newest first, one line per charge, refund or top-up. You see only the lines of the workspaces your key reaches. Like the statement in the app, it needs a key made by an organization owner or admin; any other key is refused with permission_too_low.
Check the balance before a large scoring run or a Sales Navigator search.
Limits that credits do not lift
- A key's daily credit cap. A key may use only so many credits a UTC day.
GET /meshows the cap and what is used. See Keys, workspaces and sign-in. - The month's search allowance. When it is used up, credits do not lift it. The 402 answer says when it resets.
- A workspace's monthly limit set by an agency.
Test keys
Work done with a done_test_ key charges no credits, and paid work returns realistic sample answers.
Running out
A call the workspace cannot pay for is refused with 402 insufficient_credits. The detail says how much the call needs and how much the workspace has. The fix says what to do, such as topping up credits in Plan and billing or sending fewer people.