Company verification for AI agents: registries with receipts
KYB checks, officer and ownership lookups, lapsed-LEI screening, and supplier vetting — run live against Companies House, Brønnøysund, GLEIF, and SAM.gov through one MCP endpoint.
Ask a chatbot “who owns this company?” and you’ll get an answer. Whether it’s the answer on file with a registrar is another matter — and for compliance work, “on file” is the only version that counts.
The registries themselves are the fix. Company registers are public, authoritative, and most of them have APIs. Below are four verification workflows we watched run end-to-end on live registry data (July 2026), each through an AI agent connected to Pipeworx. Every answer carries its source record.
Verify a company in one question
The question: “Verify the Norwegian company Equinor ASA — registration number, status, and registered address.”
The agent queries Norway’s Brønnøysund register directly: organisation number 923609016, legal form ASA, the registered address — and the full historic-name chain, from Den norske stats oljeselskap through Statoil to Equinor. Name-history matters more than it sounds: entities that change names are exactly the ones due-diligence teams need to trace.
Same pattern in the UK: “Is Monzo Bank registered at Companies House?” returns company number 09446231, active status, incorporation date (2015-02-18), registered address, and a deep-link to the official Companies House record.
Officers and ownership, from the primary source
The question: “Pull the current officers for UK company number 08804411 — who is on the board and when were they appointed?”
Companies House returns the live officer list: 14 officers, 9 active and 5 resigned, each with role, appointment date, and service address. Follow up with the persons-with-significant-control register — “who ultimately owns or controls it?” — and the agent reads back the PSC record: Revolut Group Holdings Ltd, 75–100% ownership and voting rights, notified April 2022.
That’s an ownership chain with notified dates, not a paraphrase of a news article.
The lapsed-LEI check
The question: “Look up the LEI record for Wirecard — is its registration still active?”
GLEIF returns LEI 529900A8LX4KL0YUTH71: entity status active, registration status LAPSED, last updated November 2020 — the registration lapsed as the company collapsed. A lapsed LEI isn’t proof of anything by itself, but it’s exactly the kind of cheap, citable signal a screening workflow should catch automatically.
Supplier vetting across jurisdictions
The question: “Is Booz Allen Hamilton an active registered entity in SAM.gov for US federal contracting?”
SAM.gov confirms: UEI S3FCUG66GYK1, CAGE code 200M3, registration active. For the Norwegian supplier, the same agent pulls board roles from Brønnøysund — daily leader and board members with names and dates. One conversation, two national registers, both answers citable.
What this replaces
Not your screening platform, and not your judgment. It replaces the tab-farming: the five registry websites open before lunch, each with its own search quirks, feeding a case file by copy-paste. An agent wired to the registries does the lookups and keeps the receipts; the analyst does the analysis.
Wire it up
One MCP endpoint covers Companies House, Brønnøysund, GLEIF, SAM.gov, and 1,200+ other live sources:
https://gateway.pipeworx.io/pipeworx-catalog/mcpAdd it to Claude, ChatGPT, Cursor, or your own agent — the getting-started
guides cover each client. No key needed: ask in plain English
and the ask_pipeworx tool routes the question to the right register.