Skip to main content
The Data API is pay-as-you-go. You add credits to your workspace, and searches spend from that balance as they run. You do not sign a contract with any data provider.

1 credit = $1

Credits are prepaid US dollars. Fractions of a credit are charged as they are spent.

Cost plus 5%

You pay what the underlying data costs, plus a 5% platform fee. Nothing else.

Capped per search

Set max_credits and a search can never spend more than that.

How a search is charged

Each search calls data providers on your behalf. What those calls cost is passed through to you, and Avina adds 5% on top.
Try it: What a search costs depends on what it has to do, not on a fixed price per result: The search’s own credits_charged field is the source of truth. It updates while the search runs and is final once the search reaches a terminal status.

What is free

Control what you spend

Cap a search with max_credits

The search stops starting new work when it has spent 20 credits. It finishes with stop_reason: usage_limit_reached and keeps every result found up to that point. Without max_credits, a search can spend up to your remaining balance.
Set max_credits on every search you start from code. If limit has a typo, or a query turns out to match very few companies, the mistake then costs at most max_credits.

Start small

Run a new query with limit: 5 first. credits_charged divided by progress.accepted gives you the cost per result for that query, which you can use to budget the full run.

Stop a search early

Cancel a search to stop new spending. Provider calls already in progress may still finish and be charged.

Do not pay twice for a retry

Send an when you start a search. If the request times out and you retry with the same key, you get the original search back instead of starting, and paying for, a second one. See Errors and retries.

Check your balance

GET /usage returns your balance and what you have spent this billing period.
credits_remaining is your balance. To add credits, top up in the Avina dashboard.

When you run out

  • Starting a search with no credits returns 402 usage_limit_reached. Nothing is started or charged.
  • Running out mid-search stops new work. The search completes with stop_reason: usage_limit_reached and its results stay readable.
  • Matches found after a limit was reached are counted in progress.not_returned.

Frequently asked questions

No. Cost follows the provider calls a search needs, so two searches for 20 companies can cost different amounts. Run a small search first to measure cost per result for your query.
You are charged for the provider work that was done, even if no candidate passed every requirement. A search that is rejected, or that stops with query_needs_clarification, is not charged. Use max_credits to bound a search you are unsure about.
No. Status and results are free to read as often as you like.
Not for a request that one provider can fully answer: you pay that provider’s cost plus 5%. The saving is in what you do not have to build and buy: one integration and one bill instead of several, and verification that keeps non-matches out of your pipeline.
Contact support@avina.io for the terms on your plan.

Next steps

Get credit usage

The usage endpoint reference.

Search lifecycle

Stop reasons, including spend limits.