Amazon data, organised by the job you need done
Every page here is a working recipe with the operation chain, the request contract, and runnable examples. Start from the job you have, or from the team you sit on.
One key covers every job on this page.
- APIs on one key
- 17 APIs on one key
- supported marketplaces
- 13 supported marketplaces
- solution recipes
- 5 solution recipes
- free units on signup
- 100 free units on signup
Explore Glade's most-used Amazon APIs
By job
The workloads teams actually run against Glade, each with the relevant operation chain and the marketplace context it needs.
- Price monitoringCombine product and offer calls with freshness metadata to build bounded, marketplace-aware monitoring workflows.+ more
- Product researchResolve ASINs and GTINs, inspect product records, variants, offers, reviews, and rank signals through one contract.+ more
- Review intelligenceRetrieve review pages and rating distributions, then apply your own transparent analysis and retention policy.+ more
- Seller intelligenceInspect public seller facts and the offer records that reference them across supported marketplaces.+ more
- AI agentsExpose the same bounded Amazon operations through MCP and the Glade amazon-data Skill with one authorization model.+ more
By team
If you would rather start from who you are than from what you are building.
- The Amazon data API built for AI product teamsSeventeen typed operations across 13 marketplaces, available over MCP and the installable Glade Skill.
- The Amazon data API built for developersOne REST API, one auth header, normalized JSON, and the same contract through GraphQL and MCP.
- Reliable price and availability data for commerce teamsTrack prices, offers, stock, and observation freshness without maintaining marketplace parsers.
- Comparable product evidence for research teamsConnect identifiers, catalog records, variants, reviews, offers, and rank signals through one contract.
- Bounded review data for customer intelligence teamsRetrieve public review pages and rating distributions with explicit limits and safe telemetry.
- Marketplace seller signals for intelligence teamsConnect public seller facts, offer participation, fulfillment, and catalog context without identity inference.
Questions
What can I actually build with an Amazon data API?
The five recipes on this page cover the workflows Glade customers build today: price monitoring, product research, review intelligence, seller intelligence, and bounded tools for AI agents. Each page maps the job to the relevant Glade operations, parameters, and production considerations.
Do I need a different API key for each Amazon marketplace?
No. One Glade key covers all 17 operations across 13 supported marketplaces. Pass the documented marketplace code so currency, locale, Amazon host, and delivery context stay explicit on every request.
Are these separate products with separate pricing?
No. They are the same Glade API described by customer job. A successful normalized operation consumes one unit, while provider retries and failed operations do not silently add usage.
How do I pick between a solution page and an API page?
Start from a solution when you know the outcome you need, and from the API directory when you already know the exact operation. Solution cards link to their operation set, and every detailed solution includes an implementation path.
Can one product combine several of these solutions?
Yes. Production workflows often combine product details, offers, stock, reviews, sellers, categories, deals, and estimates. Shared authentication, response metadata, errors, and normalized contracts keep the downstream integration consistent.
Can AI agents use the same Glade operations?
Yes. REST, GraphQL, MCP tools, and the installable amazon-data Skill resolve through the same 17 bounded operations, validation rules, quotas, and authorization model.
One key, every marketplace, whichever job you picked
100 free units on signup. Start with the workflow you need and keep the same contract as your product grows.