Financials, UBOs and group structure your AI agents can cite.
Company data for AI agents, read from official government registries. Every value carries the register it came from, the filing reference and the time of the read, across 600M+ companies in 200+ countries.
Same question, same company: our own. The left answer reads well and cannot be checked. The right one declines the field the register does not publish.
An agent that cannot show its source is a liability with good grammar.
General-purpose models produce a turnover figure for any company you name. It is fluent, plausible and unattached to a filing. Put that in a case file and the first question an examiner asks is the one the agent cannot answer.
This is company data for AI agents built so the agent never has to. Every record an enterprise AI agent retrieves is read from a named government register and returned with the reference a reviewer needs to open the original. 400+ registries, 200+ countries and territories, 600M+ company records, synced daily.
Entity resolution
Turn a name, domain, VAT number or registration number into one registry record. Similarly named companies are the first place an agent goes wrong, so the resolved registration number is returned with the match.
KYB verification
Legal name, legal form, registration number, incorporation date, registered office, current status and the officers on file. KYB checks read from the statutory register, not inferred from a website.
UBO and ownership verification
Shareholders, beneficial ownership data, parents and subsidiaries, hop by hop across jurisdictions. Each hop is a registry lookup and each holding percentage is returned with the filing that recorded it.
Read financials
Filed financial statements as structured fields: turnover, profit, assets, liabilities, employees, by period. Where a register publishes documents rather than data, the fields are extracted from the filed document and the document reference stays attached.
Cite
Every value in the response carries the register, the filing reference, the retrieval timestamp and a link to the original document where the register publishes one. The agent passes these through to the user or the case file.
Log
The response is structured, so the resolved entity, the fields used and the sources can be written to the decision log without parsing prose. Re-running the query reproduces the same values against the same timestamp.
MCP server, Regis, bulk feed and API. One dataset behind all four.
The same registry records sit behind every route. Find the row that sounds like your agent; the route on the right is the one to take.
Data provenance, walked end to end.
Provenance is only useful if a reviewer can follow it from the sentence the agent wrote to the document the register holds. This is the walk, using our own record.
The sentence
What the user or the downstream system sees. Each value carries a marker back to the source list.
The record
The structured entry the marker points at: field, value, register, filing reference, time of read.
The document
The statutory filing itself, at the government register, opened independently of us.
When the register has no field
Some registers publish no financial statements, no shareholders or no beneficial owners for a given entity type. The response says so and names the register. A gap with a stated reason is a defensible entry in a case file. An estimate is not.
Freshness
Registers publish on their own schedules, from continuous to annual. Records are synced daily, and the retrieval timestamp on each value tells the agent, and the reviewer, which side of a register's update the read landed on.
Grounding an LLM and retrieving a record are two different things.
AI grounding adds context to a model that still answers from its weights. Regis is the retrieval-and-answer layer over this dataset. It runs on our own hardware, calls no third-party model API and holds no company facts in its weights. When a question asks for a field the register does not publish, it returns the gap and the reason. It does not fill it.
An agent on a general-purpose model will produce a turnover figure for any company you name. Regis returns nothing it did not read from a register on that request, so the agent's output inherits the same constraint.
Call POST /v1/regis/query with a question, or expose it through the MCP server as a tool for multi-step questions such as a full ownership chain. Structured endpoints remain available alongside it.
The written answer, the resolved entities, the fields used and the source records, in JSON. Written straight into a case management system without parsing prose.
Every major provider now has an MCP server. The difference is where the data came from.
Dun & Bradstreet, Moody's and Sayari all ship agent access and all describe their data as sourced. What separates them is how many hands the filing passed through before it reached your agent, and whether it can still be traced back.
Where this data layer is already doing the work.
AI agents for compliance, banking and financial services run the same six steps against one decision. Each workflow below links to the industry where it is most often deployed.
KYB API for onboarding agents
KYB automation for onboarding. Takes a company name from an application form, resolves it to the register, verifies status and officers, and writes a sourced decision to the case file.
Entity resolution software for agents
Deduplicates and matches company records across a CRM, a supplier master and an external list, on registration number rather than string similarity.
Claude MCP server for company data
The dataset exposed as MCP tools so an assistant or in-house agent framework calls it directly and receives sourced values.
UBO verification for AML agents
Walks a shareholding chain across jurisdictions to the natural persons in control, each hop returned against the register that recorded it.
Company financials for underwriting agents
Filed accounts as structured fields by period, so an underwriting agent reads turnover, assets and liabilities from the statutory filing and cites the document.
Supplier verification for procurement agents
Confirms a bidder or supplier is registered, active and owned by whom it declares, before a purchase order or contract award is issued.
Point your agent at a company you already know and check the filing it returns.
That is the fastest evaluation there is. A test key is issued from the platform, the MCP server connects in minutes, and bulk extracts are scoped with our team.