# Company Name to Domain: Official Website from Wikidata (`accountable_eel/company-name-to-domain-lookup`) Actor Turn a company name into its official website domain, read from Wikidata: domain, Wikidata ID, a match-confidence label and other candidates when the name is ambiguous. Pay only for names that resolve. - **URL**: https://apify.com/accountable_eel/company-name-to-domain-lookup.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Lead generation, Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.45 / 1,000 company resolveds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## 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: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~company-name-to-domain-lookup/run-sync-get-dataset-items?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 ```json { "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: ```json { "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" } ``` ```json { "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. ```json { "companies": ["Stripe", "Shopify", "Notion Labs"] } ``` **Legal names with suffixes, as they appear in a CRM export.** ```json { "companies": ["Spotify AB", "Tesla, Inc.", "Siemens AG", "The Coca-Cola Company"] } ``` **A bulk clean-up where only resolved names should come back.** ```json { "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. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~company-name-to-domain-lookup/run-sync-get-dataset-items?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=`, 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=`, 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. # Actor input Schema ## `companies` (type: `array`): 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. You're only charged for the ones we actually find — a miss costs nothing. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. This target is a free public API that needs no proxy — defaults to off, but you can turn one on if you prefer. ## Actor input object example ```json { "companies": [ "Stripe", "Shopify", "Notion Labs" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "columns": [ "domain", "website", "confidence", "matchedName", "matchType", "description", "wikidataId", "alternatives", "sourceUrl" ], "maxConcurrency": 3, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "companies": [ "Stripe", "Shopify", "Notion Labs" ], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/company-name-to-domain-lookup").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "companies": [ "Stripe", "Shopify", "Notion Labs", ], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/company-name-to-domain-lookup").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "companies": [ "Stripe", "Shopify", "Notion Labs" ], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/company-name-to-domain-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/company-name-to-domain-lookup" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/ld2ercdYdz7M2bYwh/builds/wjjOqSnlmN1v9bSJ4/openapi.json