--- title: Quicknode APIs description: Quicknode's blockchain APIs are standard HTTP endpoints that any AI agent or LLM-powered application can call directly for RPC, data pipelines, storage, and account management. tags: [] --- ## Overview > For the complete documentation index, see [llms.txt](/docs/llms.txt) Quicknode exposes its full product suite through standard HTTP, JSON-RPC, REST, gRPC, and WebSocket endpoints. These are the same APIs that power production dApps and infrastructure. Because they use standard protocols, any application, AI agent, or LLM-powered tool can call them directly without special SDKs or wrappers. TL;DR - Core API, Streams, Webhooks, Key-Value Store, and Admin API are all standard HTTP/JSON-RPC/REST/gRPC/WebSocket endpoints, no special SDK needed - API keys authenticate account-based access. Get one via the [Quicknode dashboard](https://dashboard.quicknode.com/) or programmatically through [Agent Subscriptions](/docs/build-with-ai/agent-subscriptions) - For accountless access, wallet-based per-request access with no signup is available for Core API endpoints, use [x402](/docs/build-with-ai/x402-payments) or [MPP](/docs/build-with-ai/mpp-payments) payments ## Authentication Quicknode APIs authenticate with an API key tied to your account. You can generate and manage API keys from the [Quicknode dashboard](https://dashboard.quicknode.com/) or programmatically through [Agent Subscriptions](/docs/build-with-ai/agent-subscriptions). All requests include the API key either as part of the endpoint URL or as a header, depending on the API: ```bash # JSON-RPC — API key is part of the endpoint URL curl https://your-endpoint-name.network-name.quiknode.pro/your-api-key/ \ -X POST \ -H "Content-Type: application/json" \ -d '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' # REST API — API key as a header curl https://api.quicknode.com/streams \ -H "x-api-key: YOUR_API_KEY" ``` tip If you prefer wallet-authenticated, pay-per-request access with no account required, see [x402 Payments](/docs/build-with-ai/x402-payments) or [MPP Payments](/docs/build-with-ai/mpp-payments). ## Supported Protocols Quicknode endpoints support multiple protocols depending on the chain and product: - **JSON-RPC** — Standard RPC calls over HTTP for all supported chains - **REST** — RESTful endpoints for Streams, Webhooks, Key-Value Store, and Admin APIs - **gRPC** — High-throughput streaming for Solana gRPC (Yellowstone-compatible Geyser gRPC) and Hyperliquid (Hypercore) - **WebSocket** — Real-time subscriptions for event-driven workflows ## Available APIs | API | Description | Docs | | --- | --- | --- | | Core API | Interact with RPC, REST, and gRPC endpoints across all supported blockchains | [View](https://www.quicknode.com/docs/welcome) | | Streams API | Create and manage real-time blockchain data pipelines | [View](https://www.quicknode.com/docs/streams/rest-api/getting-started) | | Webhooks API | Configure event-driven notifications for onchain activity | [View](https://www.quicknode.com/docs/webhooks/rest-api/getting-started) | | SQL Explorer API | Run SQL queries against indexed onchain data via REST | [View](https://www.quicknode.com/docs/sql-explorer/using-rest-api) | | Key-Value Store API | Read and write to serverless key-value storage | [View](https://www.quicknode.com/docs/key-value-store/rest-api/getting-started) | | Admin API | Programmatically manage endpoints, usage, security, and billing | [View](https://www.quicknode.com/docs/admin-api) | | IPFS API | Pin and retrieve files on IPFS through the Quicknode gateway | [View](https://www.quicknode.com/docs/ipfs) | Each API has full documentation with method references, parameters, and ready-to-run examples. Point your agent at the [docs index](https://www.quicknode.com/docs/llms.txt) or install [Blockchain Skills](https://skills.sh/quiknode-labs/blockchain-skills/quicknode-skill) to give it accurate knowledge of these APIs out of the box. ## Quicknode SDK Manage your whole Quicknode setup from code. The [Quicknode SDK](/docs/quicknode-sdk) gives you typed clients for the Admin, Streams, Webhooks, and Key-Value Store APIs in Rust, Python, Node.js, and Ruby, so you can create and configure endpoints, set security rules, handle billing, manage teams, run Streams and Webhooks, and read or write the Key-Value Store, all as native method calls. It handles authentication, request and response types, and pagination for you, so the requests come out correct with fewer runtime errors than hand-rolled calls. ## API Specifications (OpenRPC, OpenAPI) Quicknode publishes machine-readable OpenAPI and OpenRPC specs for its APIs. Agents can load them to auto-generate request shapes, validate parameters, and discover available operations without scraping the docs. | API | Spec URL | | --- | --- | | Streams API | [api.quicknode.com/streams/rest/openapi.json](https://api.quicknode.com/streams/rest/openapi.json) | | Webhooks API | [api.quicknode.com/webhooks/rest/openapi.json](https://api.quicknode.com/webhooks/rest/openapi.json) | | Key-Value Store API | [api.quicknode.com/kv/rest/openapi.json](https://api.quicknode.com/kv/rest/openapi.json) | | IPFS API | [quicknode.com/docs/openapi/ipfs.openapi.json](https://www.quicknode.com/docs/openapi/ipfs.openapi.json) | | Admin API | [quicknode.com/docs/openapi/admin-api.openapi.json](https://www.quicknode.com/docs/openapi/admin-api.openapi.json) | For the **Core API**, Quicknode publishes per-chain OpenRPC/OpenAPI specs covering RPC methods. Coverage is rolling out across major chains; see the [Ethereum API Overview](https://www.quicknode.com/docs/ethereum/api-overview#api-specifications-openrpc-openapi) for a representative example, and the linked spec is available alongside each chain's API overview page. ## We ❤️ Feedback! If you have any feedback or questions about this documentation, [let us know](https://airtable.com/shrfIppvMmbdWxHgC). We'd love to hear from you!