Cowrie Research

reservoir-primary-sources-2026-04-27

3 min read

Reservoir primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Current docs framing / product scope

  • URL: https://nft.reservoir.tools/reference/overview
  • Key takeaways:
    • The docs describe Reservoir as “an all-in-one endpoint for building NFT applications.”
    • They immediately frame the product around both NFT trading and NFT data, which is an important clue that this is backend infrastructure rather than just an indexer or marketplace frontend.
    • The docs direct developers to a developer dashboard and expose a full API reference plus guides and changelog surface.

2) NFT trading functionality

  • URL: https://nft.reservoir.tools/reference/overview
  • Key takeaways:
    • The docs say developers can buy tokens and accept bids from major marketplaces.
    • They say developers can create their own orderbook, including advanced order types.
    • They also say bids and asks can be cross-posted to other major marketplaces.
    • This makes Reservoir look like liquidity and execution infrastructure for NFT products, not just analytics or metadata tooling.

3) NFT data functionality

  • URL: https://nft.reservoir.tools/reference/overview
  • Key takeaways:
    • The docs advertise granular token price data with flexible querying.
    • They mention real-time collection floor-price and top-bid events.
    • They expose aggregated orders for buys and sells, detailed collection metadata and attributes, ownership data, collection statistics, and historical royalty data.
    • The combination of pricing, execution, eventing, ownership, and metadata makes Reservoir best understood as a combined trading-plus-data control plane for NFT apps.

4) Chain coverage and API lifecycle

  • URL: https://nft.reservoir.tools/reference/overview
  • Key takeaways:
    • The docs say Reservoir supports over 30 EVM chains.
    • They explicitly discuss versioning and say endpoint changes are deployed as new versions to preserve backwards compatibility while customers upgrade.
    • This is a useful operational clue that Reservoir should be cataloged as production application infrastructure, not just an experimental toolkit.

5) GitHub org / open-source implementation surface

  • URL: https://github.com/reservoirprotocol
  • Key takeaways:
    • The GitHub org description says: “Open-source NFT trading infrastructure enabling the next generation of NFT products.”
    • Public repos include reservoir-kit, relayer, indexer-public, and marketplace-v2, which together reveal UI, execution, and indexing layers.
    • Repo descriptions highlight a React package for embedding NFT buying flows, a service for scraping orders from various marketplaces, and an open-source marketplace implementation.
    • This open-source footprint reinforces the categorization as marketplace backend and developer infrastructure.

Whitepaper / technical-doc status

  • No canonical standalone Reservoir whitepaper or litepaper was found in this pass.
  • The strongest source of truth is the API docs plus the GitHub org and repo inventory.
  • In practice, those sources are more informative than a missing whitepaper because they expose the concrete execution, data, and component surfaces developers actually use.

Research notes

  • Best current category for the library: NFT trading infrastructure / NFT data API / marketplace backend infrastructure.
  • Key categorization insight: Reservoir should be treated as a backend liquidity, order, and data layer for NFT applications, not as a simple marketplace brand.
  • Another useful note for future scouting: NFT infra projects with docs covering both marketplace execution and chain-wide event/data surfaces often hide a much richer backend role than the homepage alone suggests.

Graph View