Reservoir

• Name: Reservoir
• URL: https://reservoir.tools/
• Category: multichain execution and NFT-market infrastructure company / routing-and-data middleware operator / developer-dashboard control plane
• Tags: ethereum-ecosystem bitcoin-ecosystem solana-ecosystem
• Summary: Reservoir belongs in companies/ because the durable dependency is not only one NFT API or one cross-chain product. The named operator sits above both the Reservoir NFT stack and the newer Relay stack, and the practical control surface lives in company-run dashboards, API-key issuance, rate limits, request history, webhook configuration, route and indexer behavior, and the default packaging of execution or market-data workflow. The useful question is not just what endpoints exist? but which organization controls the easiest production path into order ingestion, route execution, lifecycle truth, and developer support across this product family?
• What it does:
  • Operates Reservoir’s NFT trading and data infrastructure, including aggregated order and metadata APIs, marketplace cross-posting, and developer-facing dashboard access
  • Operates Relay’s app, API, and protocol-facing product shell for cross-chain swaps, bridging, call execution, deposit-address flows, and lifecycle visibility
  • Issues and revokes API keys, applies rate limits, exposes request history, and configures webhook-driven operational workflow through company-run dashboards
  • Maintains open-source implementation and integration surfaces across relayers, vaults, SDKs, order-ingestion components, marketplace kits, and related developer tooling
  • Packages chain support, versioning, support, and migration guidance around these products so downstream teams inherit one vendor-shaped path rather than stitching the stack together themselves
• Key claims:
  • Reservoir’s NFT API overview describes the product as an “all-in-one endpoint for building NFT applications,” directs users to create an account in the Developer Dashboard, and frames the stack around buying tokens, accepting bids, creating orderbooks, and cross-posting to major marketplaces
  • The same docs say Reservoir supports over 30 EVM chains and preserves backwards compatibility by shipping endpoint changes as new versions, which is a useful signal that this is production application infrastructure with company-managed lifecycle policy
  • Relay’s What is Relay? page describes a three-layer stack — Relay App, Relay API, and Relay Protocol — which is strong evidence that the practical product boundary is a company-packaged operating shell rather than one narrow protocol primitive
  • Relay’s API-key docs say keys are created, rotated, and revoked in the Relay Dashboard, where integrators also inspect request history, configure webhooks, and request elevated rate limits through support, making dashboard authority and credential workflow first-class control surfaces
  • Relay’s docs and llms.txt market a broad execution and payments surface spanning bridging, swaps, call execution, deposit addresses, gas sponsorship, transaction indexing, websockets, and webhooks across 80+ networks; treat the scale numbers as vendor claims, but the breadth of the operator shell is still analytically useful
  • The Relay GitHub profile says relay-depository, relay-vaults, and periphery packages are used by the Relay solver and protocol stack, reinforcing that the company’s open-source footprint still resolves back into one named operator path for production integrations
• Whitepaper: No classic standalone Reservoir company whitepaper surfaced in this pass. The strongest primary materials were Reservoir’s NFT API overview, Relay’s product and API-key docs, and the public GitHub organizations that expose how much developer workflow is routed through one named operator shell.
• Sources:
  • https://nft.reservoir.tools/reference/overview
  • https://docs.relay.link/llms.txt
  • https://docs.relay.link/what-is-relay.md
  • https://docs.relay.link/references/api/api-keys.md
  • https://github.com/reservoirprotocol
  • https://github.com/relayprotocol
  • https://raw.githubusercontent.com/relayprotocol/.github/main/profile/README.md

Internal linkages

• Project-layer product cuts: reservoir for the NFT market/data stack and relay for the cross-chain execution stack.
• Useful operator-side comparison set: skip, reown, and coinbase.
• Keep the budget tight: the point of this note is the shared operator shell above multiple developer products, not a directory of every downstream integration.

Protocol / company boundary

• projects/reservoir.md still does useful work as the NFT trading-and-data product surface.
• projects/relay.md still does useful work as the cross-chain execution and payments product surface.
• This company note isolates the higher boundary above both: dashboards, API-key issuance, rate-limit policy, request visibility, webhook workflow, support and migration steering, chain-support rollout, and the broader product-packaging choices that make Reservoir the practical vendor dependency.
• That split matters because what does the API do? and which operator controls the production account, keys, limits, telemetry, and upgrade path? are related but not identical questions.

Control surface

• Practical leverage sits in dashboard authority, credential issuance and revocation, rate-limit policy, request and webhook visibility, versioning cadence, supported-chain rollout, order-ingestion rules, route selection defaults, and how much downstream teams trust Reservoir-hosted lifecycle truth.

• Even with open-source components and protocol rhetoric around parts of the stack, the easiest production path still tends to run through company-managed dashboards, docs, support channels, and hosted operational surfaces.

• Treat Reservoir as a vendor-shaped execution, data, and observability boundary — not only as an SDK bundle or a neutral protocol label.

• Last reviewed: 2026-08-11 UTC