Company Name to Domain: Official Website from Wikidata

Turn a list of company names into official website domains, in seconds, with a label that says how sure the match is. Paste names such as "Stripe" or "Notion Labs, Inc." and get one row each: the domain (stripe.com), the website URL, the Wikidata item it was read from, and a confidence of high, medium or low. When a name is shared by several companies, the other candidates are listed so you can pick.

Who uses it: sales and marketing ops teams turning a company list into domains before enrichment, lead-list builders cleaning CRM exports, data teams joining company names to web data, and AI agents that need a company's website before they do anything else.

A miss is free. A name that Wikidata does not hold, or holds without an official website, comes back as a row with "found": false and is never charged.

How to use

1. In the Apify Console. Open the actor page and click Start — the companies field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~company-name-to-domain-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"companies":["Stripe","Shopify","Notion Labs"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "companies": [
    "Stripe",
    "Shopify",
    "Notion Labs"
  ]
}

One company name per line, e.g. Stripe. Case, punctuation, "&" versus "and" and Inc/Ltd/GmbH are ignored, so "Notion Labs" finds "Notion Labs, Inc.". Wikidata lists notable companies; a small local business usually comes back not found. Accepted formats: Stripe, Notion Labs, Spotify AB.

Put one company per line. Names are compared ignoring case, punctuation, "&" versus "and", a leading "The" and a trailing legal form (Inc, Ltd, GmbH, AB, PLC and similar), so "Notion Labs" finds an item whose alternative name is "Notion Labs, Inc.". Matching is strict on purpose: "Strype" does not find Stripe, and a near miss is never returned as a match. A not-found row names up to three close Wikidata labels in its message so you can retry.

Two optional run settings: onlyFound hides the not-found rows, and maxConcurrency (default 3, max 5) sets how many names are resolved at once.

How matching works

1. The name is searched on Wikidata, and only items whose label or alternative name equals it (after the clean-up above) are kept.
2. Each kept item's official-website claim is read. Retired, deprecated and ended websites are skipped, and items that are people are dropped.
3. If several items remain, the one carrying the most company facts (industry, headquarters, founding date, founder, parent, stock exchange and similar) wins, and the rest are returned in alternatives.

confidence is high when the winner has company facts and no other candidate does, medium when several candidates have them or the winner has none and stands alone, and low when the winner has none and others exist. Treat anything below high as a prompt to look at alternatives and description.

Output

One row per company found. Real rows from a run on 2026-10-11:

{
  "query": "Notion Labs",
  "found": true,
  "status": "OK",
  "domain": "notion.so",
  "website": "https://www.notion.so/",
  "wikidataId": "Q89269703",
  "matchedName": "Notion",
  "description": "collaboration software company",
  "matchType": "alias",
  "confidence": "high",
  "alternatives": [],
  "sourceUrl": "https://www.wikidata.org/wiki/Q89269703",
  "scrapedAt": "2026-10-11T19:25:39.795Z"
}

{
  "query": "Stripe",
  "found": true,
  "status": "OK",
  "domain": "stripe.com",
  "website": "https://stripe.com/",
  "wikidataId": "Q7624104",
  "matchedName": "Stripe",
  "description": "Irish-American payment technology company",
  "matchType": "label",
  "confidence": "high",
  "alternatives": [],
  "sourceUrl": "https://www.wikidata.org/wiki/Q7624104",
  "scrapedAt": "2026-10-11T19:25:39.833Z"
}

query	found	status	domain	website	confidence	matchedName	matchType	description	wikidataId	alternatives	sourceUrl	scrapedAt
Stripe	true	OK										1970-01-01T00:00:00.000Z

A miss comes back as a row with "found": false, a status (NOT_FOUND, BAD_FORMAT or BLOCKED) and a message that says why. It is never charged. Values Wikidata does not give are null, never 0 or an empty string.

Pricing

Billed per company resolved: $0.90 per 1,000 at the standard rate, less on higher Apify plan tiers (down to $0.45 per 1,000 at the top tier), plus a $0.002 start fee per run. Not-found names and errors are never charged. There is no key to bring and no proxy to pay for.

• Company resolved: $0.9 per 1,000 companies

Plus a $0.002 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are never charged.

What it covers

• Companies that have a Wikidata item with an official-website claim: in practice notable companies, brands and organisations worldwide. A small local business usually has no item and comes back not found.
• The domain is the website's host without www, as Wikidata states it. If the company's site lives on a subdomain, that is what you get, and website keeps the full URL.
• Wikidata is edited by volunteers, so a website can be out of date. Every row carries the sourceUrl of the item it was read from.
• The data is about organisations, not people: items that are people are never returned.

Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

Three well-known names. The default shape.

{
  "companies": ["Stripe", "Shopify", "Notion Labs"]
}

Legal names with suffixes, as they appear in a CRM export.

{
  "companies": ["Spotify AB", "Tesla, Inc.", "Siemens AG", "The Coca-Cola Company"]
}

A bulk clean-up where only resolved names should come back.

{
  "companies": ["Microsoft", "Adobe Inc.", "Zzzzqq Holdings Limited"],
  "onlyFound": true
}

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~company-name-to-domain-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"companies":["Stripe","Shopify","Notion Labs"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~company-name-to-domain-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"companies":["Stripe","Shopify","Notion Labs"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~company-name-to-domain-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"companies":["{{company}}"]}, mapping the row's company into the companies array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "company name to domain lookup" — the agent will find and run this actor.