> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/operate/run-a-node/run-a-node-with-quicknode.md).

# Run a Node with Quicknode

[QuickNode](https://www.quicknode.com/) is a service for rapidly getting set up with a Stacks node. As an easy and fast alternative to running your own node, you can utilize QuickNode to serve as an API.

{% stepper %}
{% step %}

#### Create a QuickNode account

Sign up on QuickNode: <https://www.quicknode.com/signup>
{% endstep %}

{% step %}

#### Create an endpoint

Once signed in, click "Create an endpoint". Select:

* Stacks
* your desired network (e.g., mainnet or testnet)
* your desired QuickNode plan level

After that you'll have an API endpoint URL you can use to connect to Stacks.
{% endstep %}

{% step %}

#### Install the Stacks network package

Install the `@stacks/network` package in your frontend project.
{% endstep %}

{% step %}

#### Import the network class

In your frontend code, import the network class:

{% code title="example.js" %}

```javascript
import { StacksTestnet } from "@stacks/network";
```

{% endcode %}
{% endstep %}

{% step %}

#### Configure the network with your QuickNode endpoint

Create the network instance using your QuickNode endpoint URL:

{% code title="example.js" %}

```javascript
const network = new StacksTestnet({ url: "<QUICKNODE_ENDPOINT_HERE>" });
```

{% endcode %}

Replace \<QUICKNODE\_ENDPOINT\_HERE> with the full endpoint URL provided by QuickNode.
{% endstep %}

{% step %}

#### Use with @stacks/transactions

You can now call transactions and other Stacks RPC methods as you normally would using the `@stacks/transactions` library, passing the `network` instance where required.

For an example integration and walkthrough, refer to the Hello Stacks tutorial.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stacks.co/operate/run-a-node/run-a-node-with-quicknode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.