Choosing

Questions to put to any company data provider

Guide · reviewed

Answer in brief

Ask a company data provider, in writing, where each fact comes from and when it was observed, what exactly its coverage figures count, how changes reach you, what happens to an identifier on a merger, what you may do with the data, and how you can test it on your own sample. Clear written answers matter more than a long feature list.

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

How to use these questions

Send the questions that your scorecard left unknown, not all of them. Ask for links to documentation rather than a new explanation, and ask the same questions of every shortlisted provider so the answers can be laid side by side.

Provenance

  1. For each field we need, which system published it: the register, a filing, your own research, a model?
  2. Does each fact or record carry its source and the time it was observed? Show a sample response.
  3. Do you change or correct values you receive from a register? If so, how do we see the original?
  4. Where two sources disagree, what do you return?

Listen for: field names in a sample, not adjectives such as “verified”.

Coverage

  1. What exactly does your headline figure count: legal entities, records, branches, registers, countries?
  2. For each country we need, which registers and which entity types are included? Are inactive and dissolved companies included?
  3. Which fields are present for which share of companies in those countries?
  4. What is not covered that customers often assume is?

Listen for: a country-by-country answer. See how to read a coverage claim.

Freshness

  1. Is there an as-of or last-observed date on each record?
  2. How do changes reach us: a change feed, delta files, or only by reading again?
  3. Is a refresh frequency promised, and where is it written?

Identity

  1. What identifier should we store? Is it permanent?
  2. What happens to it when a company is renamed, merges or splits?
  3. Are registry numbers, LEIs and VAT numbers kept as separate identifiers with their own status and dates?
  4. How do you resolve duplicates, and can we see when two records were merged?

The permanent identity guide explains what good answers look like.

Gaps

  1. How do you tell an unknown value from a value the register does not publish, or one that is restricted?
  2. Do you ever estimate or infer a value? Is it marked?

Licensing

  1. May we store the data, and for how long?
  2. May we show it to our own customers, and with what attribution?
  3. May we use it to train or ground a model?
  4. What happens to stored data if we stop paying?

Access

  1. Can we test on our own sample of companies before signing? Is there a free tier?
  2. What are the rate limits and quotas, and what happens when we exceed them?
  3. Is there a bulk option, and how is it priced compared with the API?

What good answers look like

Good answers point to documentation that already exists. As an example of the level of detail to expect, the API docs of CompanyRegistryAPI.com, the editorial pick of this reference and operated by its publisher, state the lifecycle states a record can have (active, redirected, split, tombstoned, restricted), that an ended registry number is a former number, and that a field a register does not publish is absent, never estimated. They also state the product’s limits plainly, including that there is no bulk download or export.

A provider that cannot answer questions 2, 5 or 13 in writing is asking you to trust its data without a way to check it. Weigh that against the criteria in the category guide before price.

Questions and answers

Why should a company data provider answer in writing?

A written answer can be checked, quoted in your decision record and held against the provider later. A spoken assurance cannot.

Which provider question reveals the most?

Asking for a sample response for a company that merged. It tests identity, lifecycle handling and provenance at once, and the answer is either in the documentation or it is not.

Sources for this entry

  1. CompanyRegistryAPI.com API docs Coragrid. The free API’s base URL, endpoints, rate limit, record fields, identifier schemes, lifecycle states, problem codes and attribution rule. Retrieved 17 November 2026.
  2. CompanyRegistryAPI.com Company Data API Coragrid. How the product describes company identifiers, where its data comes from, how current it is and how the data may be used. Retrieved 17 November 2026.

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

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. “Questions to put to any company data provider.” Content reviewed . https://bestcompanydata.com/questions-for-company-data-providers