Company data API
The company data API turns a domain into one structured record: company name, tagline, description, logo, industry, founding year, headquarters, postal addresses, emails, phones and social profiles. It reads the company’s own website at request time — no licensed database — for $0.03 per delivered profile.
$0.03 per delivered profile · $2 free every month · Failed runs never billed
$ curl $QD/company_profile/run \
-H "Authorization: Bearer $QD_API_KEY" \
-d '{ "domain": "quantumproxies.io", "use_ai": true }'
{ "status": "done", "count": 1,
"results": [
{ "domain": "quantumproxies.io",
"name": "QuantumProxies",
"description": "Residential and mobile proxy…",
"industry": "Web data infrastructure",
"headquarters": "Italy",
"emails": ["support@…"],
"socials": { "linkedin": "https://…" },
"ai_used": true } ],
"cost": 0.03 }
# 1 profile × $0.03 · a domain that resolves to nothing is free
What a company data API returns
A company data API turns an identifier you already have — here a domain — into a structured record about the business behind it. Most of them serve a licensed database: a snapshot of the world, refreshed on their schedule, sold with minimums. This one reads the company’s own website when you ask, so the answer is as current as the site.
It loads the homepage plus the about and contact pages, takes the deterministic fields first — JSON-LD Organization, meta tags, logo, addresses, emails, phones, socials — and then, if use_ai is on, completes description, industry, founding year and headquarters from the text of those same pages. ai_used and pages_used come back on the record, so you always know how a field was produced.
Two neighbours are worth knowing: the email scraper API if all you need is contacts at $0.02 per site, and scrape company data when you want a whole list built and delivered as a dataset rather than a call per domain.
What comes back for every company
One record per domain, sixteen published fields. Anything the site does not say comes back null — nothing is inferred silently.
| Field | Type | What it holds |
|---|---|---|
name · tagline | string | Company or brand name and its positioning line. |
description | string | What the company does (meta description, or AI from the pages). |
industry | string | Industry or sector (AI completion). |
founded | string | Founding year, from JSON-LD or AI. |
headquarters | string | HQ city and country. |
addresses | string[] | Postal addresses found on the site. |
emails · phones | string[] | Contact points published on the pages read. |
socials | object | Facebook, Instagram, LinkedIn, X, YouTube, TikTok URLs. |
logo | string | Logo URL from JSON-LD or og:image. |
language | string | Language the site is published in. |
pages_used · ai_used | string[] · boolean | Which pages built the record, and whether AI completion ran. |
Inputs: one domain
Validated before the run — a malformed domain is a 400, not a charge.
| Input | Type | Required | What it does |
|---|---|---|---|
domain | string | yes | Company domain or site URL — "stripe.com", "https://example.co.uk". |
use_ai | boolean | no | Default true: completes description, industry, founded and headquarters from the pages. Off = deterministic fields only. |
country | string | no | Proxy exit geo, for sites that vary by region. |
Pricing
What a company profile costs
One delivered profile is $0.03 — page loads, parsing and the optional AI completion included, with no minimum spend and no annual licence. Enriching 1,000 domains is $30 at list price; the free $2 covers about 66 profiles a month.
Pay as you go
- $2 free credit / month
- 60 requests / min
- List unit prices
Starter
- $15 free credit / month
- 300 requests / min
- 10% off unit prices
Growth
- $50 free credit / month
- 600 requests / min
- 20% off unit prices
Scale
- $250 free credit / month
- 1,200 requests / min
- 30% off unit prices
Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.
Integration
One POST, typed rows
Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/.
# one domain → one structured profile
curl https://api.quanticdata.io/v1/scraper/collectors/company_profile/run \
-H "Authorization: Bearer $QD_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "domain": "quantumproxies.io", "use_ai": true }'
What people run it for
Every one of these starts from a domain somebody already has and cannot do much with.
CRM and lead enrichment
A form fill gives you an email domain; this gives you the company behind it — description, industry, HQ, socials — so routing and scoring happen on facts rather than on the domain string.
Vendor and partner due diligence
Check what a supplier actually publishes about itself: legal name, addresses, founding year, contact points. pages_used keeps the evidence trail.
Investment and market mapping
Profile a list of domains in a category and compare positioning in their own words, which is a different and often better signal than a licensed sector code.
Agent research loops
An agent with the MCP server goes from a company name to a domain to a profile in a couple of calls, with the source pages attached to the answer.
Collector vs licensed databases vs registries
The "company data api" SERP is full of licensed datasets — this is deliberately not one.
| Licensed data providers | Company registries | This collector | |
|---|---|---|---|
| Source | their stored index | official filings | the company’s own live website |
| Freshness | their refresh cycle | filing cadence | read at request time |
| Coverage | large but uneven outside the US | one jurisdiction each | any company with a website |
| Commercials | annual contracts and minimums | per-lookup or bulk files | $0.03 per delivered profile |
| Fields | firmographics, sometimes financials | legal and financial filings | positioning, industry, HQ, contacts, socials, logo |
Registries, databases and a company's own words
Official registries hold the authoritative legal facts — registration number, incorporation date, officers, filings — and nothing scraped from a marketing site substitutes for them in compliance work. What they do not hold is what a company actually does today: the legal name is often a holding entity, the registered address is often an accountant's office, and the industry code was chosen at incorporation and never revisited.
Commercial B2B databases hold verified headcount, revenue estimates and hierarchy for thousands a year, with coverage skewed to larger companies and records that age between passes. This sits between them: current, self-published positioning for any company with a website. Use a registry for legal facts, a database for verified financials, and the website for what the company says it is right now.
Limits, provenance and the legal bit
One company per run, by design — the output is an assembled profile rather than a list, so a domain list is one run each and they parallelise rather than queue. Sites that are entirely client-side rendered, or that publish nothing about themselves, produce thin profiles, and pages_used shows what was actually available. Throughput is your plan's rate limit rather than anything about the collector: 60 requests/minute on pay-as-you-go, up to 1,200 on the top tier.
When use_ai is on, treat inferred fields as inferred. Founding year, industry and headquarters are often stated as prose in an About page and never marked up anywhere a parser can reach, which is exactly the case a model handles well and exactly the case where it can be confidently wrong. ai_used is returned on every record so downstream systems can weight those fields differently — and for anything consequential a registry lookup is the correct check.
Collecting publicly visible data is generally lawful in most jurisdictions, and courts have repeatedly declined to treat reading a public page as unauthorised access. Corporate information sits largely outside personal-data law, though a named founder or a sole trader's details do not. Marketing use of the collected contacts is governed separately. None of this is legal advice — get some for your actual use case.
FAQ
What people ask when comparing company data APIs — where the data comes from, and what it costs.
Something else? Ask us →What API can I use to get company details?
This one takes a domain and returns a structured profile: name, tagline, description, industry, founding year, headquarters, addresses, emails, phones, socials and logo, at $0.03 per delivered profile. For contact details alone, the email scraper API is $0.02 per site.
Where does the data come from?
From the company’s own website, read when you call: homepage plus about and contact pages. There is no licensed database behind it, which is why coverage is "any company with a website" rather than "the companies in our index", and why the record reflects the site as it is today.
Is there a free company data API?
The $2 monthly allowance covers about 66 profiles with no card, and renews monthly. Open registries like OpenCorporates cover legal filings for free in many jurisdictions — a different dataset from what a company publishes about itself.
What does use_ai actually do?
Deterministic fields — name, logo, addresses, emails, phones, socials — are parsed from JSON-LD and metadata either way. With use_ai on, an LLM reads the same pages to fill description, industry, founding year and headquarters when they are not machine-readable. The record tells you which mode ran via ai_used.
Can I enrich a whole list of domains?
Yes — call it once per domain, in parallel if you like, billed per delivered profile. For contacts across many domains in one call, site_contacts takes up to 200 at a time; for a curated list delivered as a file, use scrape company data.
What if the domain has no real website?
Parked domains, redirects to marketplaces and dead hosts deliver no usable profile — and a run that delivers nothing is not billed. Malformed domains are rejected by input validation before any request goes out.
Can I trust the AI-extracted fields?
Treat them as inference rather than fact, which is why ai_used is on every record. They are drawn from what the company writes about itself, so they are usually current and occasionally aspirational. For legal facts — registration number, officers, incorporation date — use a company registry.
Why is the input a domain rather than a company name?
Because a domain is unambiguous and a name is not. Name matching introduces exactly the class of silent error that makes an enrichment pipeline untrustworthy — the wrong company, confidently. If you only have names, resolve them to domains first with the search collector.
Start with the Company data API
$0.03 per delivered profile, $30 per 1,000 delivered profiles. $2 of free credit every month, no card — and a run that delivers nothing is never billed.
Get my free API key