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

# Overview

> Quick introduction to Uniblock's WebSockets offering.

<Info>
  Remember to create your project and get your API key through the
  [Uniblock dashboard](https://dashboard.uniblock.dev).
</Info>

Uniblock WebSockets let you connect to supported provider streams through a
single Uniblock-managed access layer. This gives you a consistent authentication
model, unified billing, and provider-specific WebSocket access without managing
separate credentials for each provider.

This section includes support for `Alchemy`, `Ankr`, `CoinGecko`, `Codex`,
`GoldRush`, `Helius`, and `Hydromancer`.

## How it works

WebSocket integrations use a two-step handshake:

1. Call the provider's HTTP validation endpoint first.
2. Open a connection to the matching WSS endpoint using the same request
   details.
3. Send the provider-specific subscription or message payload after the socket
   connects.

This validation step helps confirm that your API key and required parameters are
present before a long-lived WebSocket connection is established.

<Tip>
  Try validation first in Postman before opening a persistent WebSocket
  connection in your application.
</Tip>

## Authentication

Most Uniblock WebSocket endpoints use the `X-API-KEY` header. Some providers,
such as Hydromancer, pass the Uniblock API key as a required query parameter.

For full authentication details, see [Authentication](/reference/websockets/authentication).

## Supported providers

* [Alchemy](/reference/websockets/providers/websockets-alchemy)
* [Ankr](/reference/websockets/providers/websockets-ankr)
* [CoinGecko](/reference/websockets/providers/websockets-coingecko)
* [Codex](/reference/websockets/providers/websockets-codex)
* [Helius](/reference/websockets/providers/websockets-helius)
* [Hydromancer](/reference/websockets/providers/websockets-hydromancer)

## Pricing

WebSocket costs are calculated per response returned:

* Formula: `0.1 CU * 3181.819` per response returned

Actual usage depends on the number of responses your subscriptions receive.

For provider-specific pricing and connection limits, see
[Usage & Limits](/reference/websockets/usage-limits).