> For the complete documentation index, see [llms.txt](https://docs.validationcloud.io/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.validationcloud.io/v1/stellar/overview.md).

# Overview

## Network Support

<table><thead><tr><th width="420">Network</th><th>HTTPS</th><th>WSS</th></tr></thead><tbody><tr><td>Pubnet: Horizon (90 day history) &#x26; Stellar RPC (7 day history)</td><td>✅</td><td>❌</td></tr><tr><td>Testnet: Horizon (full history since the latest testnet reset) &#x26; Stellar RPC (7 day history)</td><td>✅</td><td>❌</td></tr><tr><td>Pubnet Archive: Horizon only (1 year history)</td><td>✅</td><td>❌</td></tr></tbody></table>

> **History retention:** Horizon on Pubnet lets you query the most recent 90 days of history, and the Pubnet Archive endpoint extends this to 1 year (the archive endpoint serves Horizon only; Stellar RPC is not available on it). Stellar RPC (formerly Soroban) serves the most recent 7 days of history on both Pubnet and Testnet, which is the Stellar network-standard retention window. Horizon on Testnet serves full history back to the most recent Stellar testnet reset; the Stellar Development Foundation periodically resets testnet, and history restarts from each reset.

#### Stellar SSE Streaming

We recently introduced an updated Compute Unit (CU) model for **Server-Sent Events (SSE)** streaming on Stellar Horizon API endpoints. SSE allows developers to receive real-time updates without the need for continuous polling.

**Pricing Model**

SSE-enabled Stellar endpoints use a two-part pricing structure:

* **Base cost per request:** 20 CUs (same as standard Stellar endpoints)
* **Data streaming cost:** 1 CU per KB of data streamed to the client

This differs from standard Stellar endpoints, which only charge the base request cost and do not include any data-based pricing.

**Compute Unit Calculation**

```
Total CUs = (20 × number of requests) + (1 × response size in KB)
```

```
Total CUs = (cu_amount × requests) + ((response_size_bytes / 1024) × cu_per_kb)
```

**Key Difference**

* **Standard endpoints:** Fixed cost per request (no data-based charges)
* **SSE endpoints:** Base request cost plus variable cost based on streamed data volume

## Compute Units

#### SSE Streaming Endpoints

Certain Stellar Horizon endpoints support **Server-Sent Events (SSE)**, allowing clients to receive real-time updates instead of polling.

> **Compute Units:** When used in streaming mode, these endpoints are charged at **20 CUs per request** plus **1 CU per KB of data streamed**.

The following endpoints support SSE streaming:

***

**Top-level endpoints**

* GET /ledgers
* GET /transactions
* GET /operations
* GET /payments
* GET /effects
* GET /trades

***

**Account-specific endpoints**

* GET /accounts/{account\_id}/transactions
* GET /accounts/{account\_id}/operations
* GET /accounts/{account\_id}/payments
* GET /accounts/{account\_id}/effects
* GET /accounts/{account\_id}/trades
* GET /accounts/{account\_id}/offers

***

**Ledger-specific endpoints**

* GET /ledgers/{ledger\_sequence}/transactions
* GET /ledgers/{ledger\_sequence}/operations
* GET /ledgers/{ledger\_sequence}/payments
* GET /ledgers/{ledger\_sequence}/effects

***

**Liquidity pool endpoints**

* GET /liquidity\_pools/{liquidity\_pool\_id}/effects
* GET /liquidity\_pools/{liquidity\_pool\_id}/trades
* GET /liquidity\_pools/{liquidity\_pool\_id}/transactions
* GET /liquidity\_pools/{liquidity\_pool\_id}/operations

***

**Transaction & operation endpoints**

* GET /operations/{operation\_id}/effects
* GET /transactions/{transaction\_id}/operations
* GET /transactions/{transaction\_id}/effects

***

**Offer endpoints**

* GET /offers/{offer\_id}/trades

***

**Claimable balance endpoints**

* GET /claimable\_balances/{claimable\_balance\_id}/transactions
* GET /claimable\_balances/{claimable\_balance\_id}/operations

### Stellar RPC (formerly known as Soroban)

<table data-header-hidden><thead><tr><th></th><th width="100"></th></tr></thead><tbody><tr><td>getEvents</td><td>10</td></tr><tr><td>getFeeStats</td><td>10</td></tr><tr><td>getHealth</td><td>10</td></tr><tr><td>getLatestLedger</td><td>10</td></tr><tr><td>getLedgerEntries</td><td>10</td></tr><tr><td>getLedgers</td><td>10</td></tr><tr><td>getNetwork</td><td>10</td></tr><tr><td>getTransaction</td><td>10</td></tr><tr><td>getTransactions</td><td>10</td></tr><tr><td>getVersionInfo</td><td>10</td></tr><tr><td>sendTransaction</td><td>10</td></tr><tr><td>simulateTransaction</td><td>10</td></tr></tbody></table>

### Horizon

<table data-header-hidden><thead><tr><th width="487"></th><th width="100"></th></tr></thead><tbody><tr><td>GET /accounts</td><td>20</td></tr><tr><td>GET /accounts/:account_id</td><td>20</td></tr><tr><td>GET /accounts/:account_id/transactions</td><td>20</td></tr><tr><td>GET /accounts/:account_id/operations</td><td>20</td></tr><tr><td>GET /accounts/:account_id/payments</td><td>20</td></tr><tr><td>GET /accounts/:account_id/effects</td><td>20</td></tr><tr><td>GET /accounts/:account_id/offers</td><td>20</td></tr><tr><td>GET /accounts/:account_id/trades</td><td>20</td></tr><tr><td>GET /accounts/:account_id/data/:key</td><td>20</td></tr><tr><td>GET /assets</td><td>20</td></tr><tr><td>GET /claimable_balances</td><td>20</td></tr><tr><td>GET /claimable_balances/:claimable_balance_id</td><td>20</td></tr><tr><td>GET /claimable_balances/:claimable_balance_id/transactions</td><td>20</td></tr><tr><td>GET /claimable_balances/:claimable_balance_id/operations</td><td>20</td></tr><tr><td>GET /effects</td><td>20</td></tr><tr><td>GET /fee_stats</td><td>10</td></tr><tr><td>GET /ledgers/:sequence</td><td>20</td></tr><tr><td>GET /ledgers/:sequence/transactions</td><td>20</td></tr><tr><td>GET /ledgers/:sequence/payments</td><td>20</td></tr><tr><td>GET /ledgers/:sequence/operations</td><td>20</td></tr><tr><td>GET /ledgers/:sequence/effects</td><td>20</td></tr><tr><td>GET /ledgers</td><td>20</td></tr><tr><td>GET /liquidity_pools</td><td>20</td></tr><tr><td>GET /liquidity_pools/:liquidity_pool_id</td><td>20</td></tr><tr><td>GET /liquidity_pools/:liquidity_pool_id/effects</td><td>20</td></tr><tr><td>GET /liquidity_pools/:liquidity_pool_id/trades</td><td>20</td></tr><tr><td>GET /liquidity_pools/:liquidity_pool_id/transactions</td><td>20</td></tr><tr><td>GET /liquidity_pools/:liquidity_pool_id/operations</td><td>20</td></tr><tr><td>GET /offers</td><td>20</td></tr><tr><td>GET /offers/:offer_id</td><td>20</td></tr><tr><td>GET /offers/:offer_id/trades</td><td>20</td></tr><tr><td>GET /operations/:id</td><td>20</td></tr><tr><td>GET /operations/:id/effects</td><td>20</td></tr><tr><td>GET /operations</td><td>20</td></tr><tr><td>GET /order_book</td><td>10</td></tr><tr><td>GET /paths/strict-receive</td><td>10</td></tr><tr><td>GET /paths/strict-send</td><td>10</td></tr><tr><td>GET /payments</td><td>20</td></tr><tr><td>GET /transactions/:transaction_hash/payments</td><td>10</td></tr><tr><td>GET /trades</td><td>20</td></tr><tr><td>GET /trade_aggregations</td><td>40</td></tr><tr><td>GET /transactions/:transaction_hash</td><td>20</td></tr><tr><td>GET /transactions/:transaction_hash/operations</td><td>20</td></tr><tr><td>GET /transactions/:transaction_hash/effects</td><td>20</td></tr><tr><td>GET /transactions</td><td>20</td></tr><tr><td>POST /transactions</td><td>20</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.validationcloud.io/v1/stellar/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.