Quicknode Pack

> 18 governed workflows for operating QuickNode blockchain RPC and data infrastructure safely.

Scope

This pack treats QuickNode as several distinct operational surfaces instead of one generic Web3 API:

• endpoint data-plane access with endpoint tokens, JSON-RPC, and WebSocket subscriptions;
• account and control-plane automation through the Admin API, qn CLI, and QuickNode SDK;
• Streams and Webhooks event delivery with explicit authentication, acknowledgement, retry, and deduplication contracts;
• production observability, security, credit attribution, deployment, and migration controls.

Endpoint tokens and account API keys are different credentials. Supported chains, methods, archive history, pruning behavior, security controls, metrics, logs, and product availability vary by chain and plan. Every workflow requires those boundaries to be verified before a change is made.

Installation

/plugin install quicknode-pack@claude-code-plugins-plus

Operator Map

Current Product Boundaries

• The unified QuickNode SDK exposes product clients such as Admin, RPC, Streams, Webhooks, Key-Value Store, and SQL; availability depends on the SDK target and product.
• The qn CLI and Admin API operate account resources. The Admin API uses an x-api-key credential and is available on paid plans.
• Endpoint metrics expose latency percentiles and request behavior. Detailed logs have additional plan boundaries.
• Streams destinations include Webhook, S3, Azure Blob Storage, PostgreSQL, and Kafka. Delivery is sequential by batch, destinations must acknowledge successfully, and consumers must tolerate retries and duplicates.
• Webhooks and Streams are separate products. Choose based on the delivery and transformation contract instead of using their names interchangeably.

Documentation

• QuickNode SDK
• QuickNode CLI
• Admin API
• Streams
• Webhooks
• Supported chains and node types

Each skill also carries a consulted, workflow-specific source record in references/official-docs.md.

License

MIT