Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-keyword-expansion

ecommerce.amazon-keyword-expansion

Verified

Nexscope keyword expansion tool that expands a seed keyword into a list of related keywords with search volume, trends, PPC bids, ranking difficulty, and other metrics, covering 10 Amazon marketplaces including US, UK, DE, JP, etc. Trigger when the user mentions keyword expansion, keyword mining, long-tail keyword mining, related keywords, keyword suggestions, keyword discovery, PPC bid research, keyword competition, keyword discovery, Nexscope keywords, keyword expansion, keyword discovery, keyword scout, related keywords, long-tail keywords, keyword suggestions, PPC bid research, keyword competition, seed keyword expansion, keyword mining. Even if the user does not explicitly mention "Nexscope", if their need involves finding more related keywords and their search volume, competition, and other metrics starting from a seed keyword, this skill should also be triggered.

FileKindSize
SKILL.mdskill md11.1 KB
manifest.jsonconfig273 B
references/api.mdmarkdown8.8 KB
scripts/amazon_keyword_expansion.pyscript6.6 KB

references/api.md

View on GitHub
# Nexscope Keyword Expansion by Keyword API Reference

## API Specification

- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/tool-jungle-scout/keywords/by-keyword`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, api_key is read from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow the **## Resolving Authentication and Credits Issues** section in SKILL.md)

## Request Parameters

POST Body (JSON):

### Required Parameters

| Parameter | Type | Required | Description |
|------|------|------|------|
| marketplace | string | Yes | Target marketplace code. Options: `us`, `uk`, `de`, `in`, `ca`, `fr`, `it`, `es`, `mx`, `jp`. Default `us` |
| searchTerms | string | Yes | Seed keyword (single keyword string) |

### Optional Parameters -- Result Control

| Parameter | Type | Required | Description |
|------|------|------|------|
| needCount | int | No | Total number of results returned |
| sort | string | No | Sort field, default `-monthly_search_volume_exact` (exact search volume descending) |

### Optional Parameters -- Search Volume Filter

| Parameter | Type | Required | Description |
|------|------|------|------|
| minMonthlySearchVolumeExact | int | No | Minimum exact search volume |
| maxMonthlySearchVolumeExact | int | No | Maximum exact search volume |
| minMonthlySearchVolumeBroad | int | No | Minimum broad search volume |
| maxMonthlySearchVolumeBroad | int | No | Maximum broad search volume |

### Optional Parameters -- Other Filters

| Parameter | Type | Required | Description |
|------|------|------|------|
| minWordCount | int | No | Minimum word count for keywords (for filtering long-tail keywords) |
| maxWordCount | int | No | Maximum word count for keywords |
| minOrganicProductCount | int | No | Minimum organic product count |
| maxOrganicProductCount | int | No | Maximum organic product count |

### sort Options

| Value | Description |
|----|------|
| name / -name | Keyword name ascending/descending |
| dominant_category / -dominant_category | Dominant category ascending/descending |
| monthly_trend / -monthly_trend | Monthly trend ascending/descending |
| quarterly_trend / -quarterly_trend | Quarterly trend ascending/descending |
| monthly_search_volume_exact / -monthly_search_volume_exact | Exact search volume ascending/descending (default descending) |
| monthly_search_volume_broad / -monthly_search_volume_broad | Broad search volume ascending/descending |
| recommended_promotions / -recommended_promotions | Recommended promotions ascending/descending |
| sp_brand_ad_bid / -sp_brand_ad_bid | Brand ad bid ascending/descending |
| ppc_bid_broad / -ppc_bid_broad | PPC broad bid ascending/descending |
| ppc_bid_exact / -ppc_bid_exact | PPC exact bid ascending/descending |
| ease_of_ranking_score / -ease_of_ranking_score | Ease of ranking score ascending/descending |
| relevancy_score / -relevancy_score | Relevancy score ascending/descending |
| organic_product_count / -organic_product_count | Organic product count ascending/descending |

### Site Mapping

| Site | marketplace value |
|------|---------------|
| United States | us |
| United Kingdom | uk |
| Germany | de |
| India | in |
| Canada | ca |
| France | fr |
| Italy | it |
| Spain | es |
| Mexico | mx |
| Japan | jp |

## Nexscope response envelope

These research endpoints return a platform object with numeric `code`, nullable `msg`, and business `data`. Only outer `code: 0` means success; `200`, string codes, missing codes, and HTTP 200 alone do not. A nonzero code is a platform error: show `msg` and do not interpret the payload as a successful result.

`msg` preserves the upstream message when available; Chinese messages are translated to English by Nexscope. A successful response without a message has `msg: null`. Do not infer success or retry behavior from the message text. On both success and failure, the direct fields `code`, `errcode`, `errorCode`, `msg`, `errmsg`, `message`, and `errorMsg` are removed from public `data`. Read the message only from outer `msg`; deeper business fields are preserved, including nested `code` and `status`.

Business field tables and abbreviated business examples below describe `data`, unless explicitly labeled as a complete platform response. For example, a business `products` field is at HTTP `data.products`, and a business `data` array is at HTTP `data.data`. The research endpoints already had this outer envelope; no additional wrapper is added.

```json
{"code":0,"msg":null,"data":{}}
```

Metadata includes string `ts` (epoch milliseconds), string `cost` (elapsed milliseconds, not credits), `time`, and nullable `traceId`. Handle network/HTTP failures before the platform code; gateway failures may not be platform JSON. Keep the existing billing-header guidance separate from elapsed time.

## Response Structure

| Field | Type | Description |
|------|------|------|
| costToken | integer | Tokens consumed |
| keywordInfoList | array | Keyword information list |

### Each Object in keywordInfoList

| Field | Type | Description |
|------|------|------|
| name | string | Keyword name |
| country | string | Marketplace code |
| monthlySearchVolumeExact | integer | Monthly average exact match search volume |
| monthlySearchVolumeBroad | integer | Monthly average broad match search volume |
| monthlyTrend | number | Monthly search volume change percentage |
| quarterlyTrend | number | Quarterly search volume change percentage |
| dominantCategory | string | Category with the highest share in search results |
| relevancyScore | integer | Relevance score to the seed keyword |
| easeOfRankingScore | integer | Ease of ranking score (higher means easier to rank) |
| organicProductCount | integer | Number of organic ranking products |
| sponsoredProductCount | integer | Number of sponsored products |
| ppcBidExact | number | Exact match PPC suggested bid (USD) |
| ppcBidBroad | number | Broad match PPC suggested bid (USD) |
| spBrandAdBid | number | Sponsored Brand ad suggested bid (USD) |
| recommendedPromotions | integer | Number of recommended promotion giveaways |

## Error Codes

HTTP 200 does not prove business success. Read only the numeric outer platform `code`: `0` succeeds and any other value fails. Show outer `msg`; never test removed provider codes or nested business `code` as the platform status. Authentication, permissions, balance, and validation failures may be platform errors even with HTTP 200; also handle non-2xx HTTP and non-JSON responses.

### Recovery guidance

| Condition | Action |
|---|---|
| Authentication failed | HTTP 401 or authorized error: follow the **## Resolving Authentication and Credits Issues** section in SKILL.md. |
| Insufficient credits/balance | HTTP 402: follow the **## Resolving Authentication and Credits Issues** section in SKILL.md. |

## curl Example

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/tool-jungle-scout/keywords/by-keyword \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"marketplace": "us", "searchTerms": "yoga mat", "needCount": 20}'
```

## Response Example

```json
{
  "costToken": 1,
  "keywordInfoList": [
    {
      "name": "yoga mat thick",
      "country": "us",
      "monthlySearchVolumeExact": 45000,
      "monthlySearchVolumeBroad": 120000,
      "monthlyTrend": 15.3,
      "quarterlyTrend": -5.2,
      "dominantCategory": "Sports & Outdoors",
      "relevancyScore": 856,
      "easeOfRankingScore": 3,
      "organicProductCount": 342,
      "sponsoredProductCount": 28,
      "ppcBidExact": 1.25,
      "ppcBidBroad": 0.89,
      "spBrandAdBid": 2.50,
      "recommendedPromotions": 150
    },
    {
      "name": "yoga mat non slip",
      "country": "us",
      "monthlySearchVolumeExact": 38000,
      "monthlySearchVolumeBroad": 95000,
      "monthlyTrend": 8.1,
      "quarterlyTrend": 12.4,
      "dominantCategory": "Sports & Outdoors",
      "relevancyScore": 920,
      "easeOfRankingScore": 2,
      "organicProductCount": 510,
      "sponsoredProductCount": 35,
      "ppcBidExact": 1.58,
      "ppcBidBroad": 1.12,
      "spBrandAdBid": 3.10,
      "recommendedPromotions": 200
    }
  ]
}
```

---

## API Key request rate and retries

All API Keys of one Nexscope user share the public API execution request-rate allowance, measured in any rolling 1-second window. The allowed RPS depends on that user's entitlements; it is not a universal 1 RPS. One Skill operation may issue multiple public API requests, each of which uses the allowance.

HTTP 429 with Nexscope outer code `13012` means request-rate exhaustion: honor the response's `Retry-After`. Outer code `13013` means concurrent-request exhaustion, not rate exhaustion; honor `Retry-After` when supplied. Check the HTTP status and outer JSON code separately. Do not automatically replay writes or requests with uncertain outcomes; first reconcile the operation's state.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall