Skip to main content
You describe the companies or people you want. Avina works out what that means, finds across its data providers, checks each one against every requirement, and returns only the ones that pass. Every search goes through the same four stages. Press Play, or select a stage:
The companies in the animation are illustrative.

​
The four stages

1

Interpret the request

A plain-language query is split into requirements of two kinds:
  • Filters: exact conditions on known fields, such as country, employee count and company type.
  • Criteria: free-text statements, such as “offers same-day implants”, for anything no field covers.
Job titles, industries and places are normalized, so “SDR” and “sales development representative” are treated as the same role.Ambiguous wording does not stop a search. Avina reads it the likeliest way and reports the reading in assumptions. A search stops before any provider is called, with stop_reason: query_needs_clarification, only when a requirement cannot be checked from the data available, or when the query gives nothing to search on.You can run this stage on its own, at no cost, with Parse.
2

Route to data sources

Different sources hold different kinds of data: company databases, job listings, technology data, and AI search of the public web. Avina picks sources from what the request contains.
  • Structured conditions, such as industry, size or an open job, go to data providers that can filter on them directly.
  • Requirements that need research, such as “opened a location this year”, go to AI web search.
  • If the data providers run out of candidates, the search continues with AI web search.
You do not choose providers, and you do not maintain an integration with any of them. See The data network.
3

Verify every requirement

Each candidate is checked one requirement at a time. Every check ends in one of three : matched, not matched, or unknown. Missing information is never treated as a “no”, and an unknown is never treated as a “yes”.A company or person is accepted only when every requirement is matched. See Evidence and verdicts.
4

Return results

Accepted records are and added to the search’s results. You can read results while the search is still running.The search stops when it reaches your limit, runs out of sources, or reaches a spend limit. stop_reason tells you which.

​
What you get back

A search is . POST returns immediately with a search id. You then poll the search’s status and read results page by page as they arrive. Each result carries the reason it matched:
One result (shortened)
Example values on this page are illustrative. Field definitions are in the API reference.

​
What a search does and does not promise

​
Next steps

Three ways to search

Plain language, free-text criteria and structured filters.

Evidence and verdicts

How to read why a result matched.

Search lifecycle

Statuses, stop reasons, cancellation and partial results.

Quickstart

Run your first search.