Business Entity Search API: Look Up Companies by Name
Search business entities by name through one API: free name resolution, SEC EDGAR and UK registry lookups, and where US state registries fit in.

Look up a list of company names and match each one to a real company record, in one prompt. Paste this into your agent:
Set up https://monid.ai/SKILL.md, and then use Monid to resolve these company names to a company record, keep the closest match for each, and give me a table with the name I gave, the matched name, website, category and status: Stripe, Perplexity AI, Snowflake.
One prompt matches a whole list. 1 min setup · 8-20 hrs saved.
You have a company name, or a few hundred, and you want to know what each one is: which company it points to, whether it is public or private, and where to go for the legal record. Searching state websites one name at a time does not scale, and no single US database covers every state. This guide shows what exists through an API, what came back when we ran it on 2026-10-16, and the traps in matching names to entities. It runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call.
What is the easiest way to run a business entity search through an API?
Monid. Install it once, add a key, and your agent resolves company names, searches company registries and reads SEC and UK registry records with calls billed one at a time, with no vendor contract and no account for each data source.
- Pay per call. Each call is billed on its own. The name-resolution endpoints cost nothing per call, and the registry lookups are $0.0594 a call (Verified 2026-10-16 on the company enrichment tools page). Buy calls as you need them: no monthly plan and no minimum top-up. Discovery and inspection are free; only a run bills.
- One install, every data source. The same key and the same balance call a name resolver, a company search by country, an SEC EDGAR lookup and a Companies House lookup. When you want firmographics for the same company next, it is another call on the same balance, and dataset versus API covers when a bought database is the better fit.
- Lives inside your agent. Install the CLI, add your key, run the prompt above, and the tools are there whenever your agent needs them, on demand, with nothing to keep running. Your agent reads
SKILL.mdand learns the rest, so setup is about a minute.
There is no single endpoint that searches all fifty US state registries. What you get instead is a short chain: resolve the name for free, then spend a paid call only on the companies that matter.
How do you look up a list of company names at once?
Resolve every name with the free search first, then run the paid lookups on the survivors. The free step is /v1/company/search from the provider akta. It takes one query, a company name or a website, and returns candidate companies.
| Route | What you get | Cost shape | Fits |
|---|---|---|---|
| Search each state website by hand | The state's own record for one entity | Your time | A handful of lookups in one state |
| Buy a company database | Pre-built records for millions of companies | Contract | Segment-wide lists, one export |
| Scrape the state sites | Whatever your parser reads | Your hours | A fixed state you will maintain |
| Monid name search and registry endpoints | Candidate companies per name, plus SEC and UK registry records | Pay per call, free for name search | Lists of names, agents, enrichment flows |
Monid fits a list because the work is the same call repeated, and you pay for the lookups you run and nothing between runs.
For agents
Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:
set up https://monid.ai/SKILL.md
It learns the whole discover, inspect, run workflow itself. More in the agent quickstart.
For humans
npm install -g @monid-ai/cli
monid keys add -k <your-api-key> -l main
Resolve one name
monid run -p akta -e /v1/company/search --query '{"query":"Perplexity AI"}' -w
Page through a country-filtered search
The second free endpoint, /v2/company/list from tendata, searches a company registry by name keyword, filters by ISO3 country code and pages up to 20 rows at a time:
monid run -p tendata -e /v2/company/list \
--query '{"name":"Stripe","pageNo":1,"pageSize":5,"countryCodes":"USA"}' -w
Look up an SEC filer
The paid lookup for US public companies reads SEC EDGAR and takes company, company_name, ticker or cik:
monid run -p api.strale.io -e /x402/us-company-data \
--query '{"company":"Snowflake"}' -w
Loop it over your list
Put one company name per line in names.txt, then run:
mkdir -p out
while read -r name; do
monid run -p akta -e /v1/company/search \
--query "{\"query\":\"$name\"}" -w > "out/$(echo "$name" | tr ' ' '_').json"
done < names.txt
Each name writes one file of candidates. The finding a company's website from its name guide covers the same name-to-company step when the website is what you want.
Or hand the whole job to an agent
Give this to your agent![]()
Set up https://monid.ai/SKILL.md, and then use Monid to resolve every company name on this list, keep the closest match for each, flag the ones with more than one plausible match, and give me one table with the name, the matched company, website, category and status.Can you search state business registries yourself with Python?
Yes, and for one state and a few names it is an afternoon. Every state runs its own search page, so you build one fetcher per state, parse the result list, and match what comes back to the name you hold.
The cost is the count. There are fifty states with fifty different search pages and no shared schema or identifier, so a list of names that spans states needs fifty small scrapers, each with its own markup, its own limits and its own repair day. A page with a session token or a form that changes breaks quietly. If your question is "does this company legally exist, with this exact name, in this state", the state's own search page is the answer and it is free.
The Monid route is the choice when the question is the one most lists actually ask: which company is this name, and is it worth a deeper look. The candidate search is maintained for you, the output is typed JSON instead of HTML you parse, and the name search is free per call. The registry lookups are priced per call ($0.0594 each, Verified 2026-10-16), so a hundred SEC lookups cost $5.94. Searching a company by name shows the same name-to-record lookup done from code.
What does a business entity record look like, and what can you build?
The name search returns a short candidate row, and the registry lookups return the legal record. We ran the two free searches on 2026-10-16, so the fields below are what came back.
The candidate row
Searching Stripe on the akta endpoint returned 25 rows. The top rows, trimmed:
{ "uuid": "0000031",
"name": "Stripe",
"website": "https://stripe.com",
"product_category": "Online Payment Processing",
"company_status": "private",
"akta_rank": 41 }
Every row has a uuid, name, website, product_category, company_status and akta_rank. Some rows add a parent_company object: Stripe Capital and Stripe Atlas both carried { "name": "Stripe", "uuid": "0000031" }, which tells you they belong to the company in the first row. The uuid is the handle the enrichment endpoints take next, and the endpoint's own description says to prefer the candidate whose website matches the company you mean.
The registry search row
The tendata list returns a thinner row, name, id and country, plus a total and paging:
{ "page": 1, "size": 5, "total": 375,
"content": [ { "name": "STRIPE, INC.", "id": "USAI0950091d062716370ee66846f016d0f3", "country": "USA" } ] }
The search for Stripe filtered to USA found 375 companies, so at 20 rows a page, reading every one is 19 calls. The id is what you pass to the profile endpoint to pin down the exact company.
The registry records
The paid endpoints return the legal record for companies the source holds. Their listings describe the fields: the US endpoint reads SEC EDGAR and returns the company name, CIK, SIC code, state and a filings summary; the UK endpoint reads Companies House and returns name, status, incorporation date, SIC codes and registered address; the Swedish one reads Bolagsverket and returns name, legal form, status, address and registration date. The tendata profile endpoint lists registration numbers, operating status, incorporation date, industry and addresses. We inspected these and did not run them, because each call is priced above our test limit or billed per matched profile.
What you can build with it
- A cleaned account list. Resolve every name, keep the row whose website matches, and drop the near-misses before you spend anything on enrichment.
- A first-pass vendor check. Before onboarding a supplier, resolve its name and look at the category and parent company, then send the legal check to the right registry.
- A public-company screen. Run the ticker or the name through the SEC lookup to get the CIK and state, which is what filings searches take.
- A liveness signal. A company with a website, a category and hiring activity is operating, which a hiring feed can confirm.
What goes wrong when you match company names in bulk?
Four things hide until you run more than a handful of names. All four come from the 2026-10-16 runs.
Why does one name return many companies?
Because the search is fuzzy, and it says so. Searching Perplexity AI returned four rows: the real company, a venture fund with a similar name, a roofing company and an SEO software company. Searching Stripe returned 25: the payments company first, then a growth equity firm called Stripes, a convenience store chain, a pavement marking business and an education company called Stride.
Never take row one unread. It was right both times, and that is luck you cannot budget on. Score each candidate on website and product_category before you spend a paid call on it.
Why does the number of rows change between names?
Because the endpoint returns what matches, not a fixed page. Four rows for one name and 25 for another means a loop should read the row count from each response instead of assuming a page size. A step that takes "the first ten" will discard real candidates on one name and pad the list with noise on another.
Is company_status the status of the legal entity?
No. The values we saw were private, public and, on one row, an empty string. That is a market classification of the company, not the registry status of a legal entity, which is a different question with answers such as active or dissolved. Reading private as "in good standing" is the mistake to avoid. Treat an empty value as missing.
Why do two sources return a different "Stripe"?
Because they index different things. The akta search returned the brand and its products, with stripe.com as the website. The tendata search filtered to the USA returned registry-style entries, with STRIPE, INC. first, then STRIPE FOR STRIPE LLC and PRIME STRIPE, 375 in total. The first answers "which brand is this", the second "which registered companies carry this word". Match on the field you need, carry the source along with the id, and never mix uuid and id values from the two.
Which endpoint should I use for which job?
| Endpoint | What it does | Input | Billing | Price (Verified 2026-10-16) |
|---|---|---|---|---|
akta/v1/company/search | Resolve a name or website to candidate companies | query | Per call | Free |
tendata/v2/company/list | Search the registry by name, filter by country | name, pageNo, pageSize, countryCodes | Per call | Free |
api.strale.io/x402/us-company-data | SEC EDGAR record for a US filer | company, ticker or cik | Per call | $0.0594 |
api.strale.io/x402/uk-company-data | Companies House record | company_number | Per call | $0.0594 |
api.strale.io/x402/swedish-company-data | Bolagsverket record | org_number | Per call | $0.0594 |
api.strale.io/x402/company-id-detect | Identify the type and country of a registration number | id | Per call | $0.0594 |
tendata/v2/company | Company profile for a matched company | name, companyId | Per matched profile, a miss is free | $0.08 |
Prices Verified 2026-10-16 with monid inspect. The first two rows are the ones to loop over a list. The /x402/company-id-detect endpoint is useful for mixed international input: it identifies what a registration number is before you decide which registry can read it. The profile endpoint bills per matched profile, so a batch can cost more than the listed price; run one name before you commit a list.
For the same companies in other data sources, the company enrichment tools sit on the same key and balance.
When is another route a better fit?
You need certified registry data. A Secretary of State or Companies House issues the certificate of good standing. A resold or resolved record is not one, and no endpoint changes that.
You work in one state and a few names. The state's own search page is free and authoritative. An API earns its place when the list is long or an agent runs the lookup.
You need officers, registered agents or filing history by state. The endpoints above list none of them. Those live with each state registry.
You want every company in a segment. Name search answers questions about names you already hold. A purchased database answers segment-wide questions in one export.
And the disclosure: we resell these endpoints. The most useful thing in this post is that you should resolve names first and judge each candidate on website and category, which costs nothing and is the right habit whoever you buy the data from.
Conclusion
The quickest way to run a business entity search through an API is to resolve each name with the free candidate search through Monid, then pay $0.0594 a call (Verified 2026-10-16) only for the registry records you need. One key covers the name search, the SEC and UK lookups and every other tool, setup is about a minute, and it is ready inside your agent whenever you need it. Searching fifty state sites yourself works for one state; the maintained route is for lists.
Two things matter more than the endpoint you pick. A fuzzy search returns candidates, not answers: Stripe returned 25 rows and Perplexity AI four, so judge each on website and category. And company_status is a market label, private or public, not the legal standing of an entity, so send any compliance question to the registry that issues the record.
How we estimated the time saved: building a name-matching step with candidate scoring is roughly 3 to 6 hours, and wiring two registry sources with their own inputs, errors and parsing is roughly 3 to 7 hours each. That is 8 to 20 hours. The 1 minute is the install, key and first call once you already have a Monid key.
Free next step: run monid inspect -p akta -e /v1/company/search, then make one call on a name you know and read the website and product_category of every row. Start at monid.ai.
FAQ
Is there an API for business entity search?
There is no single API that searches every US state registry, because each state runs its own. Through Monid you can resolve names with a free candidate search, search a company registry by country, and read SEC EDGAR and UK Companies House records per call.
Is there a free business entity search?
Yes. Each state's own registry search is free, and through Monid the name-resolution endpoints cost nothing per call. Only the registry lookups are billed, at $0.0594 a call (Verified 2026-10-16), with no monthly plan and no minimum.
How do I check a business entity name?
Search the name, then read the website and category of every candidate before you accept one. Run /v1/company/search with the name as query, and use the parent_company field to see when a row belongs to a bigger company.
How do I look up what type of entity a company is?
The legal entity type is held by the registry that issued it, so the state or national registry is the source. For a registration number you do not recognise, /x402/company-id-detect identifies the type and country of the number.
Can I look up a Texas LLC through these endpoints?
Not as a state filing. The US lookup here reads SEC EDGAR, and a state LLC filing sits with the Texas Secretary of State. The free name search will tell you whether the company has a public brand and website.
Published August 2026.


