Skip to main content
No single data provider is best at everything. One has detailed company records, another indexes job listings, a third finds companies on the open web that no database has categorized. Teams that need broad coverage end up buying, integrating and reconciling several. The Data API puts those sources behind one request. You describe what you want. Avina decides which sources to query and checks what comes back.

What is in the network

Company databases

Structured facts about a company, often called : industry, location, employee count, revenue, company type, funding and founding year.

Job and hiring data

Open job listings and recent hires, by title and date. Powers “is hiring” and “just hired” requirements.

Technology data

Which products and vendors a company uses, and when the technology was detected.

AI web search

Live research across the public web for requirements no database has a column for.

People and contact data

Who works where, in what role, with work emails and phone numbers on request.

Verification

Email verification, and evidence checks that confirm a claim before it reaches you.
Results are normalized into one schema, so a company looks the same whichever provider found it. Provider names are not part of the response.

How sources are chosen

Before a search retrieves anything, Avina looks at what the request contains and picks the sources that can answer it. Two rules apply to every search:
  • When data providers run out of candidates, the search continues with AI web search.
  • Every candidate is checked against all of your requirements, whichever source found it.
Anything you can express as a structured filter is checked against data records rather than researched, which costs less than a free-text criterion.

Deduplication

The same company can come back from several providers under slightly different names. Avina merges candidates into one record per company website domain before checking them and before counting them.
  • A company appears once in a search’s results.
  • limit counts distinct companies, not provider rows.
  • Twenty matching job listings at one employer still produce one result.

What the network cannot know

Some requirements cannot be answered from public or licensed data, whichever provider you ask. Avina tells you so instead of guessing.

Compared with going direct

Going straight to one provider is a reasonable choice when its data already answers your question. The Data API is the better fit when a request needs more than one kind of data, or when you do not want to build and maintain the integrations. The trade-off is the 5% platform fee. For a request that one provider can fully answer, calling that provider directly at the same rate costs slightly less. See Pricing.

Next steps

Pricing

How provider cost becomes credits.

How it works

The full search pipeline.