Install Jentic One Beta

Connect the Amazon Scraper API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Scraper 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%2Famazonscraperapi.com%2Famazonscraperapi" | sh

Step 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%2Famazonscraperapi.com%2Famazonscraperapi" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Amazon Scraper API.

Fetch structured product data for a single Amazon ASIN as JSON

Retrieve structured Amazon search results for a keyword

Submit asynchronous batch jobs of product and search lookups

Pull product fields such as title, price, and rating across supported marketplaces

Use Cases

Patterns agents use Amazon Scraper API for, with concrete tasks.

GET STARTED

Start building with Amazon Scraper API

Explore with Jentic One

View OpenAPI Document

★ AI agent for product research

A research agent needs clean product facts rather than raw HTML. Through Jentic the agent searches for getting structured Amazon product data, loads the single-product lookup with the credential already injected, and returns a normalized JSON record it can reason over. The agent can run a keyword search first and then enrich the top results with full product detail.

Call GET /api/v1/amazon/search for a keyword, then GET /api/v1/amazon/product for the top ASIN to get full detail

Price and availability monitoring

A monitoring workflow checks the price and availability of a set of ASINs on a schedule and flags changes. The Amazon Scraper API returns structured product fields per ASIN, and its batch endpoint lets the agent submit many ASINs in one asynchronous job rather than looping single calls. Because billing follows successful responses, failed fetches do not inflate cost.

Call POST /api/v1/amazon/batch with a list of ASINs and compare each returned price against the stored baseline

Competitive catalog analysis

A seller's agent compares its listings against competitors for the same keywords. The API returns structured search results for a keyword, which the agent can expand into per-product detail to compare titles, prices, and ratings. This builds a competitive snapshot without parsing marketplace pages by hand.

Call GET /api/v1/amazon/search for a target keyword and summarize the price range across the returned products

Key Endpoints

3 endpoints — the amazon scraper api turns amazon product pages and search results into structured json, returning dozens of fields per product across the marketplaces it supports.

METHOD

PATH

DESCRIPTION

GET

/api/v1/amazon/product

Get structured data for a single Amazon product by ASIN

GET

/api/v1/amazon/search

Get structured Amazon search results for a keyword

POST

/api/v1/amazon/batch

Submit an asynchronous batch of product and search jobs

GET

/api/v1/amazon/product

Get structured data for a single Amazon product by ASIN

GET

/api/v1/amazon/search

Get structured Amazon search results for a keyword

POST

/api/v1/amazon/batch

Submit an asynchronous batch of product and search jobs

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Amazon Scraper API by hand means choosing between its api_key query parameter and a bearer token, handling asynchronous batch polling, and parsing the structured JSON per marketplace yourself. Through Jentic you install once, import the Amazon Scraper API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Amazon Scraper API has three operations: single-product lookup, keyword search, and an asynchronous batch job. You choose the operations your agent may call, so you can allow the product and search reads and leave batch submission out of the allowed set unless you add it.

Credential isolation

Your Amazon Scraper 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 'get Amazon product data' or 'search Amazon for a keyword', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Amazon Scraper API through Jentic.

What authentication does the Amazon Scraper API use?

The Amazon Scraper API accepts an API key either as the api_key query parameter or as a bearer token in the Authorization header, per its OpenAPI spec. Both forms authorize the same operations, so you can use whichever fits your client. Through Jentic the key is injected at call time and never travels in the agent's context.

Can I search Amazon and get structured results?

Yes. Call GET /api/v1/amazon/search with a keyword and the API returns a structured list of matching products as JSON. For full detail on one result, follow up with GET /api/v1/amazon/product using the ASIN.

What are the rate limits for the Amazon Scraper API?

The OpenAPI spec does not define request-rate ceilings. The service bills per successful 2xx response and offers a free monthly tier before paid usage begins, so throughput is governed by your plan rather than a fixed per-second limit. Check the Amazon Scraper API documentation for the quota that applies to your key.

Is there an Amazon Scraper API MCP server?

You don't need an MCP server to give your agent the Amazon Scraper API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls operations such as GET /api/v1/amazon/product on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Amazon Scraper API?

Yes. Write a rule that allows only the single-product and keyword-search reads, so the agent can fetch and search product data but cannot submit large asynchronous batch jobs, and every call it makes is logged. You add the batch operation to the allowed set only when you want it.

How do I get structured Amazon product data through Jentic?

Search Jentic for 'get structured Amazon product data', load the GET /api/v1/amazon/product operation, and run it after your key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Amazon Scraper API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey, bearer3 EndpointsREST

For Agents

Fetch structured Amazon product and search data as JSON by ASIN or keyword, and submit batch jobs for many lookups at once.

Use for: Get structured data for an Amazon product by ASIN, Search Amazon for a keyword and return structured results, Submit a batch of product lookups at once, Retrieve the current price and rating for a product

Not supported: Does not place orders, manage seller inventory, or process payments. Use for retrieving structured Amazon product, search, and review data only.

The Amazon Scraper API turns Amazon product pages and search results into structured JSON, returning dozens of fields per product across the marketplaces it supports. It serves single-product lookups by ASIN, keyword search results, and an asynchronous batch endpoint for submitting many product or search jobs at once. Billing is tied to successful responses, so an agent pays for the data it actually retrieves.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

58%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

43%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

38%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Amazon Scraper API to your agent

Capabilities

Use Cases

Start building with Amazon Scraper API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Amazon Scraper API

Jentic AI Readiness Score

Amazon Scraper API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness