## Company name to official domain
Find a company's official website domain from its name. Use the result to match company records, prepare prospect lists, or pass a domain to a company enrichment workflow.
### Request
Send a JSON object containing only `company_name`, from 1 to 500 characters:
```json
{
"company_name": "Microsoft"
}
```
### Response
The synchronous JSON response includes `success`, `message` and `data`. A completed lookup returns HTTP 200. `data` contains:
- `domain`: the selected company domain, or `null` when no match is found.
- `confidence`: an integer from 0 to 100; a confidence estimate, not a guarantee of accuracy.
- `linkedin_url`, `industry`, `sub_industry` and `sector`, when available.
- `is_live`: the website status assessed during the search, or `null`; saved results are not a live uptime check.
- `reasons` and `lower_reasons`: reasons supporting the match and points of uncertainty.
A no-match result has `domain: null` and `confidence: 0`. An error is returned separately and must not be treated as a confirmed no-match. Ambiguous company names may produce uncertain matches; review the confidence and reasons before using a result.
### Pricing and repeated requests
The PAYG rate is $0.035 per completed lookup ($35 per 1,000 completed lookups). Both found-domain and no-match results are billable. Each repeated completed request is charged again, including found and no-match responses served from saved results.
Requests rejected for invalid input, authentication or rate limits are free. Server errors, provider failures and timeouts are also free.
Both found and no-match results are reused until manually updated by the operator. A repeated request does not force a new search, and there is no public refresh parameter.
### Limits and errors
Per buyer, up to 5 uncached lookup requests and 15 saved-result requests are allowed per minute. Repeats and no-match results count toward the corresponding limit. Up to 2 AI searches may run concurrently per buyer. Shared service limits also apply. On HTTP 429, follow `Retry-After`. Invalid input returns 422; service failures return 5xx.
Only a company name is accepted. Additional context, URLs, emails and batch requests are not separate supported inputs.