Rainforest API Alternative: Amazon Plus 23 Other Marketplaces and Platforms
A Rainforest API alternative compared fairly: Rainforest's Amazon credit plans vs NeuralVerge's per-result Amazon sources plus 23 marketplaces, over API or MCP.
By the NeuralVerge team · 13 min read · Updated October 2026
▸On this page
A Rainforest API alternative is a different way to get Amazon product data as JSON, and the useful question is what you need beyond Amazon. Rainforest API, from Traject Data, is built around Amazon and sold in monthly credit plans. NeuralVerge prices its Amazon sources per result in points, and the same account reaches 23 other marketplaces and platforms, over REST or by an AI agent through MCP. This post compares the two fairly and shows one real Amazon request and response.
The short version
- —Verdict. If your whole workload is Amazon and you rely on reviews, deals or Buy Box monitoring, a service built around Amazon is a reasonable choice. If Amazon is one of several marketplaces you read, or an agent makes the calls, the NeuralVerge catalog fits better.
- —Who it is for. Teams doing price and ranking monitoring, assortment research or competitor checks across more than one marketplace, in code or through an agent. The e-commerce data guide covers the whole catalog.
- —What it costs. Amazon product search is 1 point per returned result ($1 per 1,000). Product, offers and seller lookups are 5 points ($5 per 1,000). A search that finds nothing is not billed. Plans are on the pricing page.
- —Reference. The Amazon product search source page lists exact fields, request shape and prices.
| Rainforest API | NeuralVerge | |
|---|---|---|
| Scope | Amazon only, many request types | Amazon (5 sources) plus 23 other marketplaces and platforms in 128 e-commerce sources |
| Amazon requests | Product details, reviews, price, seller and store, deals, Buy Box, product search | Search, product, offers, seller, seller products |
| Pricing model | Monthly credit plans | Points per result: $1 per 1,000 search results, $5 per 1,000 lookups |
| Delivery | Response, webhook or cloud storage | Request and response, over REST or MCP |
| Best when | The whole workload is Amazon and needs reviews, deals or Buy Box data | Amazon is one of several marketplaces, or an agent makes the calls |
Rainforest's column comes from its public product page at the time of writing and can change. Check its current terms before you decide.
What Rainforest API offers
Rainforest describes itself as a real-time Amazon product data API. If the job is Amazon and nothing else, a service built around that one marketplace is a reasonable thing to want.
What its public page lists
- —Many Amazon request types. Product details by ASIN, reviews, price, seller and store data, promotional deals, Buy Box monitoring, image and title scraping, and product search.
- —Amazon marketplaces across countries. The page says all major Amazon marketplaces are supported, including the US, UK, Germany, France, Canada and India.
- —Credit-based plans. Monthly plans range from a small hobbyist tier of a few hundred credits to plans in the millions, with a lower price per extra credit at higher tiers, an annual billing option and a free trial. Plans also differ in how many custom zip or postal codes they allow.
- —Delivery options. JSON or CSV output, pulled in the response, pushed by webhook, or written to cloud storage.
Where it wins
It goes deeper on Amazon-specific things such as deals and Buy Box ownership, and it offers push delivery that suits large scheduled collections. NeuralVerge's Amazon sources do not list those request types, so if your use case depends on them, test before planning a move.
What this post could not confirm
The credits each Rainforest request type consumes were not checked, so this post does not turn its plans into a cost per product or per search. That conversion matters most for your own workload; take it from Rainforest's documentation, not from a third-party blog.
NeuralVerge as a Rainforest API alternative
NeuralVerge is a platform with a catalog of data sources, and Amazon is five entries in it. The same account also runs cited AI research and schema-based extraction, so Amazon can be one input among several in a workflow.
The five Amazon sources
Each Amazon source is a separate, single-purpose lookup with a fixed price in points, from the source pages:
| Source | What it returns | Cost |
|---|---|---|
| Amazon product search | Keyword search results: ASIN, title, URL, price, rating, review count, image | 1 point per returned result |
| Amazon product | Product details by ASIN | 5 points per lookup |
| Amazon product offers | Every marketplace offer on a listing: price, condition, seller, delivery | 5 points per lookup |
| Amazon seller | Seller profile with rating over 30, 90 and 365 days | 5 points per lookup |
| Amazon seller products | Products in a seller's storefront | 1 point per returned result |
All of them take a domain parameter and cover 19 Amazon marketplaces. Search-type sources bill by records returned, so a search that finds nothing costs nothing. The product, offers and seller lookups charge only for successful lookups, according to their source pages.
Beyond Amazon
The e-commerce category lists 128 sources across 24 marketplaces and platforms, which is Amazon plus 23 others, including Walmart, eBay, Target, Newegg, AliExpress, Alibaba, Zalando, Rakuten, Vinted, Mercari and OLX. The number 128 counts lookups, not marketplaces: most marketplaces have a search source, a product source, a seller source and sometimes a reviews source. The same pattern holds across the catalog. A search source takes a keyword, a product source takes an identifier, a seller source takes a seller, and each returns records in documented fields. Search sources on Walmart, eBay and Target also cost 1 point per returned result, so a cross-marketplace price check stays one account, one key and one bill.
Where NeuralVerge is narrower
- —Fewer Amazon request types, as far as the public pages show. Reviews, deals and Buy Box monitoring are listed by Rainforest and are not Amazon sources here.
- —Search results are a snapshot. Ranking, sponsored placements and prices move, so a stored result is only as current as the moment you asked.
- —Delivery is request and response. Webhook push and cloud storage delivery are not listed for the Amazon sources, so batch jobs are something you schedule yourself.
REST and MCP
The same Amazon source is reachable two ways. The REST path follows the endpoint name with hyphens; the MCP tool has the same name with underscores and takes the same arguments. The Amazon sources are available over both, with the same points and the same response. Setup for the hosted MCP server is in the MCP server for Claude guide. AI research is REST-only, but every source, including these, works as an MCP tool.
One real request and response
This is the request from the source page, using a placeholder API key. Endpoint details are in the documentation.
curl -X POST https://api.neuralverge.ai/functions/v1/run-amazon-product-search \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "query": "wireless mouse", "max_items": 25, "domain": "amazon.com" }'
The MCP form of the same call, as the source page documents it, is:
{ "tool": "run_amazon_product_search", "arguments": { "query": "wireless mouse", "max_items": 25, "domain": "amazon.com" } }
The body needs a query. max_items caps the number of results, start_page pages further into the results, and domain picks the marketplace, defaulting to amazon.com. The response below is the real captured sample from the source page. It was captured for the query usb cable with max_items set to 2, so it is two results and two points, not the 25 the example request would ask for. It is not shortened.
{
"session_id": "11111111-1111-1111-1111-111111111111",
"kind": "amazon_product_search",
"query": "usb cable",
"domain": "amazon.com",
"max_items": 2,
"start_page": 1,
"partial": false,
"human": "# Amazon product search\n\n- **Search term:** usb cable\n- **Domain:** amazon.com\n- **Starting page:** 1\n- **Max items:** 2\n- **Records returned:** 2\n- **Proxy traffic:** 572.0 KB",
"machine": {
"total_items": 2,
"first_item": {
"id": "B07X6CWM3G",
"title": "6amLifestyle 2 Pack 10ft PS4 Controller Charging Cable,Micro USB Braided Cord Compatible with PlayStation 4 DualShock 4, PS4 Slim/Pro, Xbox One S/X, Android Phones, Kindle, Black & Blue",
"url": "https://www.amazon.com/sspa/click?ie=UTF8&spc=MToyNzg0MjMyMzk4ODUwMDM3OjE3OTA3ODE3MDQ6c3BfYXRmOjMwMDYxOTg2MjUwNDcwMjo6MDo6&url=%2FPS4-Controller-Charging-Cable-Compatible%2Fdp%2FB07X6CWM3G%2Fref%3Dsr_",
"price": "$13.99",
"rating": 4.6,
"review_count": 23645,
"image": "https://m.media-amazon.com/images/I/71G1-QuX2IL._AC_UY218_.jpg"
},
"items": [
{
"id": "B07X6CWM3G",
"title": "6amLifestyle 2 Pack 10ft PS4 Controller Charging Cable,Micro USB Braided Cord Compatible with PlayStation 4 DualShock 4, PS4 Slim/Pro, Xbox One S/X, Android Phones, Kindle, Black & Blue",
"url": "https://www.amazon.com/sspa/click?ie=UTF8&spc=MToyNzg0MjMyMzk4ODUwMDM3OjE3OTA3ODE3MDQ6c3BfYXRmOjMwMDYxOTg2MjUwNDcwMjo6MDo6&url=%2FPS4-Controller-Charging-Cable-Compatible%2Fdp%2FB07X6CWM3G%2Fref%3Dsr_",
"price": "$13.99",
"rating": 4.6,
"review_count": 23645,
"image": "https://m.media-amazon.com/images/I/71G1-QuX2IL._AC_UY218_.jpg"
},
{
"id": "B0DZNBF9NV",
"title": "ULIFTUS USB-B to USB-C Printer Cable 3FT, Gold-Plated USB Type C to Type B Cord for MacBook Pro/Air HP, USB C MIDI Cable for Yamaha Piano DJ Controller Keyboard, 1m Printer Cord to USBC",
"url": "https://www.amazon.com/sspa/click?ie=UTF8&spc=MToyNzg0MjMyMzk4ODUwMDM3OjE3OTA3ODE3MDQ6c3BfYXRmOjMwMDc0ODIxMjk0MzgwMjo6MDo6&url=%2FULIFTUS-Printer-Gold-Plated-Controller-Keyboard%2Fdp%2FB0DZNBF9NV%2Fre",
"price": "$5.99",
"rating": 4.7,
"review_count": 478,
"image": "https://m.media-amazon.com/images/I/71hy5RQ8vOL._AC_UY218_.jpg"
}
],
"proxy_traffic_bytes": 585701
},
"total_points": 2
}
Reading the response
The cost is total_points: 2, one point for each of the two records returned. Every response carries a session_id for tracing the request later, a human summary for reading and a machine object for code. Each result has the same field names every time: id (the ASIN), title, url, price, rating, review_count and image. The price is a string exactly as the page shows it, including the currency symbol.
first_item repeats the first entry of items, which is convenient when an agent only needs the top hit. The url of the first result is a sponsored click-through link rather than a clean product page address. The search runs at request time against what Amazon's search page shows for that query and marketplace, so sponsored and organic placements both appear, and ranking can shift between two requests made minutes apart. The ASIN in id is the stable handle, and it is what you pass to the Amazon product, offers or seller lookups next.
Worked example and migration
Acme Oy checks a competing product
Acme Oy, a fictional Finnish retailer, wants to see how a competing product is priced and ranked on Amazon Germany, then on Amazon.com, then on a couple of other marketplaces. With a single-marketplace service, the Amazon part is one integration and everything else is a separate project. With a catalog, the Amazon part is a call with "domain": "amazon.de", and the rest are calls to other sources on the same account. The results can be compared field by field after a small mapping step.
Moving an existing Rainforest workload
- —List the fields your code reads today and check each against the NeuralVerge source page. Anything missing is a gap to plan for.
- —List the request types you use. If you rely on reviews, deals or Buy Box data, confirm what exists on the other side before you commit.
- —Confirm the Amazon domains you need are among the 19 on the source page.
- —Check location settings. Rainforest's plans mention custom zip codes. Whether location-dependent prices can be handled the same way on NeuralVerge is not stated on the source page, so test it.
- —Run a sample of real keywords and ASINs through both and compare fields, failures and cost.
Cost compared
NeuralVerge, per the source pages. Amazon search is $1 per 1,000 returned results. Amazon product, offers and seller lookups are $5 per 1,000. Plans are listed on the pricing page in points per month. Because the price is per result, a cost estimate is a multiplication: results per query times queries per day times days.
Rainforest, per its public page. Plans are monthly and credit based, with extra credits priced per credit, and the price per extra credit falls as the plan grows. How many credits a given request type uses was not determined, so the two cannot yet be compared on cost per search or per product.
A fair comparison starts from your real monthly workload, for example 2,000 keyword searches at 50 results each plus 10,000 product lookups. On NeuralVerge that is 100,000 search results at 1 point plus 10,000 lookups at 5 points, so 150,000 points. Price the same workload on Rainforest with its own credit table and see which model fits. Steady, high-volume Amazon workloads and bursty, mixed-marketplace ones can come out in opposite directions. One caveat: a miss on a search or lookup is not billed on these sources, but check what an empty result returns on the other side as well.
How to decide
| If this describes you | Lean towards |
|---|---|
| All traffic is Amazon and you depend on reviews, deals or Buy Box monitoring | Rainforest API |
| You want results pushed to a webhook or cloud storage | Rainforest API |
| You read Amazon plus Walmart, eBay, Target or other marketplaces | NeuralVerge |
| You prefer a per-result price with no monthly allowance to size | NeuralVerge |
| An AI agent should choose the lookup itself | NeuralVerge |
Then work through these questions:
- —Which fields and request types do you use today? Reviews, deals and Buy Box data are the likeliest gaps.
- —Which marketplaces and countries? Amazon only, or Amazon plus others?
- —What is your monthly workload, priced both ways? Use each vendor's current terms.
- —How fresh must the data be? Both are described as real time, but run the same queries at the same moment and compare.
- —How will it be called? Scheduled code, a webhook-style push, or an agent tool. Check that the delivery mode you need exists.
- —What does a miss look like? Check what an empty result returns and whether you are billed for it.
Common uses that fit NeuralVerge: price and ranking monitoring by running the same keyword on a schedule, cross-country pricing by pointing one query at several Amazon domains, seller research through a seller's profile and storefront, and agent workflows where a lookup tool answers a pricing question with current data.
Frequently asked questions
Is NeuralVerge a drop-in replacement for Rainforest API?
No. The request and response shapes are different, so moving over means changing the call and the parsing code. NeuralVerge's Amazon sources return search results, product details, offers, seller profiles and seller catalogs as structured JSON. Rainforest lists other request types, such as reviews, deals and Buy Box monitoring, which you should check against your own needs before switching.
How many marketplaces does NeuralVerge cover besides Amazon?
The e-commerce category of the source catalog lists 128 sources spread across 24 marketplaces and platforms, which is Amazon plus 23 others, among them Walmart, eBay, Target, Newegg, AliExpress and Zalando. A source is one lookup, such as a search, a product, a seller or a reviews feed, so one marketplace usually has several. The data sources page lists exactly what is there.
How much does an Amazon search cost on NeuralVerge?
Amazon product search costs 1 point per returned result, which is $1 per 1,000 results, with up to 250 results per request. A search that matches nothing is not billed. Amazon product details, offers and seller lookups cost 5 points each, which is $5 per 1,000, and only successful lookups are charged.
Can an AI agent call the Amazon sources over MCP?
Yes. The Amazon sources are available over REST and as MCP tools on the hosted MCP server. The tool name is the endpoint name with underscores, for example run_amazon_product_search, and the arguments match the REST body. The MCP server for Claude guide covers setup.
Does NeuralVerge cover Amazon marketplaces outside the US?
Yes. The Amazon sources accept a domain parameter and the source pages list 19 supported Amazon marketplaces, including amazon.com, amazon.co.uk and amazon.de. The same query can be pointed at a different country's catalog and pricing.
What should I test before leaving Rainforest API?
Run your real queries and ASINs through both services and compare the fields you actually use, how each handles a country or postal code if you need one, and what each charges for the same workload. Rainforest's own pricing page and terms are the source for its current plans and credit rules.
Related articles
What an ecommerce data api should return, how NeuralVerge's 128 marketplace sources work over REST and MCP, with a real Amazon request, response and point cost.
Build a price monitoring agent that tracks one product across Amazon, Walmart and Target over REST or MCP, with a real JSON response and the cost per check.
Amazon product data for AI agents: look up an ASIN, read every offer, vet a seller, over REST or MCP, with a real JSON response and points per call.
About NeuralVerge
Give your agents structured, cited, real-world data from 300+ sources and the open web — through one API or MCP server.
Data Sources on the NeuralVerge blog.