# Overview

## Solana Vibe Station Developer Documentation

Welcome to the Solana Vibe Station (SVS) developer documentation. This site is your reference for building on top of our Solana infrastructure — from standard RPC calls all the way through to low-latency transaction landing, gRPC streaming, historical data, and our partner marketplace.

Everything you need to integrate is documented here. If you're new, start with **Getting Started → Rate Limits**, then jump to the section that matches what you're building.

***

### [Getting Started](/developers/getting-started.md)

Before making your first request, review the basics:

* **Rate Limits** — Per-tier request limits, burst behavior, and headers you should be reading on every response.

***

### [Solana RPC](/developers/solana-rpc/http-methods.md)

The foundation of the platform. Standard Solana JSON-RPC, served from our Atlanta and Amsterdam regions.

* [**HTTP Methods** ](/developers/solana-rpc/http-methods.md)— Full set of supported HTTP RPC methods for queries, account state, transaction submission, and chain metadata.
* [**Websocket Methods**](/developers/solana-rpc/websocket-methods.md) — Real-time subscriptions for accounts, programs, slots, signatures, and logs over WSS.

### [Jito](/developers/jito/jito-solana-rpc-methods.md)

Access the Jito block engine through SVS endpoints for bundle submission, simulation, and tip discovery.

* [**Jito Solana RPC Methods** ](/developers/jito/jito-solana-rpc-methods.md)— Submit and simulate bundles, query tip accounts and floor amounts, and interact with the rest of the Jito block engine surface area.

### [Lightspeed](/developers/lightspeed/overview.md)

Our optimized `sendTransaction` propagation service for applications that need the highest possible landing rates and lowest confirmation latency.

* [**Overview**](/developers/lightspeed/overview.md) — Tiered tip routing across staked validators and direct leader connections, plus the `/lightspeed` endpoint reference.

### gRPC Streaming

The lowest-latency way to consume on-chain data. Subscribe to accounts, transactions, slots, blocks, and entries with sub-second deltas.

### [Historical Data](/developers/historical/overview.md)

Archival access to the full Solana chain history when our standard RPC retention isn't enough.

* **Overview** — Supported archival methods, including `getBlock`, `getBlocks`, `getBlocksWithLimit`, `getBlockTime`, `getFirstAvailableBlock`, `getSlot`, `getTransaction`, `getSignaturesForAddress`, and `getSignatureStatuses`. Use these for backfills, analytics, and reorg-aware indexing.

***

### [Partner Marketplace](/developers/partner-marketplace/overview-partner-marketplace.md)

Third-party data products integrated alongside SVS infrastructure and accessible under your existing API key.

* [**Overview**](/developers/partner-marketplace/overview-partner-marketplace.md) — How the marketplace works, billing, and access management.
* SVS API — A higher-level data API layered on top of our infrastructure. Built for teams that need clean token and DeFi data without standing up their own indexer.
  * **Token Price API** — Spot pricing for any SPL token.
  * **Token Info API** — Core token metadata, supply, and identity.
  * **Token Metadata API** — Extended off-chain metadata pulled from token URIs.
  * **Token Rank** — Ranking and discovery signals across the SPL token universe.
  * **Price Subscribe** — Streaming price updates over websocket.
  * **DeFi Price** — Pool-aware pricing across major Solana DEXes.
  * **DeFi Multiprice** — Batch pricing for multiple tokens in a single call.
  * **Prediction Candles** — Forward-looking candle data for supported markets.
  * **SVS API MCP Server** — Model Context Protocol server exposing the SVS API to AI agents and IDEs.
* [**Sailfish**](/developers/partner-marketplace/sailfish.md) — Real-time launchpad and AMM data:
  * **Latest Block Tick**
  * **Pool Information**
  * **Token Information**
  * **Normalized Trades**
  * **Graduated Pools**
  * **WebSocket Event Stream**

***

### Need Help?

If you hit something the docs don't cover, reach out via your portal account or on Discord by submitting a support ticket.


---

# Agent Instructions: 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:

```
GET https://docs.solanavibestation.com/developers/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.