API comparison

Canopy API vs. Rainforest API

Two ways to pull Amazon product data into your app. Here's how pricing, interfaces, and data coverage compare, so you can pick the right one for your stack.

Side by side

Canopy API vs. Rainforest API at a glance

Both are real-time Amazon product data APIs covering products, search, reviews, pricing, deals, and best sellers. The differences are in how you pay for it and how you get the data out.

Canopy APIRainforest API
Free tier100 requests/month, freeNo published free tier — free trial only
Starting price$0.01/request, pay-as-you-go, no monthly minimum$23/month for 500 credits ($0.06/credit overage)
Pricing modelPer-request, volume discounts apply automaticallyTiered credit plans — bigger plans lower the per-credit rate
Credit multipliersNone — every request is a flat rateSome parameters (e.g. variant_prices, import_fees) cost 2–3x credits
InterfacesREST, GraphQL, MCP server, LLM skillsREST (GET requests with query parameters)
Response formatsJSONJSON, CSV, HTML
Data coverageProduct details, search, reviews, pricing & Buy Box, deals, best sellers & categoriesProduct details, search, reviews, pricing & Buy Box, deals, best sellers & categories, seller & reviewer profiles
SetupSign up, generate a key, start making requestsChoose a credit plan, then generate a key

Pricing and features shown as of July 2026, based on each provider's publicly published plans. Confirm current numbers on each provider's site before deciding.

Under the hood

Where the two approaches actually diverge

Rainforest API is built around a single REST endpoint: every request is a GET call with a typequery parameter that tells it which kind of Amazon data to return — product, search, reviews, and so on. It's a familiar, predictable shape, and results can come back as JSON, CSV, or HTML depending on what your pipeline needs.

Canopy API takes a different approach: REST endpoints for request/response simplicity, plus a GraphQL endpoint for pulling several related pieces of product data — say, pricing, images, and reviews — in a single round trip instead of chaining calls. On top of that sits a native MCP server and LLM skills, so an AI agent can query live Amazon data as a tool call without a custom wrapper layer.

The pricing philosophy diverges too. Rainforest bills against a monthly credit plan, with some parameters costing more credits than others. Canopy bills every request at the same flat per-request rate, with volume discounts applied automatically as usage grows — no plan to size upfront, no multiplier to account for.

Why teams switch

Where Canopy API fits best

No plan to pick
Pay per request from the first call. There is no credit tier to size upfront and no monthly floor if usage is light or spiky.
Built for AI agents
A native MCP server and LLM skills sit alongside REST and GraphQL, so agent-based tools can query Amazon data without a custom wrapper.
GraphQL when you want it
Fetch exactly the fields a view needs in one request instead of stitching together multiple REST calls.
Fast to integrate
One API key and a generous free tier get real product data flowing in minutes, with code samples for every endpoint.
Which one fits

Choose based on how you build, not just price

Choose Canopy API if…

  • You want GraphQL alongside REST to fetch nested product data in one request
  • You are building AI agent tooling and want a native MCP server
  • You would rather pay per request than size a credit plan upfront
  • You want a real free tier to prototype before committing to spend

Choose Rainforest API if…

  • You need webhook or destination-based delivery (S3, GCS, Azure) for large scheduled jobs
  • CSV or HTML output is a hard requirement for your pipeline
  • You already have Rainforest-specific tooling built and the switching cost outweighs the savings
  • You need seller or reviewer profile data Canopy does not yet expose
FAQ

Frequently asked questions

Is Canopy API a good Rainforest API alternative?

Yes, especially for teams that want GraphQL alongside REST, native MCP support for AI agents, and pay-as-you-go pricing with no plan to size upfront. Both APIs cover the core Amazon data types — product details, search, reviews, pricing, deals, and best sellers.

Does Canopy API have a free tier?

Yes. Every account gets 100 free requests per month. Past that, usage is billed per request starting at $0.01, with automatic volume discounts as usage grows.

Can I use GraphQL with Rainforest API?

No — Rainforest API is REST-only, using GET requests with query parameters. Canopy API offers both REST and GraphQL, so you can query nested product data in a single request instead of chaining multiple calls.

How does Rainforest API’s credit system work?

Each request consumes credits from a monthly plan, and some parameters cost more than the base rate — options like variant_prices or import_fees can multiply a request’s credit cost by 2–3x. Canopy has no credit multipliers: every request is billed at the same flat per-request rate regardless of which fields you ask for.

Which is cheaper, Canopy API or Rainforest API?

It depends on volume and shape of usage. Canopy charges per request from the first call with no monthly minimum, which tends to be cheaper for lighter or spiky usage. Rainforest’s credit plans get cheaper per unit at higher tiers, so compare current published rates directly against your expected monthly volume.

Does Canopy API support AI agents and MCP?

Yes. Canopy ships a native MCP server and LLM skills in addition to REST and GraphQL, so agent frameworks can query Amazon product data as a tool call without a custom integration layer.

Can I migrate from Rainforest API to Canopy API?

Most integrations map cleanly: Rainforest’s type=product, type=search, type=reviews, and similar query parameters correspond to REST endpoints or GraphQL fields covering the same data. The bigger change is architectural — moving from a single query-param endpoint to either discrete REST routes or a single GraphQL query — not a change in what data is available.

Try Canopy API with 100 free requests

Get an API key and start pulling live Amazon data over REST, GraphQL, or MCP — no plan to pick, pay only for what you use past the free tier.