QuickNode Credential Boundary

Overview

Separate data-plane endpoint tokens from account-level API keys. An endpoint token authorizes chain RPC traffic; an API key authorizes QuickNode product and control-plane clients such as Admin API, Streams, the unified SDK, and qn.

Prerequisites

• The client, chain, network, environment, and required QuickNode products
• An approved secret manager and named rotation owner
• A QuickNode account role permitted to create only the required credential

Instructions

Step 1: Inventory credential consumers

Use Read and Grep to locate endpoint URLs, x-token, x-api-key, QN_SDK__API_KEY, and QUICKNODE_* references. Record owners without printing values. Treat any token embedded in an RPC URL as secret material.

Step 2: Select the credential type