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

# Tiers

Snowsight provides three tiers available to users:

1. Premium Tier\*
   * Lowest latency connection to mempool, with up to 3 concurrent websocket connections
   * Highest priority access for institutional users
   * **𝛿** (pending -> finalized): \~2.1 s
   * Per-block pending transaction coverage: >95%
2. Standard Tier
   * Generic connection to mempool, lower priority than Premium Tier
   * **𝛿** (pending -> finalized): \~900 ms
   * Per-block pending transaction coverage: \~75%
3. Trial Tier
   * No cost connection to mempool
   * Lowest priority access, mempool access can be delayed and no pending transaction coverage guarantees

\*only Premium Tier is eligible to use the Transaction Propagator 


---

# 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.snowsight.chainsight.dev/snowsight/tiers.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.