Pricing
25 search results per Credit, and nothing for a search that finds nothing
Reading records costs one Credit per five. That is the whole rate card, and every plan bills at it: what a larger plan buys is a larger monthly allowance, not a different rate per call. Everything below is the exact settlement behaviour behind those numbers.
Plans
- Plan
- Free
- Monthly price
- $0
- Credits
- 100 one-time, valid 30 days
- Which is
- 2,500 searches or 500 records
- Plan
- Go
- Monthly price
- $9
- Credits
- 300 per month
- Which is
- 7,500 searches or 1,500 records
- Plan
- Plus
- Monthly price
- $19
- Credits
- 1,000 per month
- Which is
- 25,000 searches or 5,000 records
- Plan
- Pro
- Monthly price
- $59
- Credits
- 5,000 per month
- Which is
- 125,000 searches or 25,000 records
Free Credits are granted once and expire; paid Credits arrive with each confirmed renewal. Nothing you build has to change when you move between plans, because no rate below moves with them.
Pay as you go
You do not need a plan to buy Credits. One rate at every amount: $1 buys 30 Credits, and purchased Credits never expire.
- Pay
- $10
- Credits
- 300
- Which is
- 7,500 searches or 1,500 records
- Pay
- $25
- Credits
- 750
- Which is
- 18,750 searches or 3,750 records
- Pay
- $50
- Credits
- 1,500
- Which is
- 37,500 searches or 7,500 records
- Pay
- $100
- Credits
- 3,000
- Which is
- 75,000 searches or 15,000 records
- Pay
- $500
- Credits
- 15,000
- Which is
- 375,000 searches or 75,000 records
That works out to $0.0333 per Credit, above the $0.030 a Credit costs on Go. Pay-as-you-go is the base price; a plan is the discount for committing to a month. Nothing else changes: the rates below are the same whichever way you paid.
Automatic top-up adds Credits with a saved card when your balance drops below a level you choose. You set the amount, the level, and a monthly limit it will never spend past. The level has to stay below what one top-up adds, or every top-up would land under it and immediately trigger the next.
Purchased Credits are spent last
Balance lifetime and spend order
- Current visible Credits are the total active, unexpired balance.
- Existing free or legacy Credits expire 14 days after the human-run migration backfill. The Billing page shows the server-reported expiry date and days remaining.
- Paid invoices add idempotent period buckets without deleting earlier usable buckets.
- Usage spends the soonest-expiring active bucket first.
- Purchased Credits have no expiry, so they sit last in that order and survive a renewal or a plan change.
Server-confirmed grant boundary
Usage pricing
- Product action
- Query Spec search on people, jobs, or companies
- Debit rule
- ceil(returned IDs / 25)
- No-charge outcome
- 0 IDs returned
- Product action
- People natural-language search
- Debit rule
- 5 + ceil(returned IDs / 25)
- No-charge outcome
- Successful requests keep the 5 Credit base
- Product action
- Profile, job, or company detail
- Debit rule
- ceil(found records / 5)
- No-charge outcome
- 0 records found, or not_found
A query is translated before anything is charged, so a request refused for an unknown field or a malformed tree costs nothing. Validation failures, timeouts, upstream 5xx responses, internal retryable failures, and not_found rows are not charged either.
Paging spends per page. A search that walks four pages of 250 IDs costs the same as one that takes 1,000 in a single page, because both return 1,000 IDs.
Contact enrichment has no price yet
Plan changes
- Event
- Start
- Effect
- The confirmed paid-plan bucket is additive after signed-webhook processing.
- Event
- Upgrade
- Effect
- Stripe calculates the immediate net amount. After confirmed payment, a new period starts and the target plan's full monthly Credits are added.
- Event
- Downgrade
- Effect
- The current plan and Credits remain usable through period end. The lower plan starts after the next paid renewal is confirmed.