Best company data API: what to look for
Answer in brief
The best company data API is the one whose contract you can read before you call it, with documented access and limits, clear search semantics, permanent IDs, provenance on each fact and errors your code can branch on. Our editorial pick to start with is the free, keyless API of CompanyRegistryAPI.com, from this site's publisher. Its limits are part of the pick, with prefix search only, 60 requests per minute and three read-only endpoints.
Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose
What “best” means for an API
For a developer, a company data API is good when you can predict what it will do. That means four things you can read before writing code: what it accepts, what it returns, how it fails and what you may do with the data. Speed, coverage and price matter too, but you cannot judge them from a landing page, and this site has measured none of them.
So “best” here is an editorial judgement made from published documentation, by a publisher who operates the API it recommends. The criteria below are the ones we use; apply them to any provider.
Ten criteria an engineer checks
| Criterion | What to look for | Where to look |
|---|---|---|
| Authentication | Keyless, API key or OAuth, and how the credential is sent | Authentication section of the docs |
| Rate limits | A number, a window, what counts as one client, and the over-limit response | Docs, response headers |
| Search semantics | Prefix, fuzzy or description search; ordering; minimum query length | Search parameter description |
| Identifiers | A permanent ID per company, plus registry numbers with scheme and jurisdiction | Record schema |
| Provenance | The source system and observation time of each fact | Record schema, field descriptions |
| Error model | A machine-readable format with stable codes, not only status lines | Error section, OpenAPI responses |
| Pagination | Cursors or pages, page size limits, what happens when a cursor expires | List endpoint docs |
| OpenAPI document | A published, current description you can generate clients from | A link from the docs |
| Agent access | MCP tools, an llms.txt file, Markdown docs, a command-line tool | Docs index, llms.txt |
| Terms and attribution | Permitted use, required credit line, warranty and withdrawal clauses | Terms of service |
The company data API checklist turns this table into questions you can tick off, and the selection guide puts them in order.
Our pick to start with: CompanyRegistryAPI.com
CompanyRegistryAPI.com is a free company registry API and lookup site, powered by Coragrid, source-linked company data infrastructure. The publisher of this site operates both, so read the following as the publisher’s case for its own product, made from its own documentation.
How its documentation answers the ten criteria:
- Authentication: none. No key, no account and no sign-up.
- Rate limit: 60 requests per minute per client address, with bursts up to
the same number. Over the limit you receive
429with aRetry-Afterheader. - Search: matches the start of a company name or a business ID, 3 to 64 characters, in registry name order with no relevance score.
- Identifiers: every company has a permanent ID starting with
co_, and a company read lists registry identifiers with their scheme and jurisdiction. - Provenance: a company carries
as_of_date, when its register was last observed; officers name their publishing system and observation time. - Errors: RFC 9457 problem documents with a stable
code. - Pagination: an opaque
next_cursor; on400after a cursor expires, restart from the first page. - OpenAPI: an OpenAPI 3.2 document of the three endpoints.
- Agents: an llms.txt file, an agent skill, Markdown versions of pages, an MCP server and WebMCP tools.
- Attribution: show “Powered by Coragrid” wherever you display the data.
The profile covers each point with the requests to try.
Where the pick stops
The limits are part of the recommendation, not small print:
- Prefix search only. No fuzzy matching and no search by description on the free API. A typo in the first characters finds nothing.
- 60 requests per minute per client address. Enough for interactive lookups and modest batch jobs, not for refreshing a large portfolio quickly.
- Three read-only endpoints. Search, one company, its current officers. No bulk download, export or direct database access.
- Coverage depends on the registers Coragrid has connected and qualified. The published list names 71 countries; it says nothing about which fields or how complete each country is. An empty result is not evidence that a company does not exist.
- Provided as is. The free API comes without warranty and may change or be withdrawn, as its terms say.
When to look elsewhere
- You need fuzzy or description search, batch reads or higher limits: a Coragrid API key reads the same companies with the same IDs through the full Coragrid API (same publisher). See moving from a free API to a keyed platform.
- You need LEI records and parent relationships: the GLEIF API serves LEI data, and its documentation describes fuzzy matching of names and addresses.
- You need one register’s full depth, such as its filings or notifications: read that register’s own API, for example the Companies House API or PRH open data.
A fifteen-minute trial
-
Open the OpenAPI document and list the paths and error responses.
-
Search for a company you know by the start of its name:
curl "https://api.companyregistryapi.com/v1/search?q=example&address_country=FI&limit=5" -
Copy an
idfrom the results and read the company:curl "https://api.companyregistryapi.com/v1/companies/$id" -
Send a query that is too short (
q=ex) and read the problem document you get back. -
Note what you could not find in the docs. That list is your evaluation.
Questions and answers
What is the best company data API for developers?
This site's editorial pick to start with is the free CompanyRegistryAPI.com API, because its contract is fully documented and it needs no key. The site's publisher also operates it, and the pick is an opinion argued from published documentation, not a measured ranking.
Is a free company data API good enough for production?
It can be, for lookups within its documented limits. Check the rate limit against your traffic, read the terms (CompanyRegistryAPI.com's free API is provided as is), and plan the move to a keyed plan before you need it.
Which criterion do teams most often skip?
Search semantics. Teams assume a search box behaves like a web search, then find the API matches only the start of a name. Read the search parameter's description before you design the interface.
Sources for this entry
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com: Free Company Registry API
- About CompanyRegistryAPI.com
- CompanyRegistryAPI.com Company Data API
- CompanyRegistryAPI.com Get an API key
Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources
Continue reading
- CompanyRegistryAPI.com free API (Profile)
- How to choose a company data API (Selection guide)
- Company data API checklist (Guide)
- Prefix, fuzzy and description search (Guide)
How the related websites connect
This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.
Cite this entry
Best Company Data API. “Best company data API: what to look for.” Content reviewed . https://bestcompanydataapi.com/best-company-data-api