License registry-sourced company data and verified business contact data across 600M+ companies — and pass it on to the people who use your product.
The difference between them is who the data reaches and what they may do with it, not what data you get — all four license the same two data sets, set out below. Pick the one that matches what you are building; if you straddle two, we write one agreement that covers both.
Build our data into your product. Our fields blended into your own records and shipped under your brand, on a product-embedding licence.
Deliver our records to your customers. Handed to them intact, on a redistribution licence with territory and named channels agreed.
Ground your agents in filed records. Your agents answer from our data at query time, on a retrieval grant. Training rights are agreed separately in writing.
Introduce the clients who need it. You introduce clients who need the data but will not license it themselves. Fee terms agreed in writing before the first introduction.
This is where most data partnerships die. Incumbent agreements are drafted to keep the data inside your four walls, which is exactly the opposite of what a partner needs. Ours are drafted the other way round.
Inside your product, through your own interface.
Onward to your own clients, as part of what you sell.
Under your brand rather than ours.
Through channel partners named in the agreement.
Model training and grounding, licensed like everything else.
Legal teams rarely arrive with a general concern. They arrive with one specific paragraph from a previous vendor contract that ended the project: a redistribution ban, a derivative works restriction, a territory cap, a per-record charge that made the unit economics impossible. Send us that paragraph and we will tell you whether we can write around it.
Whichever model you pick above, these are the blocks you license. First-party, sourced directly from official government registries across 600M+ companies in 200+ countries — eight blocks, together or separately.
Collected directly from 400+ official government registries and gazettes across 200+ countries — no intermediary data vendor in between.
The second data set, licensed under the same agreement. Business contacts only, resolvable by person, company domain or LinkedIn profile and tied back to the company record — sourced separately from the registry data and labelled as such in the API.
Person name · Job title · Location · LinkedIn profile
Work email · Phone number
Professional headline · Work experience · Education · Skills
We connect to 15 contact data partners rather than relying on one. Every lookup is routed through them in sequence, which is what lifts the match rate — no single vendor covers every market — and each field is taken from the first partner that verifies it, so quality holds at volume. The run stops the moment the record is complete, so nothing is queried twice and the cost stays down.
Starting the run
Seven ways to take the same data. Pick one or combine them — a live API for the paths inside your product, a bulk feed for your warehouse, or a prebuilt connector for the tools your users already open. Fields are mapped to your names, types and identifiers before the first delivery.
Live lookups inside your product — verification, officers, shareholders, financials, group structure.
Regis is our AI, trained only on official registry filings. Your users ask a question in plain language; Regis finds the right records and returns a sourced answer — so nobody has to know which endpoint or field to call.
Resolve a person by name, company domain or LinkedIn profile; returns a verified work email and business phone.
Full corpus or a scoped subset into storage you own, then only the changed records on the same schema and keys.
The licensed corpus exposed as tools to Claude and any other MCP client, on the same key and provenance fields as the API.
Enrich, verify and refresh company records inside the CRM your customers already work in.
Teams who try this in-house usually get three registries working, then discover that the fourth changes its export format without notice and the fifth charges per document. Here is what sits behind the licence instead.
The same records reach end users through compliance, screening, risk and enrichment platforms as well as through our own application.
When you're resolving entities and mapping risk across borders, the foundation has to be authoritative and traceable. Global Database gives us that across the markets we're expanding into, and their team absorbs the registry-level differences and constant changes, so ours stays focused on the intelligence layer rather than the data plumbing.
Read the case studyTell us what you are building. A named person on the partnerships team replies within two business days, in writing.