SuperAPI AI Directory

linkfox-jiimore-get-niche-info

Data & analytics

View repository

Updated 10-15 09:06

About this skill

Jiimore Niche Market Info

This skill guides you on how to query and analyze Amazon niche market data via the Jiimore data service, helping Amazon sellers gain deep insights into specific niche markets including competition, pricing, reviews, and growth trends.

How to call

  • API endpoint:POST /jiimore/getNicheInfo(For full parameters/responses/error codes, see references/api.md)
  • Python script:python scripts/jiimore_get_niche_info.py '<JSON 参数>' [--inline]
  • Cost constraints: This tool consumes compute; by default, the same parameter combination is called only once per session, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the zip code in repeated probing; if further retrieval is needed, first explain to the user that it will incur additional consumption.

Output strategy (default script behavior):

  • Alwayswrite the full response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-jiimore-get-niche-info-<timestamp>.json(<cwd> is the working directory when the script runs, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, and if the current directory is not writable, report an error)
  • Response body ≤ 8 KB: after saving to disk, print the full JSON to stdout
  • Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
  • Add --inline to force full printing to stdout (also saved to disk)

Data reading suggestions: First look at the summary to determine whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting the entire JSON into the context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

  • API Key not configured: The environment variable is not configured LINKFOX_AGENT_API_KEY, and LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • Response indicates insufficient compute or balance: The message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

Core Concepts

A niche market in Jiimore represents a fine-grained product segment on Amazon. Each niche is identified by a unique nicheId. This tool retrieves comprehensive market intelligence for a single niche at a time, covering:

  • Market overview: niche title, demand score, product count, brand count, selling partner count
  • Pricing: average price, minimum price, maximum price
  • Search & conversion: weekly/quarterly search volume, search volume growth, search conversion rate, click-to-sale conversion rate, units sold
  • Competition concentration: top 5 / top 20 product and brand click share (current, 90-day, 360-day snapshots)
  • Product launches: new products launched, successful launches across 90-day / 180-day / 360-day windows
  • Inventory health: average out-of-stock rate over time
  • Seller maturity: average brand age, average selling partner age
  • Review insights: average review rating, average review count, positive and negative customer review insights
  • Advertising: ACOS (advertising cost of sales), sponsored products percentage
  • Profitability: profit margin > 50% SKU ratio, break-even ratio, return rate

Supported marketplaces: US (United States), JP (Japan), DE (Germany). Default is US.

Parameter Guide

Parameter Type Required Description
nicheId string Yes The niche market ID to query. Maximum 1000 characters. Only one ID per request.
countryCode string No Marketplace code. Allowed values: US, JP, DE. Defaults to US.

How to Use Parameters

  1. nicheId is mandatory: The user must provide or you must identify the niche market ID. This is a string identifier for a specific Amazon niche segment.
  2. countryCode defaults to US: Only specify a different value when the user explicitly mentions Japan (JP) or Germany (DE).
  3. Single ID per call: This tool only supports one niche ID per request. If the user wants to compare multiple niches, make separate calls.

Usage Examples

1. Basic niche market lookup (US) Query niche market data for a given niche ID in the US marketplace:

nicheId: "12345678"
countryCode: "US"

2. Query a niche in the Japan marketplace

nicheId: "87654321"
countryCode: "JP"

3. Query a niche in the Germany marketplace

nicheId: "11223344"
countryCode: "DE"

Analysis Guidance

When presenting results, organize the rich data into logical sections for the user:

Market Overview

  • Niche title (English and Chinese translation if available)
  • Demand score, product count, brand count, selling partner count
  • Reference ASIN image (if available)

Pricing & Profitability

  • Average price, min price, max price
  • Profit margin > 50% SKU ratio, break-even ratio, return rate
  • ACOS

Search & Demand Trends

  • Weekly and quarterly search volume and growth rates
  • Search conversion rate, click conversion rate
  • Units sold (weekly/quarterly)

Competition Landscape

  • Top 5 and top 20 product/brand click share (current vs. 90-day vs. 360-day)
  • Brand count trends, selling partner count trends
  • Sponsored products percentage over time

Product Launch Activity

  • New products launched and successful launches across time windows
  • Launch success rate (semiannual)

Review & Customer Insights

  • Average review rating and count trends
  • Positive and negative customer review insights
  • Product star rating impact

Inventory & Operations

  • Average out-of-stock rate trends

Display Rules

  1. Present data clearly: Show query results in well-structured tables or grouped sections without subjective business advice unless specifically requested.
  2. Trend comparison: When the response includes current, 90-day-ago, and 360-day-ago data points, present them side-by-side so users can easily spot trends.
  3. Percentage formatting: Display share and rate values as percentages (e.g., 0.35 as 35.0%).
  4. Review insights: If positive/negative customer review insights are present, list them as bullet points.
  5. Image display: If referenceAsinImageUrl is present, display or link to the niche reference image.
  6. Error handling: When a query fails, explain the reason based on the response and suggest checking the niche ID or country code.

Important Limitations

  • Single ID only: Only one niche ID can be queried per request. Batch queries are not supported.
  • Three marketplaces: Only US, JP, and DE are supported.
  • Niche ID required: The user must supply the niche ID; this tool cannot search for niches by keyword or category.

User Expression & Scenario Quick Reference

Applicable -- Queries about a specific Amazon niche market:

User Says Scenario
"Look up this niche market", "niche ID info" Basic niche lookup
"How competitive is this niche", "brand concentration" Competition analysis
"What's the average price in this niche" Pricing intelligence
"Search volume for this niche", "demand trends" Search & demand analysis
"How many new products launched", "launch success rate" Product launch tracking
"Review rating in this niche", "buyer feedback insights" Review analysis
"Out-of-stock rate", "inventory health" Inventory analysis
"Is this niche worth entering", "niche opportunity" Comprehensive niche evaluation

Not applicable -- Needs beyond niche market lookup:

  • Searching for niches by keyword or category (this tool requires a known niche ID)
  • Individual ASIN-level product analysis
  • ABA search term data (use the ABA Data Explorer instead)
  • Advertising campaign management or PPC optimization
  • Listing copywriting or review management

Compute consumption rules

Consumes 9 compute.

Users will pay fees due to compute consumption. Please fully assess: when this skill needs to be called frequently, or the user's expectation of compute consumption is insufficient, be sure to remind the user and let the user decide whether to continue.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.


For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.