Does the normalised identifier follow a published structural rule?
PRODUCT
Resolve the company.
Use the evidence in the right workflow.
Start with a company name, VAT number, EIN, registration number or supported identifier. Resolve the legal entity, review what the returned evidence proves, and choose the delivery method that fits the operating job.
VAT LOOKUP TOOLS
Start with the information you already have.
01
VAT NUMBER LOOKUP BY COMPANY NAME
Find a VAT number by company name.
Legal company name + registration countryMatched company + available VAT or tax ID
Open the task 02
VAT & EIN COMPANY MATCH
VAT number checker and EIN company lookup.
VAT number or US EIN + countryCompany-record match + legal entity context
Open the task 03
US EIN LOOKUP
EIN lookup by company name.
US legal company name + optional stateMatched US company + available EIN
Open the task WHAT VATFIND RETURNS
One resolved entity. Fields that explain the match.
A useful result is more than an identifier in isolation. VATFind keeps the legal company, business identifiers, available company context and evidence details together while preserving the meaning of each field.
- Legal identity
- Legal name, jurisdiction, registration number and legal form where those fields are available.
- Business identifiers
- VAT, EIN and supported tax identifiers kept separate from company registration numbers.
- Company context
- Registered address, source-reported company status, incorporation date and website where the returned record supports them.
- Evidence context
- Resolution outcome, source and retrieval time. Field presence differs by delivery method, country and individual record.
DELIVERY OPTIONS
Connect systems, data platforms and AI agents.
REST API
Integrate company identity into an application.
Use deterministic requests, explicit result states, idempotency and stable error handling.
Explore the REST APIMCP FOR AI AGENTS
Ground agent answers before action.
Expose scoped company tools inside an MCP-compatible client while your agent policy controls the next step.
Explore MCP accessMONITORING
Choose which evidence must stay current.
Run company-change monitoring in the workspace, and assess authority-backed VAT-status monitoring separately by country.
Compare monitoring typesBULK DATA DELIVERY
Scope company identity for a data platform.
Define the population, countries, attributes, record keys, change semantics and refresh design before delivery.
Plan a bulk feedDELIVERY COMPARISON
Five ways to use the same evidence model.
| Delivery | Best fit | Operating pattern | Access and evidence |
|---|---|---|---|
| Web lookup | One company reviewed by a person | Search, compare candidates and open the selected record | Browser result with source and retrieval context |
| REST API | Deterministic application and workflow calls | Request/response integration with explicit statuses, errors and idempotency | Bearer key, sandbox and live environments |
| MCP | AI agents that need governed company tools | Typed tool calls controlled by the client and agent policy | OAuth scopes, structured output and workspace usage |
| Monitoring | Evidence rechecks after onboarding | Self-service company-change monitoring; VAT-status monitoring requires confirmed authority coverage | Separate alert semantics, sources and operational states |
| Bulk delivery | Agreed company populations and data platforms | Snapshot or change design scoped to countries, fields and cadence | Contracted schema, transfer, licensing and quality controls |
ONE RESULT, SEVERAL FACTS
Do not collapse identity, format and status into one label.
The REST and MCP result model keeps number format, company-record association, tax-authority status and company legal status separate. A field can be unsupported or unavailable without changing the meaning of the other evidence.
Read exact status semanticsDid the identifier return a matched, ambiguous or no-match company-data result?
A separate capability field. It must not be inferred from a company match when unsupported or not checked.
The legal-company state returned by the available company record.
ENTERPRISE READINESS
Decide these five points before production.
A technically successful integration can still fail if teams disagree about evidence, exceptions or ownership.
- Countries and identifier types required at launch.
- Fields that drive a decision and fields that are only context.
- How matched, ambiguous, not-matched and unavailable results are routed.
- Evidence retention, source display and reviewer ownership.
- Volume, latency, refresh, licensing and security requirements.
CHOOSE THE RIGHT DELIVERY
A browser lookup and a production data workflow serve different jobs.
Use individual lookup for one-off searches, REST for application calls, company monitoring for scheduled company-record rechecks, MCP for governed agent tools, and bulk delivery for an agreed population or change design. Confirm VAT-status coverage separately when authority status matters.
PRODUCT QUESTIONS
What VATFind does—and where each workflow fits.
Compare web lookup, REST, MCP, monitoring and bulk delivery against the evidence you need.
What does the VATFind product do?
VATFind helps resolve a legal company from a name or supported business identifier and returns available company-record evidence with source and retrieval context. It supports individual lookup and governed automated workflows.
Can VATFind find a VAT number by company name?
Yes, where the selected company record supplies a VAT or tax identifier. Search using the legal name and jurisdiction, compare the candidate entities, and treat an unavailable identifier as missing data rather than proof of absence.
Can VATFind check a VAT number or EIN?
VATFind can search for company-record evidence associated with a submitted VAT number, EIN, or other supported identifier. Result states distinguish format, registry association, authority capability, and company legal status.
What company fields can VATFind return?
Fields can include legal name, registration number, jurisdiction, company status, address, VAT or tax identifiers, legal form, source, and retrieval time. Availability varies by country, source, delivery, and individual record.
What is the difference between VATFind web lookup and REST API?
Web lookup is designed for an individual to search, review, save, or monitor records in a workspace. REST provides a deterministic structured contract for application workflows, keys, idempotency, usage, monitors, events, and webhooks.
When should I use VATFind MCP instead of REST?
Use MCP when a compatible AI client needs scoped typed tools through OAuth. Use REST when your application should make deterministic server-to-server calls with API keys and direct control over orchestration.