The registry, as an endpoint.

We read 400+ government registers across 200+ countries and hand you the result over REST, MCP, webhooks or a warehouse feed. Fintechs, marketplaces, SaaS platforms and AI teams build on it.

0+registries
0+countries
0M+profiles
Dailysync
ownership chain · 3 registersSAMPLE
ACME LOGISTICS SAMPLE BVKVK · Netherlands · active
SAMPLE HOLDING GMBHHandelsregister · Germany
SAMPLE HOLDINGS SARLRCS · Luxembourg · ultimate owner
3 levels resolved · 0 unresolved branches61.4% effective
sources — read directly, no reseller in the middle
Companies HouseGB
KVKNL
HandelsregisterDE
SEC EDGARUS
RCSLU
INPIFR
Registro MercantilES
Registro ImpreseIT
Corporations CanadaCA
BolagsverketSE
BrønnøysundNO
CVRDK
ASICAU
FirmenbuchAT
ZefixCH
ACRASG
MCAIN
CIPCZA
Junta ComercialBR
NZBNNZ
Companies HouseGB
KVKNL
HandelsregisterDE
SEC EDGARUS
RCSLU
INPIFR
Registro MercantilES
Registro ImpreseIT
Corporations CanadaCA
BolagsverketSE
BrønnøysundNO
CVRDK
ASICAU
FirmenbuchAT
ZefixCH
ACRASG
MCAIN
CIPCZA
Junta ComercialBR
NZBNNZ
why us — sourcing and rights

Five things that decide whether you can build on it.

01/05
source

Read straight from the register

400+ government registers across 200+ countries, read at the source by pipelines we run ourselves.

source_url

Every field names its register, and links to it

Which authority each value came from, its filing reference, and the URL of the page it sits on.

timestamps

Two dates on everything

When the company filed it, and when we last read it.

document

The original filing comes with it

The document reference the value was taken from, carried on the record.

rights

Yours to sell, redistribute and train on

Reseller and derivative rights are available, priced separately from access.

resellredistributetrain
where it lands

Six teams. One dependency.

01 · growth and revops

Growth and RevOps

what they pull

Firmographics, filed accounts and group structure written onto the account object.

what it decides

Whether territory maths and routing rest on filed numbers or typed notes.

regis

Regis, over the API

A domain-specific model built for company verification. It plans and executes multi-step queries across government registers and returns structured data, with every value carrying the register it came from, the filing reference and the moment it was read.

Regis APIData provider + assistant
Commercial contractsOneTwo
Data processing agreementsOneTwo
Assistant seat licencesNoneRequired
Pricing basisPer resultPer token consumed
Bulk retrievalDirect, no inferenceVia the model context window
Data pathSingle supplierCrosses a third party
Where the citation landsOn the register's own reference, per fieldOn the provider's own dataset
Fields a register does not publishReturns null and names the silent registerNot guaranteed
Customer data in trainingExcluded, set out in the DPAGoverned by two sets of terms
fields

Every field on the record, sourced

147 documented fields per company, in six groups. Each one read from the register it was filed with, carrying its own register, reference and timestamp. Modelled values are labelled as modelled.

01

Company registry data

  • Legal name & previous names
  • Registration number, VAT & tax IDs
  • Legal form & incorporation date
  • Company status
  • Registered & trading addresses
  • Registry source & filing link
02

Financials

  • Filed revenue & turnover
  • Assets, liabilities & net assets
  • Profit & loss figures
  • Filing history & latest accounts
  • Currency & reporting period
  • Multi-year financial trend
03

Firmographics

  • Industry codes — SIC, NACE, NAICS
  • Employee counts & size bands
  • Company age & trading status
  • Websites & digital footprint
  • Phone numbers
  • Geographic & jurisdiction data
04

Directors & officers

  • Directors & active officers
  • Officer role & position
  • Appointment & resignation dates
  • Nationality & country of residence
  • Date of birth (where filed)
  • Occupation
05

Shareholders & ownership

  • Shareholders & shareholdings
  • Share classes & percentages
  • Beneficial owners (PSCs / UBOs)
  • Ownership percentages
  • Ultimate beneficial owner chain
06

Group structure

  • Immediate parent
  • Global ultimate owner
  • Subsidiaries & branches
  • Corporate linkage across registries
  • Cross-registry entity resolution
security and procurement

Everything your security review will ask for.

What the data actually is

Public-record company information published by government registers. Officer and beneficial-owner details are the ones the register itself publishes. No consumer personal data is collected or resold.

Data protection

UK GDPR and EU GDPR. A DPA and a current sub-processor list are available on request and form part of the security pack.

Certification

ISO 27001 certified in the United Kingdom. Certificate number, issuing body, scope and expiry are supplied with the security pack.

Hosting and residency

Data is hosted in the European Union. Sub-processor locations are listed in the pack. Other residency arrangements are handled contractually.

Retention and exit

Retention, deletion and post-termination handling of retrieved records are set in the MSA rather than left to policy. Data already delivered under a bulk licence stays under the terms it arrived on.

Contracting entities

Global Data Intelligence Limited, registered in England and Wales, company number 09410808, VAT GB260423730 — the contracting entity for UK and EU customers. Global Database North America Inc. contracts customers in the Americas.

How to access the data.

Seven routes into the same primary, government-sourced dataset — pick the one that fits your stack.

Platform

Search, screen and export company records from the web application.

API

Query any company by registry ID — documented endpoints, JSON responses, provenance on every value.

Bulk data feeds

Full datasets and scheduled deltas, delivered to your warehouse on your cadence.

CRM

HubSpot, Salesforce and Microsoft Dynamics. Registry fields on the record your team already works in, matched on registration number.

MCP

Connect the dataset to any MCP-compatible agent or tool, on the same key.

Assistant connectors

Pull registry data straight into your AI assistant, with the source attached to the answer.

Regis AI

Ask questions in natural language across the dataset and get sourced answers — in the platform, or over the API.

Start with a key, not a meeting.

Resolve one of your own records and read the source block. If it does what you need, the commercial conversation is a short one.

Before you book the call

Where does the data actually come from?

Primary government sources — company registers, tax authorities, filing bodies and official gazettes — read directly by our own pipelines across 400+ sources in 200+ countries. Every value carries the register it came from, the filing reference and the moment it was read — attached at field level, not as a footnote on the response. Where a register does not publish a field, the API returns null and names the register that is silent, rather than filling the gap.

How fresh is it?

Sources are synced daily and detected changes are pushed to your webhook endpoint. Freshness follows the underlying register: some jurisdictions publish continuously, others in batches. The payload always states when the record was filed and when we read it.

Can we redistribute the data inside our own product?

Yes, under a redistribution licence. Settle this before you build. It is where technology teams get caught by agreements written for internal analyst use — ask for the specific clause in writing.

Do we have to adopt a proprietary company identifier?

No. Records key on open identifiers — registration number, jurisdiction and VAT number. You can join our records to what you already hold without adopting a key that only works while you remain a customer.

How do we evaluate match quality before committing?

Batch-resolve a sample of your own records with a test key and read the match confidence distribution. Evaluating on your own messy inputs tells you more than any coverage statistic, including ours.

Can an agent call this directly?

Yes. The MCP server exposes search, details, ownership, financials, group structure and screening as tools, under the same authentication as the REST API. Regis answers from what it retrieved for that query rather than from training, so an agent that finds nothing reports nothing.

What about personal data and GDPR?

Officer and beneficial-owner information is published by the registers themselves under statutory transparency regimes, and we carry the source and legal basis with the record. Data protection documentation, including processing terms and the sub-processor list, is available on request during procurement.

Can we use it to train or ground a model?

Grounding and retrieval are covered under standard terms, and the source block gives model output something citable. Training licences are separate and priced separately.