US Vehicle & Equipment Manufacturer Leads Scraper — NHTSA vPIC (Contacts, Principals & Products)

Extract every US motor-vehicle and motor-vehicle-equipment manufacturer from the official NHTSA vPIC manufacturer registry in one run — the ~20,000 companies that build, import, alter or finish vehicles and regulated equipment for the US market (filed under 49 CFR Part 566). Every record comes back as a ready-to-use B2B lead: company name + DBAs, full address, contact e-mail, phone and fax, a named principal (owner / president / CEO) with title, manufacturer type(s), the vehicle types + GVWR classes and equipment items they make, the stated primary product, and a derived lead score.

No login, no cookies, no browser, no API key — fast, reliable extraction straight from the federal NHTSA vPIC API.

Why this vehicle manufacturer scraper?

Every other NHTSA scraper on the market pulls recalls, complaints, crash data or VIN decodes. None of them turns the vPIC manufacturer registry into a contactable lead list. Generic Google-Maps "auto parts" scrapers grab a guessed e-mail and miss the regulatory firmographics that let you segment and qualify the automotive supply chain. This actor reads the official registry directly and ships the richest manufacturer dataset in the category — firmographics and contacts and product detail in one clean table.

Data	Recall / Maps scrapers	This actor
Company name + DBAs	partial	✅
Full address (street, city, state, ZIP, country)	partial	✅
Contact e-mail	guessed	✅ from the federal record
Contact phone + fax	guessed	✅
Named principal (owner / president / CEO) + title	❌	✅
Manufacturer type (vehicle / equipment / importer / alterer / final-stage…)	❌	✅
Vehicle types built + GVWR weight classes	❌	✅
Equipment items manufactured	❌	✅
Stated primary product	❌	✅
Record last-updated date (freshness / new-registration signal)	❌	✅
Derived lead score + lead signals	❌	✅
Only-new / changed monitoring mode	❌	✅

Who buys vehicle & equipment manufacturer data?

• Automotive parts & component suppliers (Tier 1/2/3) — sell castings, electronics, fasteners, seating, lighting, glazing, brakes and trim to the OEMs, trailer builders, RV makers, upfitters and equipment manufacturers who actually build the product.
• EV, battery, charging & powertrain suppliers — find completed- and final-stage vehicle manufacturers by vehicle type and weight class.
• Contract manufacturing, tooling, machinery & raw materials — reach SMB manufacturers (trailers, truck bodies, specialty & low-volume vehicles) that buy steel, aluminum, plastics and capital equipment.
• FMVSS compliance, homologation & test labs — target newly-registered and active manufacturers, importers and alterers who need certification.
• Recall, quality & traceability software (and PLM/ERP/MES) — sell to manufacturers segmented by type and product.
• Customs, freight forwarding, logistics & trade finance — importers and manufacturers are recurring shipping and working-capital accounts.
• M&A, market & competitive intelligence — map the full US vehicle & equipment manufacturing field, by type, product and geography.
• Industry media, trade shows & recruiting — a clean, segmented list of every registered manufacturer with a named contact.

How to use

1. Sign up for Apify — the free plan is enough to try this actor.
2. Open the US Vehicle & Equipment Manufacturer Leads Scraper, optionally pick manufacturer types (vehicle / equipment / importer / alterer…), a company name, vehicle types, states or US-based only, add any contact filters, and choose your limit.
3. Click Start and watch records stream into the dataset table.
4. Export as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the Apify API.

Input

{
    "manufacturerTypes": ["vehicleManufacturer", "equipmentManufacturer"],
    "vehicleTypes": ["Trailer", "Truck"],
    "usBasedOnly": true,
    "hasContactOnly": true,
    "sortBy": "leadScore",
    "maxResults": 1000
}

• manufacturerTypes — keep only vehicleManufacturer, completedVehicle, incompleteVehicle, finalStage, intermediate, equipmentManufacturer, importer, alterer, replica. Filtered server-side for speed. Leave empty to scan the whole registry.
• nameQuery — find manufacturers whose name contains this text (e.g. freightliner, trailer, Tesla). Uses a fast name lookup that returns full contact detail directly.
• manufacturerIds — look up specific NHTSA vPIC manufacturer IDs (e.g. ["955","1084"]).
• vehicleTypes — keep only manufacturers that build these vehicle types (Passenger Car, Truck, Motorcycle, Trailer, Bus, MPV…).
• states / cities / countries / usBasedOnly — location filters (2-letter US state codes).
• primaryProductContains — filter on the manufacturer's stated primary product (e.g. trailer, tire).
• hasEmailOnly / hasPhoneOnly / hasNamedPrincipalOnly / hasContactOnly — contact filters.
• updatedWithinDays — only manufacturers whose record was updated within N days (freshness / newly-registered signal).
• minLeadScore / maxResults / sortBy / deduplicateResults — output controls. Sort by leadScore (default), recentlyUpdated, name, or source.
• maxEnrichments / enrichConcurrency — performance controls (how many manufacturer detail lookups to perform, and how many in parallel). Raise maxEnrichments for deeper score-ranked or state-filtered pulls.
• monitorMode / monitorKey — only return manufacturers that are new or changed since the last run.
• proxyConfiguration — optional; the source is public US-government data and needs no proxy, so leave it off for the fastest queries.

Output

By default you get one clean, dense table of manufacturers. A record:

{
    "recordType": "manufacturer",
    "source": "NHTSA vPIC Manufacturer Registry",
    "mfrId": 955,
    "name": "Tesla, Inc.",
    "legalName": "TESLA, INC.",
    "commonName": "Tesla",
    "dbaNames": [],
    "manufacturerTypes": ["Completed Vehicle Manufacturer"],
    "isVehicleManufacturer": true,
    "isEquipmentManufacturer": false,
    "isImporter": false,
    "primaryProduct": null,
    "vehicleTypes": [
        { "name": "Passenger Car", "isPrimary": true, "gvwrFrom": "Class 1A: 3,000 lb or less", "gvwrTo": "Class 1D: 5,001 - 6,000 lb" },
        { "name": "Truck", "isPrimary": false, "gvwrFrom": "Class 2G: 8,001 - 9,000 lb", "gvwrTo": "Class 8: 33,001 lb and above" }
    ],
    "vehicleTypeNames": ["Passenger Car", "Truck", "Multipurpose Passenger Vehicle (MPV)"],
    "primaryVehicleType": "Passenger Car",
    "equipmentItems": [],
    "equipmentItemCount": 0,
    "street": "1 Tesla Road",
    "city": "Austin",
    "state": "TX",
    "stateName": "Texas",
    "postalCode": "78725",
    "country": "United States",
    "isUSBased": true,
    "fullAddress": "1 Tesla Road, Austin, TX, 78725",
    "phone": "(508) 272-8358",
    "fax": null,
    "email": "erwilliams@tesla.com",
    "hasContact": true,
    "principalName": "Elon Musk",
    "principalPosition": "CEO",
    "lastUpdatedDate": "2026-06-16",
    "updatedDaysAgo": 5,
    "leadScore": 92,
    "leadSignals": ["E-mail on file", "Named principal (Elon Musk, CEO)", "Vehicle manufacturer", "Record updated in last year"],
    "scrapedAt": "2026-06-21T05:10:00.000Z"
}

Every record also carries the raw NHTSA vPIC detail row under sourceFields unless you turn off includeRawFields. Switch the dataset view to Leads, Contacts, or Products & types for a focused table.

What to expect (field coverage)

vPIC contact fields are populated when a manufacturer filed them with NHTSA, so they're common but not universal. Verified across the registry, you can typically expect:

Field group	Coverage
Company name, manufacturer type, country	✅ ~100%
Full street address	✅ ~100%
Phone	✅ ~60–65%
Named principal (owner / CEO) + title	✅ ~55%
E-mail	✅ ~40%
Vehicle types + GVWR / equipment items	✅ when the manufacturer reports them

A blank field means the manufacturer didn't file that detail with NHTSA — not that scraping failed. Nothing is dropped, so you always get the richest record available. We never fabricate contact data.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it weekly/monthly with monitoring mode to capture newly-registered manufacturers and updated contacts as fresh leads.
• Webhooks — trigger downstream actions (CRM import, Slack alert, e-mail sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/vehicle-manufacturer-leads').call({
    manufacturerTypes: ['vehicleManufacturer'],
    usBasedOnly: true,
    hasContactOnly: true,
    sortBy: 'leadScore',
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} manufacturers`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new manufacturer leads straight into your CRM.
• Slack — get notified when a monitored type or state gets a new or changed manufacturer.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find every US-based trailer manufacturer with a named principal and a phone number, sorted by lead score" and let it run the scraper for you.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
• Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

More scrapers from scrapesage

Build a complete automotive, trade & B2B lead-gen stack:

• US Auto Dealer & Repair Shop Leads — licensed dealers, repair, body, salvage & tow businesses from official state DMV registries.
• ImportYeti Scraper — US importers and their overseas suppliers from customs bill-of-lading data.
• FMCSA Trucking Scraper — US motor carriers & freight brokers with operating authority, insurance & contacts.
• US Customs Broker & Freight Forwarder Leads — CBP customs brokers + FMC freight forwarders / NVOCCs with bonds & contacts.
• AutoScout24 Scraper — European car listings, prices & dealer leads.
• US Business Formation Scraper — newly-registered companies as fresh leads.
• SBA Loan Leads Scraper — small businesses financed under SBA 7(a) & 504.
• USASpending Scraper — federal awards and the companies that win them.

Tips

• Whole supply chain: leave manufacturerTypes empty (or pick several) to pull vehicle makers, equipment makers, importers and alterers in one run.
• Type-targeted pulls are fastest: setting manufacturerTypes filters at the source, so the actor only enriches relevant candidates.
• Contactable leads: set hasContactOnly: true (or hasEmailOnly / hasPhoneOnly) to drop registry stubs and keep records you can actually reach.
• By product: combine vehicleTypes (e.g. Trailer, Motorcycle) or primaryProductContains with usBasedOnly to focus on a niche.
• Deeper pulls: raise maxEnrichments when you want the full score-ranked field or are filtering by a specific state.
• Recurring monitoring: combine Schedules with monitorMode to capture only manufacturers added or changed since the last run.

FAQ

Where does the data come from? From the official NHTSA Product Information Catalog and Vehicle Listing (vPIC) API — specifically the manufacturer registry that companies file under 49 CFR Part 566. It's published by the U.S. National Highway Traffic Safety Administration at vpic.nhtsa.dot.gov.

Does it need an API key or login? No. The vPIC API is public — no key, no login, no browser.

What manufacturers are included? Every company registered with NHTSA as a manufacturer, importer, alterer, intermediate or final-stage manufacturer of motor vehicles or regulated motor-vehicle equipment for the US market — from major OEMs to trailer builders, RV and bus makers, upfitters, tire and child-seat makers, and specialty / low-volume manufacturers.

Does it include e-mails and phone numbers? Yes — when the manufacturer filed them with NHTSA. About 40% carry an e-mail and ~60% a phone; nearly all carry a full address, and ~55% list a named principal. We never fabricate contact data — everything is straight from the federal record.

How fresh is it? vPIC is updated continuously as manufacturers file and amend their registration; each record carries a last-updated date. Run on a Schedule with monitoring mode to capture new registrations and contact changes.

How many manufacturers are there? Roughly 20,000 in the registry. Use the type, vehicle-type, location and contact filters to focus on the segment you sell to.

Can I export to Google Sheets, CSV, or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

Is scraping this data legal? This actor collects publicly available U.S. government data. You're responsible for using it in compliance with applicable laws and NHTSA's terms.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.