Reservoir

• Name: Reservoir
• URL: https://reservoir.tools/
• Category: NFT trading infrastructure / NFT data API / marketplace backend infrastructure
• Tags: ethereum-ecosystem
• Summary: Reservoir at the project layer is the NFT trading-and-data stack inside a broader Reservoir company shell that also now matters separately through Relay. The useful product cut here is still the NFT-specific surface developers integrate directly: aggregated marketplace execution, orderbook creation and cross-posting, token and collection data APIs, events, versioned endpoints, and marketplace-building components. The broader operator boundary lives one layer up in reservoir, which is the cleaner place to reason about dashboard authority, API-key issuance, support, versioning policy, and the shared vendor shell across Reservoir and Relay.
• What it does:
  • Provides APIs for NFT data such as prices, metadata, ownership, collection statistics, and real-time floor / top-bid events
  • Lets developers buy tokens, accept bids, create their own orderbooks, and cross-post bids and asks to major marketplaces
  • Exposes open-source infrastructure and developer tooling through public repos including UI kits, relayers, indexers, and marketplace examples
  • Supports multi-chain NFT application development across a broad set of EVM chains
  • Maintains versioned APIs to preserve backwards compatibility as endpoints evolve
• Key claims:
  • The API overview says Reservoir is an “all-in-one endpoint for building NFT applications”
  • The docs say developers can buy tokens and accept bids from major marketplaces, create their own orderbook with advanced order types, and cross-post orders to other major marketplaces
  • The docs say Reservoir supports over 30 EVM chains
  • The docs emphasize granular token price data, collection events, ownership and stats data, royalty data, and aggregated order data for execution
  • The GitHub org describes Reservoir as “Open-source NFT trading infrastructure enabling the next generation of NFT products” and exposes repos for ReservoirKit, a relayer, public indexer code, and open-source marketplace implementations
• Whitepaper: No canonical standalone Reservoir whitepaper or litepaper was surfaced in this pass. The strongest primary sources were the official API docs and the Reservoir GitHub organization; see ../whitepapers/reservoir-primary-sources-2026-04-27.md.
• Sources:
  • https://reservoir.tools/
  • https://nft.reservoir.tools/reference/overview
  • https://github.com/reservoirprotocol

Internal linkages

• Company boundary above the product surface: reservoir.
• Sibling product note inside the same broader operator shell: relay.
• Keep this note on NFT market/data mechanics rather than on the whole Reservoir company perimeter.

Project / company boundary

• Keep this note on the NFT-specific product surface: order ingestion, marketplace cross-posting, NFT data APIs, events, UI kits, and marketplace backend tooling.
• Use reservoir when the sharper question is who controls dashboard accounts, API keys, rate limits, webhook visibility, support workflow, or the broader multi-product vendor relationship across Reservoir and Relay.
• That split matters because the NFT backend is only one part of the dependency. The surrounding operational shell is bigger than this product note.

Control surface

• At the project layer, leverage sits in order aggregation, cross-posting behavior, metadata and event availability, supported-chain coverage, and how much an NFT product outsources market and data truth to Reservoir’s APIs.

• The wider vendor control surface sits one layer up in reservoir.

• Treat Reservoir here as NFT market-and-data infrastructure, not as the whole company.

• Last reviewed: 2026-08-11 UTC