A news article says "Acme AI, led by CEO Jane Doe, raised a seed round." A bank export lists a payment to acme.ai. A CRM has three rows that all say "Acme." Before you can research, enrich, or write anything, you need to know which company and which person these refer to.
aVenture Lookup finds them in one request. Send the clues you have, and it returns the matching company or person record, tells you the subject is not in aVenture yet, or hands you a short ranked list when the clues cannot tell namesakes apart. Lookup is new and marked experimental while we expand it.
One lookup for companies and people
Lookup takes a company or a person and works out which one it is. It is available through the aVenture API, the aventure CLI, and the aVenture MCP server, so an AI agent resolves a name the same way your code does.
What to send
Send the name as you found it spelled, a URL the subject owns, or both. A website, a LinkedIn company page, or a LinkedIn profile is enough on its own. Each extra clue narrows the answer:
- Location: a city, region, or country, which separates two companies with the same name.
- Context: specific facts in plain words, such as "CEO at Acme" or "online payments company."
- Article: the news article where you found the name.
A lookup by website alone, and one with a name and a website:
GET /v1/lookup?url=https%3A%2F%2Facme.ai
GET /v1/lookup?name=Acme%20AI&url=https%3A%2F%2Facme.ai
Domains, profile URLs, and registry ids match exactly
Some clues identify a subject on their own. A website domain belongs to one company. A public profile URL belongs to one person. A registry identifier such as a stock ticker, an LEI, or an EIN names one legal entity. When your request carries one of these, Lookup resolves it directly to the record that owns it. Lookup does not rank candidates for these inputs. The same input returns the same record each time.
That makes Lookup a good fit for transaction data. A bank or card activity export often records a counterparty's domain, and invoices and payment records often carry a registry id. Send each counterparty as its own lookup. Each line with a domain or registry id maps to its company record. Lines with only a brand name still get an answer, as the next section explains.
When the clues are ambiguous, Lookup says so
Names alone are rarely unique. There are many companies called Acme and many people called Jane Doe. When the clues do not settle the question, Lookup compares the records aVenture already holds and, when needed, searches the web. Each answer has one of three statuses:
- MATCHED: one record is the subject, and Lookup returns it.
- NO_MATCH: aVenture does not hold this subject yet. It is safe to create a record or request research without making a duplicate.
- NEEDS_REVIEW: more than one record could be the subject. You get the candidates ranked by likelihood, so you or your user can choose.
Lookup does not pick between namesakes on its own. A parent company, its subsidiary, and an unrelated company with a similar name are three different companies, and Lookup treats them that way. When it cannot tell them apart, it returns NEEDS_REVIEW.
Four uses
Turning a news article into records. A funding announcement names a startup and its founder. Send one lookup for the company and one for the founder, each with the article attached, and you get both records back, or NO_MATCH for one that is new.
Identifying counterparties in bank activity. Run each counterparty from a transactions export through Lookup. Domains and registry ids resolve exactly; brand-only lines come back matched, new, or flagged for review.
Letting an AI agent resolve before it writes. An agent that creates or updates records should first know whether the record exists. Through the MCP server, the agent runs the same lookup and acts on the status: update on MATCHED, create on NO_MATCH, ask on NEEDS_REVIEW.
Cleaning up a CRM. Look up each company in your CRM. Rows that resolve to the same aVenture record are the same company. Use that record as the key for merging duplicates.
Also available now
These additions ship alongside Lookup and are also experimental:
- Whole-article lookup. Submit a news article with
POST /v1/lookup-jobsand get back the companies and people it mentions. Subjects already in aVenture come back as their existing records. Subjects that are new come back as placeholder records. - Completeness score and update time on each result. Each record carries a completeness score (
dataCompletionCoverage) and a last-updated time (updatedAt), so you can choose which ones need research. - Research many records in one request. Send a batch of companies and people to
POST /v1/enrichmentsto research them together. - Research updates from profile pages. Request a research update from a company, investor, fund, product, or person page.
Research costs $2.50 per company and $0.65 per person. The price is the same whether the record is new or already in aVenture. AI Plus and AI Pro include a monthly research allowance.
Try it
Lookup is available now through the API, the aventure CLI, and the MCP server. The request and response formats are in the aVenture docs.
