Global Company Search avatar

Global Company Search

Pricing

from $0.005 / actor start

Go to Apify Store
Global Company Search

Global Company Search

Search company names, registration numbers, LEIs, and VAT IDs across 40+ countries in one run. Get structured company data fast for research, onboarding, and vendor checks.

Pricing

from $0.005 / actor start

Rating

0.0

(0)

Developer

kane liu

kane liu

Maintained by Community

Actor stats

0

Bookmarked

7

Total users

4

Monthly active users

12 days ago

Last modified

Categories

Share

Verify a company across borders in one query. Search verified official registries across 40+ countries and entity systems such as GLEIF, VIES, FDIC, SEC, and national company registries. Get registration status, LEI, VAT validation, regulated institution records, addresses, and source-level provenance from primary public records.

If you've ever needed to verify an overseas supplier, build a due-diligence dossier, or check a company's LEI and VAT before a cross-border contract, this Actor is built for that workflow. You run one search and get back source-tagged records from the relevant official registries without integrating dozens of government APIs one by one.


Who is this for?

  • 🌍 Sourcing agents & procurement consultants verifying overseas suppliers before contracts
  • 🔎 Due diligence & KYB freelancers building company dossiers from official records
  • 📦 Import/export & trade compliance checking trading partners across jurisdictions
  • 💼 M&A and PE analysts doing entity-level research across multiple countries
  • 🏦 Trade finance & factoring brokers verifying counterparty existence + LEI
  • 💻 SaaS / platform developers embedding company verification without integrating dozens of separate registry APIs

If you need official public records before you commit to enterprise verification tooling, this is a practical starting point.


What you can do with it

1. Verify an overseas supplier before signing

In plain English: enter a supplier name, registration number, LEI, or VAT number and get back official company or institution records from the relevant public registries. That lets you quickly check whether the entity exists, whether it is active, and which registry actually returned the match.

You give:

FieldWhat to enter
Search queryCompany name, registration number, LEI, or VAT number
CountryOptional — the Actor can narrow by ISO-2 country code if you want fewer matches

You get back (table, exportable as Excel / CSV / JSON):

NameStatusCountryAuthorityLEIRegistration Number
Deutsche Bank AktiengesellschaftACTIVEDEGLEIF7LTWFZYICNSX8D621K86HRB 30000
DEUTSCHE BANK TRUST CO AMERICASActiveUSFDIC623
..................

2. Build a cross-border due diligence dossier

In plain English: one search can return a company's footprint across multiple countries and registries. Instead of checking Companies House, INSEE, GLEIF, VIES, FDIC, and state registries separately, you get one dataset with shared preview fields and full source provenance.

Example: search "Acme" and the Actor can return matches from UK company sources, French registries, GLEIF LEI records, US state registries, and other jurisdictions where an Acme-named entity exists.

Useful for:

  • Assembling a full company footprint in minutes
  • Identifying related entities across jurisdictions
  • Checking sanctions-adjacent jurisdictions
  • Generating a paper trail for audit / compliance

3. Validate LEI, VAT, SIREN, ABN, EIN — auto-routed

In plain English: paste a structured identifier and the Actor routes the query to the most relevant source family before returning the matching official record.

The routing logic supports patterns such as:

Identifier typeExampleRoutes to
LEI (20-char)7LTWFZYICNSX8D621K86GLEIF global registry
EU VAT numberDE123456789EU VIES
French SIREN552120222Recherche Entreprises
Australian ABN51824753556ASIC
US EIN123456789IRS Nonprofits / SEC

This saves you from manually figuring out which registry should handle which identifier.


4. Cross-reference your trade / customs / CRM data against official registries

In plain English: if you already have a list of company names from customs records, CRM, supplier lists, or trade documents, you can run those queries through this Actor and enrich them with official registry data.

Useful for:

  • Cleaning supplier master data
  • Enriching customs / import records with official entity metadata
  • Flagging dormant or dissolved trading partners
  • Preparing data for entity resolution pipelines

5. Embed company verification in your product (for SaaS builders)

In plain English: call the Actor from your backend through Apify and get structured company records without individually wiring up every government registry.

Works natively with:

  • LangChain / AI agents (MCP ready)
  • Make.com / n8n / Zapier for no-code workflows
  • Python / Node.js via Apify SDK

How to use (no code required)

  1. Click "Try for Free" at the top of this page
  2. Enter a company name, LEI, VAT, or registration number
  3. (Optional) Add a country filter if you want to narrow scope
  4. (Optional) Increase maxResults if you expect many matches
  5. Click Start — results appear in seconds

Download as Excel, CSV, JSON, or XML.

If you are testing with a new Apify account, the free trial credit is usually enough to run real supplier checks before you spend anything.


What you get back

Each result has three layers so you can work at the level you need:

Provenance (audit trail)

Every single result carries full source attribution — you always know exactly where the data came from and when.

  • _source_authority — Official government body (e.g. "European Banking Authority")
  • _source_name — Human-readable source name (e.g. "GLEIF LEI — Germany")
  • _retrieved_at — Exact retrieval timestamp (ISO 8601)
  • _data_freshnessreal-time, cached_12h, or preloaded
  • _response_time_ms — How long the source took

Unified preview fields (normalized across sources)

  • name, type, status, country, authority
  • registration_number, lei, vat_number, address

That makes the first review pass much easier whether the record came from GLEIF, a national company registry, FDIC, VIES, or an EU financial authority dataset.

Raw fields (source-specific)

Complete unmodified data from each registry. Different registries return different fields — the raw layer preserves everything, so you're never missing information the source actually published.


Countries & sources covered

This Actor currently routes across verified official sources covering 40+ countries and cross-border entity systems.

RegionExamples
AmericasUS state business registries, FDIC, SEC, IRS nonprofit records, Canada federal and BC sources
EuropeFR, DE, IT, GB, NL, CH, BE, ES, FI, SE, DK, PL, GR, IE, VIES, GLEIF, and EU financial authority registers
Asia-PacificAU, SG, NZ, IL
EU financial regulatorsEBA (banking), ECB (MFI + supervised banks), EIOPA (insurance), ESMA (investment)
Global / cross-borderGLEIF LEI Registry, GLEIF mapping, VIES VAT validation

Data freshness: this Actor returns a mix of real-time, cached_12h, and preloaded public records depending on the source. Every result includes freshness and provenance metadata so you can decide how to use it.


Pricing

Pay per result. No subscription, no minimums, no seat fees.

VolumePrice
1 result$0.003
30 results (typical search)~$0.09
200 results (bulk lookup)~$0.60
1,000 results~$3.00

How this compares:

Compared with subscription-heavy verification tooling, this Actor is designed to be lightweight, usage-based, and easy to test before you commit to a larger workflow.


Connect to your tools

PlatformHow to connect
Make.comSearch "Apify" → "Run Actor" → Actor ID: lentic_clockss/global-company-search
n8nAdd Apify node → "Run Actor" action → same Actor ID
ZapierApify integration → "Run Actor" trigger
LangChainApifyActorsTool("lentic_clockss/global-company-search")
MCP (AI agents)Auto-discoverable via https://mcp.apify.com

Example: Claude / GPT / Cursor (MCP)

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com",
"headers": {
"Authorization": "Bearer YOUR_APIFY_TOKEN"
}
}
}
}

Then ask: "Look up Deutsche Bank's legal entity registration data"

Example: Python direct call

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("lentic_clockss/global-company-search").call(
run_input={"searchQuery": "Deutsche Bank", "country": "", "maxResults": 50}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["name"], "—", item.get("lei"), item.get("country"))

Example: direct HTTPS

curl "https://api.apify.com/v2/acts/lentic_clockss~global-company-search/runs" \
-X POST \
-H "Authorization: Bearer YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchQuery": "Deutsche Bank", "country": "", "maxResults": 50}'

When to use something else

If you need...Use this instead
Entity resolution / deduplication logicBuild on top (results preserve all matches by design)
UBO (ultimate beneficial owner) chainsSpecialized KYB platforms (Kyckr, Moody's KYC)
Credit scoring / risk ratingsDun & Bradstreet, Experian
Private company financialsBureau van Dijk / Orbis
Formal KYC/KYB compliance with regulator sign-offLicensed KYB/KYC vendor with attestation

This Actor gives you underlying official public records and provenance, not a final legal, credit, or compliance opinion.


FAQ

Q: Are duplicate results removed? A: No — by design. Each result carries full source attribution (_source_name, _source_authority) so you can apply your own dedup/matching logic. A German company might show up from GLEIF AND from an IHK register — both records are given to you so you can decide which is canonical.

Q: How fresh is the data? A: Freshness depends on the source. Results include _data_freshness so you can tell whether the row came from a real-time query, a 12-hour cache, or a preloaded public dataset.

Q: Do I need my own API keys for each source? A: No. The Actor handles authentication with all 82 government APIs. You only need your Apify token.

Q: Can I search by VAT number or LEI directly? A: Yes. The Actor auto-detects LEI (20 chars), EU VAT, French SIREN, Australian ABN, and US EIN and routes to the matching registry. Just paste the identifier into the search field.

Q: What if the company name has special characters or isn't in English? A: The Actor works with the name exactly as registered (UTF-8 supported). For Asian-character names, search with the local-script name for best results in country-specific registries.


Input reference

For developers who want full control:

ParameterTypeDefaultDescription
searchQuerystringrequiredCompany name, registration number, LEI, VAT, SIREN, ABN, or EIN
countrystringoptionalISO 3166-1 alpha-2 country code (e.g. DE, FR, US) — narrows search to that jurisdiction
maxResultsinteger50Max results returned per source (1-200)

Full output schema is available in the Dataset tab.


→ Browse all Actors: apify.com/lentic_clockss


Also Available

  • Direct API: https://opendata.best/api/v1/data — use with any HTTP client and your API key
  • Postman Collection: Fork and test — pre-built requests with example responses
  • GitHub: Collection source files — import JSON into any API client