Reservoir review

Infrastructure, not a destination

Many NFT front ends you have used are reading Reservoir underneath. It aggregates order and sale data across marketplaces and exposes it through a documented API whose figures reconcile to on-chain events — which is the property that matters when you are building a product on someone else's data.

Priced and licensed sensibly

A documented free tier with published rate limits, paid tiers listed, and open-source components that mean a team can leave without rewriting everything. In a sector where data vendors lock customers in as a business model, that combination is unusual enough to be the main reason to choose it.

Its limits

Coverage depends on marketplace integrations, so a venue it has not integrated is invisible to anything built on it. And there is no consumer interface — this is a tool for people shipping software, not for collectors checking a floor price.

Who it suits

Developers building NFT trading into a product, and analysts who want aggregated order data without scraping several marketplaces themselves.

What to verify before building on it

Which marketplaces are integrated for the chains you need, and what the rate limits are on the tier you plan to use. Both are documented, and both decide whether your product has blind spots on day one.

Why the open components matter

Because data vendors in this sector routinely make leaving expensive. Open-source pieces and a documented API mean a migration is work rather than a rewrite.