QuickNode API
Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey5 EndpointsREST
For Agents
Programmatically create an endpoint, list endpoints. Covers 5 operations with apiKey authentication.
Use for: I need to an endpoint, I want to endpoints, Search for an endpoint, Find all an endpoint
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
QuickNode provides blockchain infrastructure. This API covers the QuickNode management/provisioning REST API for managing endpoints, chains, and account resources. Actual blockchain RPC calls are made through provisioned node endpoints. The API exposes 5 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the QuickNode API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QuickNode API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fquicknode.com%2Fquicknode" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fquicknode.com%2Fquicknode" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with QuickNode API.
Create an endpoint
List endpoints
Get an endpoint
Delete an endpoint
Access QuickNode API communications resources via REST API
Use Cases
Patterns agents use QuickNode API for, with concrete tasks.
★ Communications Operations
Use the QuickNode API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including create an endpoint, list endpoints, get an endpoint.
Call POST /endpoints to create an endpoint
Automated Chains Management
Automate chains operations by combining multiple QuickNode API endpoints. Agents can list endpoints and then get an endpoint in a single workflow.
Call GET /endpoints to list endpoints, then verify the result
AI Agent Integration via Jentic
AI agents discover and call QuickNode API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create an endpoint', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
5 endpoints — quicknode provides blockchain infrastructure.
METHOD
PATH
DESCRIPTION
POST
/endpoints
Create an endpoint
GET
/endpoints
List endpoints
GET
/endpoints/{endpoint_id}
Get an endpoint
DELETE
/endpoints/{endpoint_id}
Delete an endpoint
GET
/chains
List supported chains
POST
/endpoints
Create an endpoint
GET
/endpoints
List endpoints
GET
/endpoints/{endpoint_id}
Get an endpoint
DELETE
/endpoints/{endpoint_id}
Delete an endpoint
GET
/chains
List supported chains
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring QuickNode by hand means learning its x-api-key header auth, targeting the api.quicknode.com host, and managing your own retries against its blockchain endpoint operations. Through Jentic you install once, import QuickNode from the API Directory, store the API key once, and your agent calls it.
Permission scoping
QuickNode puts the endpoint id in the URL path (/endpoints/{endpoint_id}), so a rule can pin your agent to one endpoint: it can read that endpoint and nothing else. You choose the operations it may call, so destructive ones like deleting an endpoint are not included unless you add them.
Credential isolation
Your QuickNode API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a QuickNode endpoint' or 'list supported chains', and Jentic returns the matching QuickNode operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using QuickNode API through Jentic.
What authentication does the QuickNode API use?
The QuickNode API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create an endpoint with the QuickNode API?
Yes. Use the POST /endpoints endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the QuickNode API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create an endpoint through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an endpoint'. Jentic returns the matching QuickNode API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the QuickNode API have?
The QuickNode API exposes 5 endpoints covering chains, endpoints operations.
Can I limit what my agent is allowed to do with the QuickNode API?
Yes. Because you run Jentic One yourself, your own rules decide which QuickNode operations the agent may call and which stored API key it may use. You can allow read-only operations like listing endpoints (GET /endpoints), fetching a single endpoint (GET /endpoints/{endpoint_id}), or listing supported chains (GET /chains) while leaving out write operations such as creating (POST /endpoints) or deleting an endpoint (DELETE /endpoints/{endpoint_id}). Since the endpoint id lives in the URL path, a rule can even pin the agent to one specific endpoint so it can read that endpoint and nothing else.
GET STARTED