How to call the Data Galactica company API: verification endpoint guide (2026)

Verify a company by name in one HTTP call, read the verdict and keep a permanent Galactica ID


Written by the Data Galactica team. This is a how-to for our own API, checked against the live service on 20 November 2026. Records can be wrong, and every page lists its sources, so cite what you use.

Data Galactica gives every organisation and person a permanent Galactica ID, built from public registers and first-party sources. It covers 28M+ organisations and 98M+ people, and is strongest on India and the UK. This guide shows how to verify a company by name with one HTTP call, read the answer, and decide what to call next.

Try it with no key

You can make 25 free data calls a day per address without an API key, without contact details. The x-trial-remaining response header counts down.

curl -s "https://datagalactica.com/api/v1/verify/company?name=Infosys&country=IN"

A real response (trimmed) looks like this:

{
  "ok": true,
  "data": {
    "verdict": "match",
    "confidence": 0.9,
    "grade": "gold",
    "cite": {
      "id": "DGC-8SFS42RSWAX9",
      "name": "Infosys Limited",
      "url": "https://datagalactica.com/company/DGC-8SFS42RSWAX9/infosys-limited"
    },
    "conflicts": ["listed under INFY on two US exchanges; one of them is probably wrong"],
    "next": ["company.diligence", "company.people", "company.contact"]
  }
}

How to read the answer

Field What it means What to do
verdict match or possible_match On possible_match, show the candidates to a person and stop
confidence 0 to 1 Treat it as a hint, not proof of identity
grade Contact grade: verified, gold, silver or bronze It is about contact details, not identity
cite.id The Galactica ID (DGC- for organisations, DGP- for people) Store it; it never changes
conflicts Disagreements between sources Show them to the user
next Suggested follow-up calls Usually /company/{id}/diligence

Names collide. A lead-list "Infosys" in another city is not Infosys Limited, whatever its grade. Check place, identifiers and sources before you treat two records as the same.

Look up by identifier instead of name

If you already hold an identifier, skip the name match. Source IDs resolve to the Galactica ID in page URLs and in the API: Indian CIN and LLPIN, LEI, UK company number (as GB- plus the 8-character number, for example GB-00445790), SEC CIK and Wikidata Q-id. For a website, use /company/by-domain?domain=acme.com.

Going past the trial

For more calls, sign up at datagalactica.com/signup. New accounts get Rs 50 of free credit (125 calls), then it is Rs 0.40 per answered call from a prepaid wallet. Errors, empty pages and not-found answers are free. Send the key as Authorization: Bearer <key> to https://api.datagalactica.com/api/v1.

The same tools are on an MCP server for AI assistants at https://datagalactica.com/mcp (a keyless trial server is at https://datagalactica.com/mcp/free). In Claude Code:

claude mcp add --transport http datagalactica https://datagalactica.com/mcp

The MCP tool for this guide is verify_company; company_diligence is the usual next step.

A simple KYB flow

  1. GET /verify/company?name=...&country=... (or &website=...).
  2. If verdict is possible_match, ask a person to pick. Stop there.
  3. If match, call /company/{id}/diligence and keep the Galactica ID and page URL with your record.
  4. Show any conflicts instead of hiding them.

FAQ

Is there a free tier? Yes: 25 keyless calls a day per address, and Rs 50 of credit on sign-up.

Which countries work best? India and the UK have the deepest coverage.

Can I cite the result? Yes. Cite the Galactica ID and the page URL in cite.url.

References