For Agents
Search Amazon for a product's ASIN, read its current offers and price history, and keep it on a watchlist with a target price and drop alerts across eleven Amazon marketplaces.
Use for: Find the ASIN for 'Sony WH-1000XM5' on amazon.com, Get the price history of B09DFCB66S over the last 180 days, I want to be emailed when this product drops below $250, List all tracked products that are cheaper now than when I added them
Not supported: Does not place Amazon orders, manage seller listings, or track retailers other than Amazon. Use for Amazon price lookup, price history, and watchlist alerts only.
The Asin API tracks Amazon product prices on a watchlist that is checked on a schedule, with price history and email alerts. It searches Amazon to find a product's ASIN, reads who sells it and at what price, and returns every recorded price for an ASIN over up to 730 days with the lowest, highest, and average. Tracked products carry a target price, a check interval, and drop alerts, and can be checked on demand. It covers eleven Amazon marketplaces including amazon.com, amazon.co.uk, amazon.de, and amazon.co.jp, and each price check of a tracked product costs one credit.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Asin 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%2Fasin.dev%2Fasin" | 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%2Fasin.dev%2Fasin" | 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 Asin API.
Search Amazon by keywords on a chosen marketplace to find a product's ASIN
Read the current offers for an ASIN, cheapest first, with Amazon's own price and the cheapest new and used offers
Retrieve the price history of any ASIN over a period of up to 730 days, with lowest, highest, and average prices
Track a product by ASIN or Amazon link with a target_price and an interval_minutes check schedule
Change a tracked product's target price, drop alerts, or check interval, or pause its checks
Trigger an immediate price check for a tracked product and wait for the result
Check the account's plan, remaining credits, and how many products it tracks
Patterns agents use Asin API for, with concrete tasks.
★ Shopping agent price watch through Jentic
An AI shopping assistant asked to buy a product at the right price needs live and historical Amazon prices. Through Jentic the agent searches for 'track an Amazon product price', receives the Asin trackProduct operation with its schema, and calls POST /products with the ASIN, a target_price, and the marketplace. Asin then emails the owner when the price reaches the target, and the agent can read GET /products/{id} to report the current state.
Call POST /products with product 'B09DFCB66S', marketplace 'com', and target_price 250, then call GET /products/{id} with the returned id to report the current price
Price history lookup before purchase
Before buying, a shopper wants to know whether today's price is actually low. GET /history returns every price Asin has read for an ASIN on a marketplace over a period set by days (up to 730), oldest first, with the lowest, highest, and average. The call is free and reads no credit, so an agent can compare the current offer against the historical range in one step.
Call GET /history with asin 'B09DFCB66S', marketplace 'com', and days 365, then compare the latest price to the lowest and average values returned
Offer comparison across sellers
A buyer wants to see who sells a product and whether Amazon itself is cheapest. GET /offers returns the offers last read for an ASIN, cheapest first, with Amazon's own price and the cheapest new and used offers, without spending a credit. When no read exists yet, POST /offers reads Amazon for one credit, and a read made in the last 3 hours is returned free.
Call GET /offers with asin 'B09DFCB66S' and marketplace 'co.uk'; if the list is empty, call POST /offers with the same asin and marketplace and report the cheapest new offer
Watchlist triage
Someone tracking many products wants to see only what needs attention. GET /products accepts a filter such as drops, target, out_of_stock, or paused to return the matching watchlist entries with their recent price trend. PATCH /products/{id} then adjusts the target price, the check interval, or pauses checks, and DELETE /products/{id} removes a product and its history.
Call GET /products with filter 'drops' and limit 50, then for each result call PATCH /products/{id} with alert_on_drop true
11 endpoints — the asin api tracks amazon product prices on a watchlist that is checked on a schedule, with price history and email alerts.
METHOD
PATH
DESCRIPTION
/search
Search Amazon to find an ASIN
/history
Price history of any ASIN
/offers
Offers already known for an ASIN
/products
Track a product
/products
List tracked products
/products/{id}
Change alerts and checks
/products/{id}/check
Check the price now
/search
Search Amazon to find an ASIN
/history
Price history of any ASIN
/offers
Offers already known for an ASIN
/products
Track a product
/products
List tracked products
/products/{id}
Change alerts and checks
/products/{id}/check
Check the price now
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Asin by hand means sending your asin_ key as a bearer token, picking the right marketplace code on every call, and polling or waiting on background price checks. Through Jentic you install once, import Asin from the API Directory, store the key once, and your agent calls it.
Permission scoping
Asin puts the tracked product id in the URL path (/products/{id}), so a rule can pin your agent to one tracked product and the operations you pick. You choose the operations it may call, so ones that cost credits or remove data, like POST /products/{id}/check or DELETE /products/{id}, are not included unless you add them.
Credential isolation
Your Asin 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 'track an Amazon product price' or 'get the price history of an ASIN', and Jentic returns the matching Asin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Asin API through Jentic.
What authentication does the Asin API use?
The Asin API authenticates with HTTP bearer auth per its OpenAPI spec: you send a personal API key, which starts with asin_ and is created in your account, as the bearer token in the Authorization header. Through Jentic that key is held by your own Jentic One instance and attached at call time.
What are the rate limits for the Asin API?
The OpenAPI spec states two limits: GET /search is free and limited to 30 searches per hour, and GET /history is free and limited to 600 reads per hour. Price checks are metered by credits instead: each check of a tracked product costs 1 credit, and POST /products/{id}/check runs at most once per 5 minutes.
Can I get the price history of a product I do not track with the Asin API?
Yes. GET /history takes any asin and marketplace and returns every price Asin has read for it, whoever tracks it, over the days you ask for, up to 730. It uses no credit, but an ASIN that nobody has tracked yet comes back with an empty history.
How do I set a price alert through Jentic?
Search Jentic for 'track an Amazon product price', load the trackProduct operation, and call POST /products with the product ASIN or link, the marketplace, and a target_price. Asin emails the owner when the price reaches that amount. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an Asin MCP server?
Yes - the Asin API description says the same key works with its MCP server at /api/mcp. You can also connect Asin directly through Jentic: your agent gets the full 11-endpoint surface without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.
Can I limit what my agent is allowed to do with the Asin API?
Yes. A read-only rule could allow GET /search, GET /history, and GET /products/{id} for one tracked product id, so the agent can look up prices and report on that product but cannot add products, change alerts, or spend credits on checks. Every call it makes is logged.
GET STARTED