Products & Services · API
One REST call: jurisdiction and identifier in, structured company data out. 161 official registry integrations sit behind a single endpoint and a single schema, queried live at request time.
The suite
No per-country integration work, no portal-hopping, no vendor patchwork behind the scenes.
A single REST call takes a jurisdiction and an identifier and returns structured company data. 161 official registry integrations sit behind one endpoint and one schema.
Each call queries the official government registry at request time, not a cached mirror. Every record carries its source name, source URL and retrieval timestamp.
Resolve a legal name and country into the correct registry identifier across 148 jurisdictions, then feed it straight into a search. No need to know the local ID format first.
Officers, shareholders, ownership, addresses, capital and accounts arrive de-duplicated and normalised, whether the source is Brazil, Japan or Luxembourg.
Retrieve the registry PDFs themselves, with OCR and AI extraction lifting shareholder tables and subsidiary holdings out of filings registries never expose as fields.
API key or OAuth2, an async job model so long retrievals never block a workflow, follow-on calls that expand ownership layer by layer, and credit metering that refunds on failure.
The data model
Every source is de-duplicated and normalised into the same objects, so integration code is written once and never per country.
Names, roles and legal forms arrive readable, with the original preserved alongside.
Documents
Registries publish documents, not fields. The API returns the document itself and then reads it, so data that was never exposed as a field still reaches your system as structured output.
The filing as the registry issued it, retrievable through the same call that returns the structured record.
Older and image-only documents are read, so coverage does not stop at the registries that publish clean text.
Shareholder tables and subsidiary holdings are lifted out of annual accounts and returned as fields, not as a document to read by hand.
Integration
A CLM, an onboarding flow, a data lake. The mechanics assume the API is a component of your system, not a destination for your analysts.
Whichever fits your estate. Keys for service-to-service work, OAuth2 where user identity has to travel with the call.
Long registry retrievals return a job immediately and complete in the background, so no workflow waits on a slow foreign register.
Follow-on calls walk an ownership tree one level at a time, so you fetch only the depth a case actually needs.
Credits are counted per search and returned automatically when a retrieval fails, so a bad source costs you nothing.
Contact our team for API access, documentation and a sandbox key.