Answer in brief

Move from a free company data API to a keyed platform when your traffic, search needs or batch jobs outgrow the free tier, not before. Plan for changes in authentication, request shapes and limits, and keep stored IDs valid by choosing a free API that shares IDs and field names with its paid platform. CompanyRegistryAPI.com and the Coragrid API share both.

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

Signals that the free tier is too small

  • 429 responses at your peak even with caching and backoff.
  • Users need search by description or tolerant matching.
  • Batch refreshes no longer fit in a night at the documented limit.
  • The product needs terms beyond “provided as is”.

None of these says the data is wrong; they say the access model no longer fits. Moving within one provider usually keeps the data model.

What changes, and what stays

The CompanyRegistryAPI.com key page sets out the difference between its free API and the full Coragrid API:

Free CompanyRegistryAPI.com API Coragrid API with a key
Credential None API key, sent as a bearer token
Search Start of a name or a business ID Search by description with structured filters
Search request GET /v1/search?q=... A QUERY request with a JSON body, per the Coragrid OpenAPI document
Limits 60 requests per minute per client address Set per key, shown by cgd auth status
Extra calls Resolve names and domains to IDs; batch reads
Command line cgd
Company IDs and field names Permanent co_ IDs The same

The same publisher operates both. Read this table as that publisher’s account of its own offer, from its key page.

Switch in one module

If your calls go through one client module, the switch is a change of transport inside it:

const FREE = "https://api.companyregistryapi.com";
const CORAGRID = "https://api.coragrid.com";

export async function getCompany(id) {
  const key = process.env.CORAGRID_API_KEY;
  const url = `${key ? CORAGRID : FREE}/v1/companies/${id}`;
  const headers = key ? { Authorization: `Bearer ${key}` } : {};
  const response = await fetch(url, { headers });
  if (!response.ok) throw new Error(`${response.status}`);
  return response.json();
}

The company read path is the same in the product’s examples for both APIs. Search is not: on the Coragrid API it is a QUERY request with a JSON body. Follow the Coragrid OpenAPI document for that request and for the response envelope when you port the calls.

Run both during the move

  1. Request a key and check its scopes with cgd auth status; lookups need companies:read, and search by description also needs search:semantic.
  2. Point a share of reads at the Coragrid API and compare responses for the same IDs.
  3. Port the search call to the new request shape.
  4. Move the rest, and keep the free API as a fallback for reads while the terms allow it.

Keep the key safe

Inject CORAGRID_API_KEY into the process environment from a secret store at run time. Never commit it, write it to a shell profile, or paste it into a conversation with an agent. The access models guide has the details.

Other providers

The same questions apply anywhere: does the paid tier keep the IDs you stored, the field names you parse, and the error format you branch on? If not, budget for a data migration, and run the checklist again on the paid tier.

Questions and answers

What signals that it is time to move?

Sustained 429 responses at peak, users who need fuzzy or description search, batch refreshes that no longer fit in the rate limit, or a need for terms and support that a free, as-is service does not offer.

Do I need to migrate stored company IDs?

Not when moving from the free CompanyRegistryAPI.com API to the Coragrid API. The product's pages say companies keep their permanent IDs and field names, so what you stored stays valid.

How do I get a Coragrid API key?

Coragrid issues keys and their scopes on request at coragrid.com/request-access. CompanyRegistryAPI.com has no sign-up form and never asks for a key.

Sources for this entry

  1. CompanyRegistryAPI.com Get an API key Coragrid. What a Coragrid API key adds over the free API, how keys are issued and stored, and the first calls with a key. Retrieved 17 November 2026.
  2. CompanyRegistryAPI.com API docs Coragrid. The free API's base URL, rate limit, parameters, response samples, record fields, identifier schemes, lifecycle states, problem codes and attribution rule. Retrieved 17 November 2026.
  3. About CompanyRegistryAPI.com Coragrid. Where the product's records come from, what it does not do with them, and the free API terms, including "provided as is". Retrieved 17 November 2026.
  4. CompanyRegistryAPI.com: Free Company Registry API Coragrid. What the product is, its key features, the country-level coverage list and the first calls in cURL, JavaScript and Python. 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 API. “Moving from a free API to a keyed platform.” Content reviewed . https://bestcompanydataapi.com/from-free-api-to-keyed-platform