Check a business customer against the official record
Is the company real, active and who it says it is? Who runs it, and who owns it where that is published? NeuralVerge looks it up in national company registries and legal entity identifier records, and returns structured fields your onboarding flow or your analysts can act on.
What you ask, and what comes back
“A new customer signed up as “Nordpack AB, Sweden, org. no. 556xxx-xxxx”. Does that match the registry?”
What the customer told you, next to what the registry says.
| Field | Customer said | Registry says | Match |
|---|---|---|---|
| Legal name | Nordpack AB | Nordpack AB | Yes |
| Status | — | Active | — |
| Address | Storgatan 4, Malmö | Storgatan 4, Malmö | Yes |
| Legal form | AB | Aktiebolag | Yes |
Illustrative output — company and contact names are fictional.
Registry portals, one country at a time
Business verification is mostly lookups in official registries. The problem is that every country has its own registry, format and language.
Each market you onboard customers from means another registry to learn, another search form and another format to read.
Registries across Europe, the Americas and Asia-Pacific are called the same way and return structured fields, so a new market is a new parameter, not a new process.
Every business application means opening the registry, reading the extract and typing name, number, address and directors into your case system.
Call the registry lookup from your onboarding code over REST and compare the response to what the customer entered — analysts only see the mismatches.
A customer's company is dissolved or changes directors a year after onboarding, and nobody notices until something goes wrong.
Run the same lookup on existing customers periodically and flag status, officer and ownership changes for review.
Start in three steps
Call registry lookups over REST from your onboarding flow, or give analysts an MCP client for ad-hoc checks.
Search by name or registration number in the right country's registry and fetch the full record.
Match the record against what the customer told you. Pass the clean cases automatically; route mismatches to a person.
Claude Code and Claude Desktop: run this once. It registers NeuralVerge as an HTTP MCP server, and its tools appear in your next conversation. Replace YOUR_ACCESS_TOKEN with your NeuralVerge token.
claude mcp add --transport http neuralverge \ https://api.neuralverge.ai/functions/v1/mcp-server \ --header "Authorization: Bearer YOUR_ACCESS_TOKEN"
Verification that doesn't stop at onboarding
From a lookup at sign-up to periodic re-checks of your customer base — in your own code or scheduled in your agent.
Verify before the account goes live.
- Registry match on name, number and addressOnboarding flow
- Officers and owners for reviewCase system
Catch changes in your customer base.
- Status and officer changes on business customersCase system
Refresh the file with the current record.
- Full registry and LEI refreshCase system
Schedules run in your agent or your own code. NeuralVerge answers the lookups; it does not run or send anything on its own.
The sources this runs on
National company registries and LEI records: status, registration, officers, filings and ownership where published.
See the sourcesCompany profiles, websites and reviews to check the business is what it says.
See the sourcesEmail and phone validation for the contact details a customer gives you.
See the sourcesPublic company pages and people profiles for directors and signatories.
See the sourcesCommon questions
No. There is no document check, selfie or liveness verification. NeuralVerge covers the business side — company records, officers and published ownership — and email and phone validation. Pair it with an identity-verification provider for individuals.
Verify business customers against the official record
National registries and LEI records, one request format — over REST or MCP.