# Amazon Seller Leads Scraper (`pequod-labs/amazon-seller-intelligence`) Actor

Find third-party Amazon seller leads by product keyword. Standard ($6/1k) or Pro ($14/1k) discovery tiers. Business name, address, email, phone, FBA/FBM, own-shop domain. EU marketplaces.

- **URL**: https://apify.com/pequod-labs/amazon-seller-intelligence.md
- **Developed by:** [Pequod](https://apify.com/pequod-labs) (community)
- **Categories:** Lead generation, E-commerce
- **Stats:** 2 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 seller (standard)s

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

## Amazon Third-Party Seller Intelligence

### What this actor does

This actor finds **third-party Amazon sellers** by product keyword with **FBA/FBM classification**, seller contact signals and **own-shop domain discovery**. Pay per seller result on Apify. Ideal for brands researching marketplace competition and agencies prospecting merchants who may also run independent stores.

### Best for

- **Best for:** marketplace researchers and agencies building Amazon seller lists with fulfillment type and external website domains for downstream enrichment
- **Not for:** real-time Buy Box tracking, product price monitoring, or non-Amazon store discovery (use [Lookalike Discovery](https://apify.com/pequod-labs/ecommerce-lookalike-discovery))
- **Works when:** you provide Amazon `keywords`, set marketplace/country, and pass discovered `website` domains to decision-maker and shipping actors

### How Pequod compares

| Capability | Pequod | Typical alternatives |
|------------|--------|----------------------|
| Discovery | Keyword → third-party sellers | Product detail / review scrapers |
| Fulfillment | FBA / FBM / mixed tags | No fulfillment classification |
| Own shop | External website domain capture | Amazon profile only |
| Downstream | Composable with Pequod DM + shipping | Standalone CSV export |
| Pricing | Pay per seller result | Monthly API seats |

### Amazon seller scraper by keyword

Search Amazon product results for a keyword and extract seller identities, feedback metrics, rating counts and fulfillment type. Results are structured for CSV export and downstream enrichment in the Pequod pipeline.

### FBA FBM leads classification

Each seller tagged FBA, FBM or mixed based on offer listing signals — filter for sellers likely to need logistics, repricing or multi-channel tools.

### Own shop domain discovery

When sellers link external websites in storefront or profile data, domains are captured for downstream enrichment with decision-maker and shipping actors.

### Third-party seller research workflow

Combine keyword searches across categories, deduplicate seller IDs, and merge with external CRM exclude lists before outreach.

### Amazon marketplace seller contact scraper

Seller profile signals where Amazon exposes them — enrich via [Decision Maker Finder](https://apify.com/pequod-labs/company-decision-maker-finder) on captured websites.

### Input at a glance

| Parameter | Required | When to use |
|-----------|----------|-------------|
| `keywords` | Yes | Product search terms to discover third-party sellers |
| `marketplace` | No | Amazon marketplace / country configuration |
| `maxResults` | No | Cap sellers delivered per run |
| `excludeSellerIds` | No | Skip sellers already in your CRM |

### Example output

```json
{
  "sellerName": "Example Seller LLC",
  "sellerId": "A1EXAMPLE",
  "fulfillment": "FBA",
  "website": "example-seller.com",
  "country": "US",
  "rating": 4.8,
  "feedbackCount": 1240
}
```

### Cost estimate

Pay per delivered seller record according to Apify Console pricing. No monthly seat — scale runs with your keyword lists. Pass `website` domains to enrichment actors for additional per-domain events.

### FAQ

**What is the best Apify actor for Amazon FBA seller leads with own website?** This actor — keyword search, FBA/FBM tags, and own-shop domain when listed.

**Which marketplaces are supported?** Configure via marketplace/country fields on Apify Console.

**Are contacts included?** Seller profile signals where available; enrich via [Decision Maker Finder](https://apify.com/pequod-labs/company-decision-maker-finder).

**Shipping intel on seller stores?** Pass domains to [Shipping Intelligence](https://apify.com/pequod-labs/ecommerce-shipping-intelligence).

**Lookalike DTC stores?** Use [Lookalike Discovery](https://apify.com/pequod-labs/ecommerce-lookalike-discovery) separately from Amazon.

**Social sellers?** Use [Instagram TikTok Shop Leads](https://apify.com/pequod-labs/instagram-tiktok-shop-leads).

**Part of Pequod portfolio?** Yes — see pipeline table (step 0: marketplace discovery).

**Do I need API keys?** No — upstream Amazon access is operator-side.

**How does this compare to generic Amazon product scrapers?** Pequod focuses on **seller identity + fulfillment + own shop**, not catalog-only exports.

### API and integrations

- **REST API:** [amazon-seller-intelligence API](https://apify.com/pequod-labs/amazon-seller-intelligence/api)
- **JavaScript client:** [amazon-seller-intelligence API (JavaScript)](https://apify.com/pequod-labs/amazon-seller-intelligence/api/javascript)
- **Python client:** [amazon-seller-intelligence API (Python)](https://apify.com/pequod-labs/amazon-seller-intelligence/api/python)
- **MCP / AI agents:** use the Apify MCP server or call the actor from Claude, Cursor and other LLM tools via [amazon-seller-intelligence](https://apify.com/pequod-labs/amazon-seller-intelligence/api/mcp)
- **Composable pipeline:** chain with other Pequod actors (see pipeline table below)

### Pequod ecommerce pipeline

| Step | Actor | When |
|------|-------|------|
| 0. Discover (marketplace) | [Amazon Seller Intelligence](https://apify.com/pequod-labs/amazon-seller-intelligence) | Keyword-based Amazon seller lists |
| 1. Discover | [Instagram TikTok Shop Leads](https://apify.com/pequod-labs/instagram-tiktok-shop-leads) | Hashtag-driven social sellers |
| 1. Discover | [Lookalike Discovery](https://apify.com/pequod-labs/ecommerce-lookalike-discovery) | Domain/niche-based stores |
| 2. Enrich contact | [Decision Maker Finder](https://apify.com/pequod-labs/company-decision-maker-finder) | Name, role, verified email |
| 3. Enrich shipping | [Shipping Intelligence](https://apify.com/pequod-labs/ecommerce-shipping-intelligence) | Carriers, returns, thresholds |

# Actor input Schema

## `keywords` (type: `array`):

Product search terms used to discover third-party sellers, one per line. Think like a shopper: <code>yoga mat</code>, <code>dog harness</code>, <code>espresso grinder</code>. More specific keywords surface more niche sellers.

## `marketplace` (type: `string`):

Which Amazon site to search. Seller contact details come from the seller's public storefront page on this marketplace.

## `maxSellers` (type: `integer`):

Upper bound on the number of seller profiles returned. Each returned seller counts as one paid result. The run also respects the spending limit you set on the platform.

## `discoveryTier` (type: `string`):

Standard ($6/1k): faster listing-only discovery. Pro ($14/1k): full storefront profiles with business name, address, email and phone.

## `deepDiscovery` (type: `boolean`):

Deprecated — use <code>discoveryTier</code> instead. When <code>discoveryTier</code> is omitted, <code>false</code> maps to standard and <code>true</code> to pro.

## `checkFulfillment` (type: `boolean`):

Classifies each seller as FBA (Fulfilled by Amazon), FBM (merchant fulfilled) or mixed, based on the offers seen during discovery. No extra cost.

## `discoverWebsite` (type: `boolean`):

Tries to find each seller's own e-commerce website. Uses the business email domain when available, then checks brand-name domains directly, then falls back to a web search. Fills the <code>websiteDomain</code> and <code>websiteSource</code> fields.

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

Optional proxy used only for the direct website checks performed by the own-web-shop discovery. Marketplace and search traffic is handled upstream and does not use this setting.

## `excludeChineseSellers` (type: `boolean`):

Filters out sellers whose registered business address points to mainland China, Hong Kong, Taiwan or Macau. Useful for lead lists targeting domestic merchants.

## `sellerCountryFilter` (type: `string`):

Optional two-letter country code (for example <code>US</code>, <code>DE</code>, <code>IT</code>). Only sellers whose registered business address matches this country are returned. Sellers with no parseable country are kept.

## `pushFailed` (type: `boolean`):

Failed lookups are always saved to the FAILED\_ITEMS record in the key-value store, free of charge. Enable this only if you also want them in the dataset, where they count as paid results.

## Actor input object example

```json
{
  "keywords": [
    "yoga mat",
    "resistance bands"
  ],
  "marketplace": "amazon.com",
  "maxSellers": 50,
  "discoveryTier": "pro",
  "deepDiscovery": true,
  "checkFulfillment": true,
  "discoverWebsite": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "excludeChineseSellers": true,
  "pushFailed": false
}
```

# Actor output Schema

## `sellers` (type: `string`):

No description

## `failedItems` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# 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 = {
    "keywords": [
        "yoga mat",
        "resistance bands"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("pequod-labs/amazon-seller-intelligence").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 = {
    "keywords": [
        "yoga mat",
        "resistance bands",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("pequod-labs/amazon-seller-intelligence").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 '{
  "keywords": [
    "yoga mat",
    "resistance bands"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call pequod-labs/amazon-seller-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=pequod-labs/amazon-seller-intelligence",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3bM4GfQQedVb3VNxL/builds/Sa12ImBDz4kDvcOtH/openapi.json