Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ecommerce Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fecommercedataapi.com%2Fmain" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fecommercedataapi.com%2Fmain" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Ecommerce Data API.
Search and research Amazon products by keyword or ASIN
Pull an ASIN's price, BSR, and sales-estimate history
Run keyword research with reverse-ASIN lookups and search-volume trends
Analyze market concentration, demand, and price distributions for a category
Look up global trademark registrations by brand
GET STARTED
Extract text from a product image
Patterns agents use Ecommerce Data API for, with concrete tasks.
★ Agent-driven product research
An AI agent evaluates whether a product is worth selling by pulling its ASIN detail, review counts, and sales-estimate and price history in one research pass. Because the API returns BSR-based sales estimates and historical trends, the agent can judge demand and pricing pressure before a human spends time on the listing.
Fetch an ASIN's detail, review data, and sales-estimate history, then summarize its demand and price trend
Keyword and traffic intelligence
Sellers optimizing listings need the keywords that drive traffic and the products that already rank for them. The API runs keyword research, reverse-ASIN lookups, and search-volume trends, so an agent can build a keyword set for a listing and see the competing ASINs behind each term.
Run keyword research for a seed term and a reverse-ASIN lookup to list the products ranking for it
Market structure analysis
Deciding whether to enter a category needs a view of how concentrated and how priced it is. The market endpoints return seller and brand concentration, demand trends, and price distribution for a category, so an agent can assess competition and typical price points before a go or no-go call.
Pull brand concentration and price distribution for a category and report whether it is crowded
46 endpoints — the ecommerce data api returns amazon marketplace intelligence: product research and asin detail, review data, and price, bsr, and sales-estimate history for a listing.
METHOD
PATH
DESCRIPTION
/v1/amazon/product/research
Research Amazon products
/v1/amazon/asin/detail
Get Amazon product details by ASIN
/v1/amazon/asin/history
Get a product's history
/v1/amazon/review
Get Amazon product reviews
/v1/amazon/keyword-research
Run Amazon keyword research
/v1/amazon/market/research
Run Amazon market research
/v1/global/brand/list
Search global trademarks
/v1/tools/image-text
Extract text from an image
/v1/amazon/product/research
Research Amazon products
/v1/amazon/asin/detail
Get Amazon product details by ASIN
/v1/amazon/asin/history
Get a product's history
/v1/amazon/review
Get Amazon product reviews
/v1/amazon/keyword-research
Run Amazon keyword research
/v1/amazon/market/research
Run Amazon market research
/v1/global/brand/list
Search global trademarks
/v1/tools/image-text
Extract text from an image
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ecommerce Data API by hand means choosing between the X-API-Key header and bearer token and shaping a JSON body for each of its product, keyword, and market endpoints. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
The ASIN and keyword travel in the request body, so a rule bounds which operations your agent may call, such as the product and market research reads. You choose the operations it may call, so the trademark and image tools are not included unless you add them.
Credential isolation
Your Ecommerce Data API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'research an Amazon product' or 'find keywords for a listing', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Ecommerce Data API through Jentic.
What authentication does the Ecommerce Data API use?
The Ecommerce Data API authenticates with an API key, supplied either in the X-API-Key header or as an Authorization bearer token, as declared in its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs.
Can I get an ASIN's sales estimate and price history with this API?
Yes. The API returns BSR-based sales estimates for an ASIN and a history endpoint for its price and rank over time, so an agent can judge demand and pricing pressure for a listing.
What are the rate limits for the Ecommerce Data API?
The OpenAPI spec does not specify rate limits. Check the vendor documentation at ecommercedataapi.com for the current plan limits before running large research batches.
Is there an Ecommerce Data API MCP server?
You do not need an MCP server to give your agent the Ecommerce Data API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent queries Amazon product and market data on demand.
Can I limit what my agent is allowed to do with the Ecommerce Data API?
Yes. The ASIN and keyword travel in the request body, so a rule bounds which operations your agent may call, such as the product and keyword research reads, rather than naming a product, and every call it makes is logged.
How do I research an Amazon product with this API through Jentic?
Search Jentic for an intent like 'research an Amazon product' and it returns the matching operation with its input schema, then your agent calls it with the API key Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Query Amazon product, review, keyword, and market data, pull ASIN sales and price history, search global trademarks, and extract text from product images.
Use for: Research Amazon products for a product niche, Get the detail and reviews for an ASIN, Pull the price and sales-rank history of a product, Find high-volume keywords for a product listing
Not supported: Does not place orders, manage listings, or process payments. Use for reading Amazon product, keyword, market, and trademark data only.
The Ecommerce Data API returns Amazon marketplace intelligence: product research and ASIN detail, review data, and price, BSR, and sales-estimate history for a listing. It covers keyword research with reverse-ASIN lookups and search-volume trends, market research with concentration and price and demand distributions, and global trademark lookups, plus a tool that reads text from a product image. It is a read-oriented data source for sellers and analysts studying the Amazon market.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>