Install Jentic One Beta

Connect the MerchantWords API to your agent

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

Look up an Amazon keyword's search volume, depth, trend, seasonality, and monthly history for a marketplace

Run a reverse ASIN search listing every keyword a product ranks for, sorted by volume or position

Read all products on page 1 of Amazon search results for a keyword

Discover behaviourally related keywords that share product rankings with a seed, filtered by minVolume

GET STARTED

Start building with MerchantWords API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MerchantWords API for, with concrete tasks.

★ Agent-run Amazon keyword research through Jentic

A seller's agent builds a keyword plan for a new listing. Through Jentic it searches keywords containing the product phrase, pulls volume and seasonality for the top results, and checks which keywords a leading competitor ASIN ranks for. The x-api-key stays in your own Jentic One instance, and the agent can read the account endpoint first to confirm quota before a bulk run.

Call POST /keyword-search with keyword 'yoga mat', country 'us', and sort 'volume-desc', then POST /keyword with keyword 'yoga mat' and country 'us' to read its trend and seasonality

Competitor reverse ASIN analysis

To learn what traffic a rival listing captures, the ranked-keywords endpoint returns every keyword an ASIN ranks for with its position, volume, and trend, paginated and sortable by volume, position, or keyword. Pairing it with the ASIN lookup gives the product details and its top keywords in one view.

Call POST /ranked-keywords with asin 'B0DGHMNQ5Z', country 'us', sort 'volume-desc', and page 1, then return the top 20 keywords with their positions

Search results and related-keyword discovery

The search results endpoint returns all products on page 1 of Amazon search results for a keyword, and related-keyword discovery finds terms whose results share product rankings with the seed, even with no words in common. Together they surface adjacent demand a listing could target that a plain phrase match would miss.

Call POST /serp with keyword 'bluetooth speaker' and country 'us', then POST /related-keywords with the same keyword, minVolume 1000, and limit 25

Bulk keyword volume checks

Agencies auditing many listings check volume at scale. The bulk keyword endpoint returns volume and depth for up to 1000 keywords in one call, and the bulk ASIN endpoint returns product details for many ASINs at once, both scoped to one marketplace by country code.

Call POST /bulk-keywords with the agency's list of client keywords and country 'us', then return the keywords sorted by volume, highest first

Key Endpoints

10 endpoints — the merchantwords api returns amazon search keyword data, asin analytics, and search results intelligence for sellers and agencies.

METHOD

PATH

DESCRIPTION

POST

/keyword

Keyword volume lookup

POST

/ranked-keywords

Reverse ASIN search

POST

/serp

Page-1 search result products

POST

/keyword-search

Keyword search by phrase

POST

/related-keywords

Related keywords by SERP overlap

POST

/bulk-keywords

Bulk keyword lookup

POST

/asin

ASIN product lookup

GET

/account

Account, usage, and plans

POST

/keyword

Keyword volume lookup

POST

/ranked-keywords

Reverse ASIN search

POST

/serp

Page-1 search result products

POST

/keyword-search

Keyword search by phrase

POST

/related-keywords

Related keywords by SERP overlap

POST

/bulk-keywords

Bulk keyword lookup

POST

/asin

ASIN product lookup

GET

/account

Account, usage, and plans

Why Jentic?

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

Setup

Wiring MerchantWords by hand means sending an mw_live_ key in the x-api-key header, passing the right two-letter marketplace code on every POST, paging reverse ASIN results, and watching plan quota before bulk calls. Through Jentic you install once, import MerchantWords from the API Directory, store the key once, and your agent calls it.

Permission scoping

MerchantWords sends the keyword, ASIN, and country in the request body rather than the URL path, so rules bound which operations your agent may call, not which keyword or ASIN it looks up. You choose the operations it may call, so quota-heavy bulk keyword and bulk ASIN lookups are not included unless you add them.

Credential isolation

Your MerchantWords 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 'find keywords an ASIN ranks for' or 'get Amazon search volume', and Jentic returns the matching MerchantWords operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MerchantWords API through Jentic.

What authentication does the MerchantWords API use?

Per its OpenAPI spec, the MerchantWords API uses an API key starting with mw_live_ sent in the x-api-key header on every request. A public read-only sample key returns real data for a fixed set of demo keywords and ASINs, and a free signup gives a key that queries any keyword or ASIN. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I find every keyword an ASIN ranks for with the MerchantWords API?

Yes. POST /ranked-keywords with an asin and country returns all keywords the product ranks for with position, volume, and trend. Results are paginated with page, and sort accepts values such as volume-desc or position-asc.

What are the rate limits for the MerchantWords API?

The OpenAPI spec does not publish fixed numbers; limits depend on your plan. GET /account returns your current plan, live rate-limit and bulk-quota usage, and the full list of plans with their limits. See https://www.merchantwords.com/api for plan details.

Is there a MerchantWords MCP server?

You don't need an MCP server to give your agent MerchantWords. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the keyword and ASIN operations it needs on demand without loading another server's tool definitions into its context.

How do I look up Amazon keyword volume through Jentic?

Search Jentic for 'get Amazon search volume for a keyword', load the POST /keyword operation, and execute it with keyword and an optional two-letter country code. The response carries search volume, depth, trend, seasonality, and monthly history. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only POST /keyword and POST /keyword-search, so the agent can research single keywords but cannot run bulk lookups that draw down your bulk quota. Every call it makes is logged, so you can see exactly which keywords it queried.

MerchantWords API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo SemapiKey10 EndpointsREST

For Agents

Look up Amazon keyword volume, trend, and seasonality, find every keyword an ASIN ranks for, read page-1 search results for a keyword, discover related keywords by search-results overlap, and run bulk keyword or ASIN lookups per marketplace.

Use for: What is the monthly Amazon search volume for yoga mat in the US, Find all keywords this competitor ASIN ranks for, Show me the products on page 1 of Amazon for bluetooth speaker, Search for keywords containing standing desk sorted by volume

Not supported: Does not manage Amazon listings, place ads, or report a seller's own sales and orders. Use for Amazon keyword, ASIN ranking, and search results research only.

The MerchantWords API returns Amazon search keyword data, ASIN analytics, and search results intelligence for sellers and agencies. It reports a keyword's search volume, depth, trend, seasonality, and monthly history, runs reverse ASIN searches that list every keyword a product ranks for with its position, and returns all products on page 1 of Amazon search results for a keyword. Related-keyword discovery finds terms that share product rankings with a seed even when they share no words, and bulk lookups handle up to 1000 keywords in one call, with a two-letter country code selecting the Amazon marketplace.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

100%

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: B-Signals: 4

25%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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: D-Signals: 4

23%

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.

48%

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: C-Signals: 1

50%

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: ASignals: 1

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MerchantWords API to your agent

Capabilities

Start building with MerchantWords API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MerchantWords API

Jentic AI Readiness Score

MerchantWords 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