DISTRIBUTOR ATLAS

Data & API

Everything on this site is available as JSON — no key, no auth. The graph currently holds 14,571 companies and 21,989 verified relationships. “Verified” means the manufacturer’s own website names the distributor; every relationship carries the source_url of that official page. Only verified relationships are published — a company with none has no page here, and absence means “not verified yet”, never “does not exist”.

Endpoints

endpointwhat it returns
/company/{slug}.jsonone company with every relationship + evidence URLs (example; legacy {id}.json still works)
/api/search.json?q=…search — top matches by name, brand, alias, sector, or domain
/api/export/companies.json?page=1all companies (sector + indicative NAICS), 1,000 per page, next link included
/api/export/edges.json?page=1all verified relationships with sources and product-line scope, 1,000 per page
/sitemap.xml · /llms.txtcrawler guides — every company page, and a plain-text site summary for AI agents

Fields worth knowing

sector is a house classification tuned to this graph, with an indicative 2022 NAICS code alongside it for interop. edge.scope, when present, is the product line the official list covers — manufacturers often run separate distributor networks per line (e.g. crushing vs pumps), so a distributor verified for one line is not automatically verified for the whole brand. parent_companies / brands capture corporate structure (brand-of, subsidiary-of), each relation carrying the source URL that states it — brands keep their own pages because their networks are often separate.

Method

The graph is built by continuously reading manufacturers’ own published distributor lists (dealer locators, static pages, PDFs). Distributors’ line cards are read too, but only as crawl leads — they are never published as relationships. Removals only happen when a complete official list is re-read without the distributor on it — an unread list is never treated as a negative. Change history is preserved and browsable under Changes.