Skip to content
Skills Library
Programming · Tool integration

quicknode-install-auth

/quicknode-install-auth

Choose and configure the correct QuickNode credential boundary for RPC endpoints, the Admin API, the unified SDK, and the qn CLI. Use when onboarding an endpoint, separating environments, or rotating access without exposing tokens. Trigger with: "authenticate QuickNode", "configure a QuickNode endpoint", "rotate QuickNode credentials".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Choose and configure the correct QuickNode credential boundary for RPC endpoints, the Admin API, the unified SDK, and the qn CLI. Use when onboarding an endpoint, separating environments, or rotating access without exposing tokens. Trigger with: "authenticate QuickNode", "configure a QuickNode endpoint", "rotate QuickNode credentials".

Triggers from the description

authenticate QuickNodeconfigure a QuickNode endpointrotate QuickNode credentials

Arguments

/quicknode-install-auth [client-and-environment-scope]
Original author description

Choose and configure the correct QuickNode credential boundary for RPC endpoints, the Admin API, the unified SDK, and the qn CLI. Use when onboarding an endpoint, separating environments, or rotating access without exposing tokens. Trigger with: "authenticate QuickNode", "configure a QuickNode endpoint", "rotate QuickNode credentials".

How it works

  1. Overview
  2. Prerequisites
  3. Instructions
  4. Tool Discipline
  5. Output
  6. Examples
  7. Error Handling
  8. Resources
Original SKILL.md headings · 69 lines, 500 words
SKILL.md preview
---
name: quicknode-install-auth
description: 'Choose and configure the correct QuickNode credential boundary for RPC endpoints, the Admin API, the unified SDK, and the qn CLI. Use when onboarding an endpoint, separating environments, or rotating access without exposing tokens. Trigger with: "authenticate QuickNode", "configure a QuickNode endpoint", "rotate QuickNode credentials".'
allowed-tools: Read, Grep, Write, Edit, Bash(qn:*), Bash(curl:*)
version: 2.0.0
argument-hint: '[client-and-environment-scope]'
model: inherit
effort: high
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - saas
  - quicknode
  - blockchain
  - authentication
  - secrets
compatibility: 'Requires a QuickNode account; Admin API and advanced endpoint-security features depend on the account plan'
---

# 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

Use an endpoint authentication token for HTTP or WSS chain RPC. Prefer the `x-token` header for server-side clients when the chain endpoint supports it. Use a dashboard API key for Admin API, SDK, Streams, Webhooks, KV Store, or SQL Explorer access.

### Step 3: Separate environments

Give development, staging, production, and independent applications separate endpoint tokens. Multi-token authentication permits revoking one consumer without rotating every workload. Do not reuse a human CLI session as a production service identity.

### Step 4: Configure clients safely

Use Write or Edit to add secret references and documented variable names, never values. Configure the unified SDK with `QN_SDK__API_KEY`. Use Bash(qn:*) for `qn auth login` and `qn auth whoami` only in an approved interactive operator session.

### Step 5: Verify the intended boundary

Use Bash(curl:*) for one read-only JSON-RPC probe with the token supplied by the runtime secret mechanism. Confirm the chain identifier and an expected denial after removing the credential; never echo the endpoint URL or request headers.

### Step 6: Record rotation

Document credential type, endpoint or API scope, consumers, storage reference, creation date, review date, and revoke-first rollback. Rotate with overlap: create, deploy, verify, then revoke the old token.

## Tool Discipline

Use Read and Grep for discovery, Write and Edit for secret references, Bash(qn:*) for authenticated CLI identity checks, and Bash(curl:*) only for redacted read probes. Never place a live endpoint URL in source, logs, shell history, or support evidence.

## Output

- Credential-to-client matrix
- Environment-separated secret references
- Negative and positive verification results
- Rotation and revocation record

## Examples

A production RPC service receives a dedicated endpoint token through its secret manager. A deployment auditor uses a separate `x-api-key` identity through the SDK and cannot submit chain transactions.

## Error Handling

| Failure | Response |
| --- | --- |
| Endpoint returns unauthorized | Verify endpoint token placement without logging it |
| Admin API returns 401 | Verify the API key and account scope, not the RPC token |
| Token appears in a URL log | Revoke it, sanitize retained logs, and replace it |
| Rotation breaks one consumer | Restore the old secret reference during the overlap window |

## Resources

- [Authentication evidence and source notes](references/official-docs.md)
- [QuickNode SDK quickstart](https://www.quicknode.com/docs/sdk/quick-start)
- [Multi-token authentication](https://www.quicknode.com/guides/quicknode-products/endpoint-security/how-to-set-up-multi-token-authentication-on-quicknode)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 1 KB

Versions

The database has no other skills named quicknode-install-auth.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 73cd89e5c9df (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100quicknode-sdk-patterns
    Adopt the current unified QuickNode SDK with explicit product clients, timeouts, environment configuration, and platform checks. Use when coordinating Admin API, RPC, Streams, Webhooks, KV Store, or SQL Explorer from one service. Trigger with: "use the QuickNode SDK", "build a…
  • 100quicknode-hello-world
    Prove a new QuickNode RPC endpoint with a minimal, read-only JSON-RPC contract before application integration. Use when onboarding a chain endpoint or separating provider failures from client-library failures. Trigger with: "test my QuickNode endpoint", "make the first QuickNode…
  • 100quicknode
    QuickNode is hosted RPC (HTTP + WebSocket) plus Streams, Webhooks and a testnet faucet for World Chain, Unichain, Hedera, Arc, 0G and 80+ other chains. Use this skill when you need a QuickNode endpoint URL, viem/ethers on QuickNode, eth_subscribe/WebSockets, Streams or Webhooks…
  • 100quicknode-webhooks
    Receive and verify Quicknode Streams and Quicknode Webhooks deliveries. Use when setting up a Quicknode webhook handler, debugging X-QN-Signature verification, or processing block, transaction and log data streamed from a Quicknode Stream or Webhook.
  • 91quicknode-skill
    Quicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap API, x402, MPP, Agent Subscriptions, CLI, and MCP. Use for any Quicknode product,…
  • 91quicknode-skill
    Quicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap API, x402, MPP, Agent Subscriptions, CLI, and MCP. Use for any Quicknode product,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.