Data APIFor product teams
Add B2B search to your product without becoming a data company.
Your users describe the companies or people they want. Avina interprets the request, finds and verifies the matches, and returns records your product can show, with the reason each one matched.
The pieces of a search feature.
Understand the request, run it, and show your users why each result is there.
Turn a sentence into filters
Parse returns the structured filters and criteria behind a sentence, so your product can show them, let users edit them and reuse them. It is free.
POST /v1/companies/search/parse { "query": "Private dental practices in Texas hiring SDRs" } 200 OK { "filters": { "all": [ ... ] }, "criteria": [ ... ], "assumptions": [ ... ], "search_request": { ... } }Run the search behind your interface
Start the search from your server with a cap on what it can spend, then read results as they arrive.
POST /v1/companies/search { "query": "B2B software companies in the US with 50 to 500 employees that are hiring sales development representatives", "limit": 50, "max_credits": 50 }Show why each result matched
Every result carries its requirements, a verdict for each and the sources, ready to show next to the record. Example values are illustrative.
{ "name": "Lakeview Dental Group", "domain": "lakeviewdental.example", "matched_criteria": [{ "criterion": "open_jobs", "verdict": "matched", "evidence": { "summary": "1 open job matches.", "sources": ["https://lakeviewdental.example/careers/sdr"] } }] }
Why product teams build on it.
- One integration to maintain
- You do not choose data providers, sign with them or reconcile their records. New sources arrive behind the same request.
- Results your users can trust
- A record is returned only when every requirement is matched with evidence. Your product can show that evidence instead of asking users to take a match on faith.
- A known cost per search
- Each search has its own cap and reports what it was charged, so you can price the feature. Reading results as often as you like is free.
How a request is answered.
Every search goes through the same four stages. You do not choose providers, and you can see what each stage did.
Interpret
The request is turned into exact requirements: filters on known fields, and free-text criteria for anything no field covers. Nothing you asked for is dropped.
Route
Avina picks the sources from what the request contains: data providers for structured conditions, AI search of the public web for requirements that need research.
Verify
Each candidate is checked against every requirement. It passes only when every requirement is matched with evidence.
Return
Passing records are merged into one per company or person and added to the results, which you can read while the search is still running.
The APIs behind it.
One key covers all of them. Each links to its page in the docs. See all seven.
- ParseAvailableTurn plain language into structured filters you can show, edit and reuse. Free.
POST /v1/companies/search/parse - CompaniesAvailableFind companies by anything you can describe: filters, requirements no database covers, and events like a new hire or a funding round.
POST /v1/companies/search - PeopleAvailableFind people by job title, seniority and employer, with verified work emails on request.
POST /v1/people/search - AskComing soonAsk a question about a company or market and get an answer with citations.
Who else builds on the Data API.
Common questions
Can I show users how their request was understood?
Yes. Parse returns the filters, the criteria and any assumptions before a search runs, and a search reports its interpretation and assumptions too.
Can my users see which provider a record came from?
No. Provider names are not part of the response. Results are normalized into one schema, and each requirement cites the sources of its evidence.
How do I control the cost of each user action?
Set max_credits on every search your product starts. The search stops new spending at that limit and keeps the results found so far.
How do I get access?
The Data API is in beta. Request access with the form in the docs. Once you are in, a workspace admin creates an API key in the Avina dashboard and adds credits, and the quickstart takes you to your first results.
Ship search your users can check.
Request beta access and build your first search in minutes.
The Data API is in beta. Access is by request.