# US Vehicle & Equipment Manufacturer Leads Scraper (NHTSA) (`scrapesage/vehicle-manufacturer-leads`) Actor

Scrape every US vehicle & motor-vehicle-equipment manufacturer from the official NHTSA vPIC registry: company, address, contact email, phone, named principal (owner/CEO), manufacturer type, vehicle types & lead score. Filter by type, state & contact. Automotive B2B leads + monitoring.

- **URL**: https://apify.com/scrapesage/vehicle-manufacturer-leads.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$8.00 / 1,000 manufacturer lead records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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](https://vpic.nhtsa.dot.gov/)** 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](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-V/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](https://console.apify.com/sign-up) — 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](https://docs.apify.com/api/v2).

### Input

```json
{
    "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:

```json
{
    "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](https://docs.apify.com/api/v2)** — start runs, fetch datasets, and manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** — official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** — run it weekly/monthly with **monitoring mode** to capture newly-registered manufacturers and updated contacts as fresh leads.
- **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** — trigger downstream actions (CRM import, Slack alert, e-mail sequence) the moment a run finishes.

```js
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](https://docs.apify.com/platform/integrations/make)** — multi-step automation scenarios.
- **[Zapier](https://docs.apify.com/platform/integrations/zapier)** — push new manufacturer leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a monitored type or state gets a new or changed manufacturer.
- **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** — auto-export every run to a spreadsheet.
- **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** — pipe results into your data warehouse.
- **[GitHub](https://docs.apify.com/platform/integrations/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](https://docs.apify.com/platform/integrations/mcp)** — 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](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) — no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/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](https://apify.com/scrapesage/us-auto-dealer-scraper)** — licensed dealers, repair, body, salvage & tow businesses from official state DMV registries.
- **[ImportYeti Scraper](https://apify.com/scrapesage/importyeti-scraper)** — US importers and their overseas suppliers from customs bill-of-lading data.
- **[FMCSA Trucking Scraper](https://apify.com/scrapesage/fmcsa-trucking-scraper)** — US motor carriers & freight brokers with operating authority, insurance & contacts.
- **[US Customs Broker & Freight Forwarder Leads](https://apify.com/scrapesage/customs-broker-forwarder-leads)** — CBP customs brokers + FMC freight forwarders / NVOCCs with bonds & contacts.
- **[AutoScout24 Scraper](https://apify.com/scrapesage/autoscout24-scraper)** — European car listings, prices & dealer leads.
- **[US Business Formation Scraper](https://apify.com/scrapesage/us-business-formation-scraper)** — newly-registered companies as fresh leads.
- **[SBA Loan Leads Scraper](https://apify.com/scrapesage/sba-loan-leads-scraper)** — small businesses financed under SBA 7(a) & 504.
- **[USASpending Scraper](https://apify.com/scrapesage/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](https://docs.apify.com/platform/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](https://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](https://docs.apify.com/platform/schedules) 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](https://docs.apify.com/platform/integrations/drive).

**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](https://help.apify.com/). Feature requests are welcome — this actor is actively maintained.

# Actor input Schema

## `manufacturerTypes` (type: `array`):

Keep only these manufacturer types (filtered server-side at the source for speed). Allowed values: vehicleManufacturer, completedVehicle, incompleteVehicle, finalStage, intermediate, equipmentManufacturer, importer, alterer, replica. Leave empty to scan the whole registry.

## `nameQuery` (type: `string`):

Find manufacturers whose name contains this text (e.g. "freightliner", "trailer", "Tesla"). Uses a fast name lookup that returns full contact detail directly. Leave empty to scan by type / the whole registry.

## `manufacturerIds` (type: `array`):

Look up specific NHTSA vPIC manufacturer IDs directly (e.g. \["955","1084"]). When set, discovery is skipped and only these manufacturers are returned.

## `vehicleTypes` (type: `array`):

Keep only manufacturers that build these vehicle types (case-insensitive contains match, e.g. \["Passenger Car","Truck","Motorcycle","Trailer","Bus","MPV"]). Optional.

## `states` (type: `array`):

Keep only manufacturers in these US states (2-letter codes, e.g. \["CA","MI","TX"]). Optional. Note: state is only known after a manufacturer is enriched, so state filtering scans up to 'Max enrichments' candidates.

## `cities` (type: `array`):

Keep only manufacturers in these cities (case-insensitive exact match). Optional.

## `usBasedOnly` (type: `boolean`):

Drop foreign-based manufacturers (many vPIC manufacturers that sell into the US are based in Japan, Germany, China, etc.).

## `countries` (type: `array`):

Keep only manufacturers based in these countries (case-insensitive contains, e.g. \["United States","Germany"]). Optional.

## `primaryProductContains` (type: `string`):

Keep only manufacturers whose stated primary product contains this text (e.g. "trailer", "tire", "motorcycle"). Optional.

## `hasEmailOnly` (type: `boolean`):

Keep only manufacturers that have a contact e-mail on file.

## `hasPhoneOnly` (type: `boolean`):

Keep only manufacturers that have a contact phone number.

## `hasNamedPrincipalOnly` (type: `boolean`):

Keep only manufacturers with a named principal / officer (owner, president, CEO…) on file.

## `hasContactOnly` (type: `boolean`):

Keep only manufacturers that have at least one of: phone, e-mail or a named principal.

## `updatedWithinDays` (type: `integer`):

Keep only manufacturers whose registry record was updated within the last N days — a freshness / newly-registered signal. Leave empty to disable.

## `minLeadScore` (type: `integer`):

Keep only manufacturers with a lead score at or above this value (0-100).

## `sortBy` (type: `string`):

Order of the output.

## `maxResults` (type: `integer`):

Maximum number of manufacturer records to return.

## `maxEnrichments` (type: `integer`):

Safety cap on how many manufacturer detail lookups are performed per run (controls run time, not your bill). Raise it for deeper score-ranked pulls or when a restrictive state/contact filter needs to scan more candidates. Ignored in name-lookup mode.

## `enrichConcurrency` (type: `integer`):

How many manufacturer detail lookups to fetch in parallel. With proxy rotation on (the default), 12 is fast and reliable; raise for speed or lower if you run without a proxy.

## `deduplicateResults` (type: `boolean`):

Drop duplicate manufacturers that share the same ID / legal name.

## `includeRawFields` (type: `boolean`):

Attach the raw NHTSA vPIC detail record under sourceFields on each manufacturer.

## `monitorMode` (type: `boolean`):

Only return manufacturers that are new or whose contact, principal or address changed since the last run with the same monitor key. Ideal on a Schedule to catch newly-registered manufacturers as fresh leads.

## `monitorKey` (type: `string`):

Namespace for monitoring mode so independent monitors don't collide. Use a distinct key per saved configuration.

## `proxyConfiguration` (type: `object`):

Recommended ON (default). NHTSA vPIC rate-limits per IP, so rotating Apify Proxy IPs keeps large runs fast and complete. Datacenter proxy is plenty; turn it off only for tiny runs.

## Actor input object example

```json
{
  "manufacturerTypes": [],
  "usBasedOnly": false,
  "hasEmailOnly": false,
  "hasPhoneOnly": false,
  "hasNamedPrincipalOnly": false,
  "hasContactOnly": false,
  "sortBy": "leadScore",
  "maxResults": 1000,
  "maxEnrichments": 3000,
  "enrichConcurrency": 12,
  "deduplicateResults": true,
  "includeRawFields": true,
  "monitorMode": false,
  "monitorKey": "default",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped manufacturer lead records in the default dataset, each with firmographics, contacts, a named principal, product/type detail and a lead score.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "manufacturerTypes": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/vehicle-manufacturer-leads").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "manufacturerTypes": [] }

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/vehicle-manufacturer-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "manufacturerTypes": []
}' |
apify call scrapesage/vehicle-manufacturer-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=scrapesage/vehicle-manufacturer-leads",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/G9ZyvjRGX4xPV0CUp/builds/kJjctH02Fvr3yluRc/openapi.json