Access structured product, keyword, pricing, ranking, review, seller, store, sourcing, and compliance data for ecommerce marketplaces. Use one Nexscope API key through REST API, MCP, or reusable Skills.
: "${NEXSCOPE_API_KEY:?Set NEXSCOPE_API_KEY to your nk- API key}"
curl -X POST \
"https://api.nexscope.ai/api/skill-api/v1/skills/amazon-search/run" \
-H "Authorization: Bearer $NEXSCOPE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"page": 1,
"keyword": "phone case"
}'Explore selected APIs from the 174-API directory for product discovery, keyword intelligence, advertising, reviews, rankings, store research, and sourcing.
Search TikTok e-commerce store leaderboards via Kalodata and query detailed information for specific stores. Supports viewing high-ranking, high-sales TikTok Shop…
Discover trending new products across 16 TikTok Shop regional markets via EchoTik new product ranking data.
Fetch and analyze Amazon product reviews by ASIN, supporting 15 marketplaces (including US) with star rating filtering.
Simulates a real user searching on Amazon's storefront to get real-time keyword ranking and search results page data.
Retrieve detailed Amazon product information by ASIN, including title, images, bullet points, specifications, A+ content, pricing, ratings & reviews, variants, and more.
Google Trends keyword search popularity comparison and trend analysis, supporting global regions and custom time ranges.
Filter Shopify standalone stores by multiple dimensions (store name/domain, country, years since creation, product count, ad count, monthly visits, monthly orders,…
Search and analyze products on the Chinese 1688 wholesale platform (Alibaba domestic B2B market) for sourcing, supplier discovery, and product selection.
Search and filter all 174 ecommerce data APIs by seller task, marketplace, or data source. Open API Docs for schemas, request examples, and technical details.
2 APIs for All tasks
Cards lead to the existing API Docs and online tester.Filter Shopify standalone store products by multiple dimensions (keyword/URL, price, weekly sales, listing date, Facebook ads, competitiveness, supplier…
Filter Shopify standalone stores by multiple dimensions (store name/domain, country, years since creation, product count, ad count, monthly visits, monthly orders,…
Find request parameters, response examples, and integration instructions for each data API.
Use REST API for applications, MCP for AI agents, or Skills for repeatable ecommerce workflows.
Send authenticated HTTP requests and use documented parameters, response fields, examples, and errors in your application or automation.
Explore REST APIsGive a compatible agent the Nexscope tool directory so it can present capabilities, request required inputs, and call the selected MCP tool.
View MCP Tool MapUse a focused Skill to give an external Agent or automation a defined ecommerce task, required inputs, and a repeatable execution path.
Explore Ecommerce SkillsOpen and follow https://www.nexscope.ai/mcp-map to access Nexscope ecommerce data. Use the live directory as the source of truth. For an open-ended request, list every available capability under its category, with each capability’s name and a short description. Then ask the user to choose a capability or describe a goal. Do not request an API key or detailed parameters before a capability is selected. After selection, read that capability’s live request/response schema and exact MCP tool name. If a required input is missing, ask for it and explain what it controls; never invent values or copy documentation examples. If a Nexscope API key is not configured, guide the user to API Access and ask them to add it securely. Never display or repeat the key. Then call the tool through the documented authenticated MCP/JSON-RPC flow and return its structuredContent directly. If the Agent cannot make authenticated MCP/JSON-RPC requests, clearly state the limitation and do not claim the tool was called successfully.Browser-based Amazon research tools provide direct access to Nexscope ecommerce data before API or Agent integration.
Explore related searches, demand signals, and product opportunities from a seed keyword before committing to an integration.
Research Amazon keywords LIVE DATA TOOLBrowse bestseller and new-product rankings by marketplace, category, and subcategory directly in Nexscope.
Explore product rankings LIVE DATA TOOLReview listing content, images, reviews, and pricing from an ASIN before deciding whether API access fits the workflow.
Audit an Amazon listingCreate one API key to access supported ecommerce data through REST API, MCP, or reusable Skills.
Choose a seller task to see matching ecommerce data APIs. One API may support more than one workflow.
What should I sell next?
Opportunity signals and product evidenceView 18 matching APIsIs demand real and growing?
Search, demand and trend evidenceView 155 matching APIsWhat is stopping this listing from winning?
Content gaps and keyword recommendationsView 67 matching APIsWhere is ad spend being wasted?
Campaign, placement and promotion evidenceView 28 matching APIsWhy are competing products winning?
Comparable products, prices and customer evidenceView 122 matching APIsWhat are customers praising or rejecting?
Review themes, sentiment and product gapsView 57 matching APIsWhat changed since the last check?
Current ranking, price and store signalsView 34 matching APIsWhat needs attention in store operations?
Store, product, inventory and order actionsView 43 matching APIsWhere can I source this product?
Supplier, product and procurement dataView 17 matching APIsWhat compliance or infringement risk exists?
Trademark, patent and policy risk evidenceView 33 matching APIsHow should I turn product evidence into content?
Product copy, images and video-ready inputsExplore Creative APIsHow can I prepare commerce data for the next step?
Reusable files, conversions and workflow inputsView 11 matching APIsThe current directory includes Amazon, TikTok Shop, Temu, 1688, Walmart, Shopify, Etsy, Shopee, eBay, Ozon, and cross-platform data sources such as Google Trends. Select a marketplace or source in the directory to see the APIs currently available for it. Open an API card for regional coverage, supported fields, and request requirements.
Filter by the marketplace you need or by a seller task such as product discovery, market-demand validation, listing research, advertising analysis, competitor research, reviews, rankings, store operations, sourcing, or compliance. Each matching card shows the API name, purpose, marketplace logo, and estimated credits per call. Open the card to review its request schema, response fields, examples, and online tester.
Coverage includes product search and detail data, keywords and search demand, rankings, reviews, pricing and sales signals, seller and store research, sourcing, competitor analysis, advertising signals, and selected compliance data. The exact fields and time coverage depend on the API, so the API Docs for the selected capability remain the source of truth.
Nexscope supports three access patterns. REST API is intended for applications and backend automation. MCP lets compatible AI agents discover available tools, request missing inputs, and call the selected capability. Skills package focused ecommerce tasks into reusable Agent or automation workflows. Availability can vary by capability, so confirm the supported access methods in its documentation.
No. One Nexscope API key can authenticate calls across the supported ecommerce data catalog. Keep the key on the server side and do not expose it in browser code or public repositories.
Open an API card to use its documentation and online tester before writing integration code. Selected Amazon browser tools also let you experience keyword research, product rankings, and listing-quality workflows first. Once the result fits your use case, use the documented REST API, MCP tool, or Skill to connect it to your application or Agent.
Credit usage varies by capability. Each catalog card displays an estimate when available, while the API Docs and tester show the selected capability’s current usage information before you run it.
Yes. Copy the MCP setup instruction into a compatible Agent. For an open-ended request, the Agent should first read the tool directory and present the available capabilities under their categories. After you choose a goal or tool, it should read the documented schema, ask for any missing required input, and call the selected MCP tool without inventing example values.
No single freshness rule applies to every source. Search, product, ranking, store, and marketplace-result APIs may return current observations, while keyword, price, sales, or trend capabilities may include historical series or periodic datasets. Check the selected API Docs for its source, update behavior, date parameters, and returned time range.
Confirm the required inputs, supported marketplace or region, response fields, estimated credit usage, and error behavior in the API Docs. Keep the API key on the server side, validate user-provided identifiers and URLs, and test the exact capability with representative inputs before adding it to a production application or Agent workflow.
Use one Nexscope API key to access supported marketplace data through REST API, MCP, or reusable Skills.