# Helium 10 Alternative — Amazon Opportunity Research (`khadinakbar/helium10-alternative`) Actor

Turn a public Amazon keyword search into source-linked product comparison rows with price, ratings, reviews, sponsored status, and transparent opportunity signals.

- **URL**: https://apify.com/khadinakbar/helium10-alternative.md
- **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community)
- **Categories:** E-commerce, MCP servers, Agents
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $120.00 / 1,000 research results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Helium 10 Alternative — Amazon Opportunity Research

Turn one public Amazon.com keyword search into a compact, source-linked comparison set. Each returned product row includes its observed ASIN, title, price, rating, review count, visible sponsored label, position when available, source URL, and collection time. It also includes transparent opportunity signals computed from those observed fields.

### Best fit for this Actor

Use it when you need a repeatable public Amazon listing comparison for one product phrase and want the result as structured JSON. It is useful for an early product-niche review, a competitive snapshot, or a research queue.

Choose Helium 10 when the requested next step needs sales estimates, profit or FBA-fee calculations, keyword search volume or ranking history, listing optimization, Amazon advertising, Seller Central data, or team dashboards. For product-page detail enrichment after this comparison, continue with [Amazon Product Scraper](https://apify.com/khadinakbar/amazon-product-intelligence).

### How this public-listing workflow compares with Helium 10

| Decision point | This Actor | Helium 10 |
| --- | --- | --- |
| Bounded job | Collect a public keyword-search comparison set. | Broader product-research and seller workflow suite. |
| Starting point | One product phrase and storefront. | Product research with additional seller tools. |
| Output | Source-linked JSON listings and explicit scope notes. | Broader research and dashboard workflows. |
| Predictive data | Public-listing comparison signals based on visible listing fields. | Its official product-research page describes sales estimates, FBA fees, demand, and competitor performance. |
| Billing and same-job cost | Pay per event per validated row plus platform usage; a final-build same-job measurement is pending. | Subscription plans; no one-search allocation is assumed. |
| Effective efficiency | A final-build elapsed-time and usable-row measurement is pending. | No equal-workload timing comparison is claimed. |
| Integration and automation | Intended for Apify API and schedule workflows after live verification. | Broader suite and MCP offerings are documented by Helium 10. |
| Best choice | A one-off public-data comparison that can enter an API workflow. | Ongoing seller operations or any predictive/connected-account requirement. |

Helium 10 is a trademark of its owner. This independent Actor is not affiliated, associated, or endorsed by Helium 10.

### From a product phrase to a research shortlist

For `portable blender` on Amazon US, the workflow starts with a small 10-product sample. Then compare public price, rating, review count, sponsored label, and observed position. Treat a `research-further` band as a prompt to inspect the source page and gather independent evidence before a product decision.

The score is deliberately transparent:

- Lower-than-median visible review counts can increase the score.
- Lower visible ratings can increase the score because they may justify qualitative review research.
- Visible sponsored status and first-page position can reduce the score.
- Price is only used as a simple observed comparison band.

The score preserves a public-listing scope: visible price, rating, reviews, sponsorship, and position inform the comparison.

### Quick start

```json
{
  "searchQuery": "portable blender",
  "marketplace": "US",
  "maxResults": 10,
  "includeSponsored": true
}
```

Run through the Apify API after deployment:

```bash
curl "https://api.apify.com/v2/acts/khadinakbar~helium10-alternative/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQuery":"portable blender","marketplace":"US","maxResults":10,"includeSponsored":true}'
```

### What one result contains

| Field | Meaning |
| --- | --- |
| `sourceUrl` | Public Amazon listing URL used as provenance. |
| `reviewCount` | Displayed review count when Amazon provides it. |
| `isSponsored` | Visible sponsored label on the search card. |
| `opportunity` | Transparent, non-predictive comparison signals. |
| `collectedAt` | ISO collection timestamp for freshness. |

```json
{
  "asin": "B0D1ABCD23",
  "title": "Example Portable Blender",
  "sourceUrl": "https://www.amazon.com/dp/B0D1ABCD23",
  "searchQuery": "portable blender",
  "marketplace": "www.amazon.com",
  "position": 12,
  "isSponsored": false,
  "price": 34.99,
  "currency": "$",
  "rating": 4.1,
  "reviewCount": 20,
  "opportunity": {
    "score": 78,
    "band": "research-further",
    "signals": ["review count is below half of this search set median"],
    "limitations": ["not a sales or profit estimate"]
  },
  "collectedAt": "2026-08-31T12:00:00.000Z"
}
```

`position`, `price`, `rating`, and `reviewCount` can be `null` when Amazon does not visibly supply a field. The source URL and collection time make the evidence auditable.

### Data source, pricing and limits

Amazon Merchant results are retrieved through an owner-managed DataForSEO account. ScrapeCreators, SociaVault, and HarvestAPI are deliberately not used here: their configured coverage does not provide the Amazon product-search result fields this workflow requires. No caller credentials or cookies are needed.

Pricing is Pay per event: $0.00005 for Actor start and $0.12 per validated persisted research result, plus Apify platform usage. `maxResults` is the event-charge ceiling for the run; a 10-result run has a maximum $1.20 result-event charge before platform usage. Provider request cost is recorded in `RUN_SUMMARY`; final deployed-build run records and the live Pricing tab are the source of truth for economics.

### Use with an AI agent through Apify MCP

> Compare public Amazon US listings for `portable blender`. Return 10 source-linked rows with price, rating, reviews, sponsored label, source URL, collection time, and the scope notes for the opportunity score. Keep the output in scope and use dataset readback for additional rows.

For a complete request, provide a product phrase and storefront. Sales, fees, keyword volume, Seller Central data, and listing changes belong in tools designed for those workflows. A valid public result set returns `COMPLETE` or `VALID_EMPTY`, while an unavailable source is identified as `UPSTREAM_FAILED`.

### Best results, responsible use, and freshness

Start with a specific buyer phrase and a small result cap, then validate source URLs before making any inventory or launch decision. This Actor reads public Amazon search-listing data and preserves source-route diagnostics. Collection time describes one observed snapshot; repeat scheduled runs create a buyer-owned comparison history. Use output in line with Amazon's terms and applicable law.

### Focused standalone workflow

This Actor is designed as a focused standalone workflow for a single public-listing comparison. Pair it with the Amazon Product Scraper only after the shortlist identifies ASINs that need product-page detail.

### Builder's note

I designed this Actor around observable evidence: public Amazon search cards provide a useful comparison step through visible source URLs, explicit freshness, and clear score scope that an agent can preserve.

### Evidence and verification

The comparison dossier in `ALTERNATIVE_ACTOR_DOSSIER.json` records the bounded scope and current official Helium 10 product/pricing sources. Private cloud validation, charge readback, hosted-MCP evaluation, and a final-build 20-case acceptance matrix are pending before any readiness or price-efficiency claim.

# Actor input Schema

## `searchQuery` (type: `string`):

The product phrase to research on Amazon, for example 'portable blender'. Enter a concrete buyer search phrase rather than a product URL or ASIN. This field is required and is sent only to the selected public Amazon marketplace. It is not a Helium 10 project, Seller Central query, or keyword-tracker import.

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

The supported public storefront for this release. Use US for Amazon.com; prices, availability, and listing positions are collected at run time. This field is a storefront selector rather than a shipping destination or currency conversion setting.

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

The maximum public Amazon listings to include in this comparison run. The default is 20 and the maximum is 100; lower limits keep the reported field competitive set focused. Each persisted product row is a billable research result. This is not a page-count setting or a promise that Amazon exposes that many listings.

## `includeSponsored` (type: `boolean`):

Whether to keep public Amazon listings marked as sponsored in the product comparison. The default is true so the result set shows the visible search landscape. Set false when the next decision needs only observed organic placements. This does not measure advertising spend, targeting, or conversion performance.

## Actor input object example

```json
{
  "searchQuery": "portable blender",
  "marketplace": "US",
  "maxResults": 20,
  "includeSponsored": true
}
```

# Actor output Schema

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

Validated public Amazon listing comparison rows.

## `output` (type: `string`):

Compact terminal outcome.

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

Detailed run diagnostics.

# 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 = {
    "searchQuery": "portable blender",
    "marketplace": "US",
    "maxResults": 20,
    "includeSponsored": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("khadinakbar/helium10-alternative").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 = {
    "searchQuery": "portable blender",
    "marketplace": "US",
    "maxResults": 20,
    "includeSponsored": True,
}

# Run the Actor and wait for it to finish
run = client.actor("khadinakbar/helium10-alternative").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "searchQuery": "portable blender",
  "marketplace": "US",
  "maxResults": 20,
  "includeSponsored": true
}' |
apify call khadinakbar/helium10-alternative --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,khadinakbar/helium10-alternative"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lHjUSSkZAfXjVUab0/builds/fNoPuaD0dygThaxlX/openapi.json