Documentation

Connect RankGenius to your AI assistant over MCP, or call the REST API from your own code. Both expose the same tools across 21 Amazon marketplaces, authenticated with a single API key.

Building an AI agent? Get a free trial key in one unauthenticated request — no signup, no email. See the AI Agent Quickstart, the agent-oriented /llms.txt, or the /openapi.json spec.

Your API key — one key authenticates both the MCP server and the REST API. Present it as Authorization: Bearer <your-api-key>.

<your-api-key>

Find your real key on your Dashboard after you sign up free — keep it secret. Rotate it any time with Regenerate Key.

MCP (for AI clients)

Connect Claude, Cursor, or any MCP-compatible client and ask questions in natural language — the assistant calls the tools for you.

MCP Integration →

REST API (for developers)

Call the tools directly over HTTPS and get a JSON envelope back. Ideal for scripts, dashboards, and back-end integrations.

REST API Reference →

The tools

Tool	What it returns
`keyword_rank` Keyword Rank	Live Amazon organic search results (page rank) for a keyword.
`buybox` Buy Box	Who owns the Buy Box for an ASIN, plus price, stock, and delivery.
`product_page` Product Page	Structured product details parsed from the listing — title, rating, bullets, BSR, images, variations, and more.
`product_reviews` Product Reviews	Customer reviews for an ASIN — paginated, with the star breakdown.
`supported_zips` Supported Zips	The delivery zip / postal codes accepted by the optional zip parameter.

Every tool call counts as one metered request — except a repeat of the same request within the free-repeat window (about an hour) is served from cache and is not charged. You can try any tool in your browser first on the Explore page.

Watches — scheduled tracking

A watch runs any tool on a recurring schedule and records the result as a time series, so you can chart how a metric moves — a keyword’s organic rank, a Buy Box price, an ASIN’s Best Sellers Rank, or a product’s ratings count — over days and weeks.

Create and manage watches in the browser on the Watches page, or programmatically via MCP (create_watch, list_watches, get_watch, update_watch, pause_watch, delete_watch) or the REST endpoint /api/v1/watches.
The schedule is a standard cron expression in UTC (e.g. 0 9 * * * for daily at 09:00).
Each scheduled run counts as one metered request (and is subject to the same free-repeat cache above). Managing watches — create, edit, pause, delete — is free.
Results are retained for retention_days (default 90) and older points roll off.
Pause a watch to stop its runs without losing history, then resume when you want. Over MCP use pause_watch (pass resume=true to un-pause); over REST use either POST {"action":"pause"}/{"action":"resume"} or PATCH {"active": false}/{"active": true}.