> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thornode.io/llms.txt
> Use this file to discover all available pages before exploring further.

# ThorEdge RPC

> Connect to Solana JSON-RPC and WebSocket endpoints from one location URL.

ThorEdge gives you Solana JSON-RPC over HTTPS and subscriptions over WSS. Copy the complete URLs for one location from the dashboard; a successful first request returns a JSON-RPC result with a recent blockhash.

## RPC and WebSocket workloads

ThorEdge handles standard Solana RPC calls and WebSocket subscriptions. Supported account-query methods use the same URL and are routed through [FastGate](/products/fastgate-rpc).

Choose [Yellowstone gRPC](/products/yellowstone-grpc) or [Pulse Decoded Shreds](/products/pulse) when you need a persistent data stream instead of request-response RPC.

## Quick reference

| Item                 | Value                                           |
| -------------------- | ----------------------------------------------- |
| Requests             | HTTPS, JSON-RPC 2.0                             |
| Subscriptions        | WSS                                             |
| Endpoint             | Complete location URL copied from the dashboard |
| Authentication       | Credential carried by the copied URL            |
| Credential scope     | Selected access, network, and location          |
| Optional restriction | One stable public IPv4 address                  |
| Live limits          | **Usage** and **Limits** in the dashboard       |

## Before you start

You need:

* An active pass or rental with an enabled network and location
* A token for that location
* `curl` and `jq` for the first request
* One stable public egress IPv4 if you want to restrict the token

## Copy your endpoints

<Steps>
  <Step title="Select your access">
    Open **Endpoints**, keep the **Endpoints** tab selected, then choose the
    pass or rental you want to use.
  </Step>

  <Step title="Choose a network and location">
    Select the network and an offered location for the access.
  </Step>

  <Step title="Create or select a token">
    Use a token for the selected location. You can optionally restrict it to one
    stable public IPv4 address.
  </Step>

  <Step title="Copy both secure URLs">
    Copy the complete `https://` RPC URL and `wss://` WebSocket URL. Do not
    assemble either URL yourself.
  </Step>
</Steps>

<Warning>
  The complete HTTPS and WSS URLs contain or resolve to authentication material.
  Store them as secrets and keep them out of browser bundles, logs, screenshots,
  and source control.
</Warning>

## Send your first request

Follow the [RPC and WebSocket quickstart](/products/thoredge-rpc/quickstart) to receive a blockhash over HTTPS and slot notifications over WSS. The [HTTP method reference](/api-reference/thoredge-rpc/http-methods) lists every method ThorEdge serves and which service answers it.

## Run in production

* Treat non-2xx HTTP responses and JSON-RPC `error` objects as failures.
* Retry only transient failures with bounded backoff and jitter.
* Recreate WebSocket subscriptions after reconnecting and reconcile state when gaps matter.
* Recopy a URL after its token is regenerated or revoked; other location tokens are unaffected.
* Read current throughput and concurrency values from **Usage** and **Limits**.

## Troubleshooting

| Problem                   | Fix                                                                                      |
| ------------------------- | ---------------------------------------------------------------------------------------- |
| Unauthorized or forbidden | Recopy the complete URL and check the access, location, and optional IPv4 restriction.   |
| Rate limited              | Compare traffic with **Usage** and **Limits**, reduce concurrency, and back off retries. |
| RPC works but WSS fails   | Recopy the `wss://` URL and permit outbound WebSocket traffic.                           |
| A working URL stopped     | Check whether the token was regenerated, revoked, or its access expired; replace it.     |

## Next steps

* [Run the quickstart](/products/thoredge-rpc/quickstart)
* [Read the HTTP and WebSocket method reference](/api-reference/thoredge-rpc/http-methods)
* [Query accounts through FastGate](/products/fastgate-rpc)
* [Read current plans and limits](/reference/plans-and-limits)
* [Store and rotate credentials safely](/reference/security)