Open APIs · Free for the Solana ecosystem

Solana data, open to everyone building on it

Two JPool-maintained APIs for Solana validator and network data. Both share a core of validator stake, APY, commission and leader-slot data, and each adds its own. The JPool API is public. The SVT API needs a free key on request. We run them as a service for the ecosystem.

API 01
Solana Validator Toolkit APIFor validator monitoring & performance

Validator performance and MEV yield, leader and skipped-slot history, and per-validator operational stats. It also carries network-wide epoch data and SOL/JSOL price history.

api.svt.one Explore ↓
API 02
JPool APIFor validator research & network history

Validator data SVT doesn't carry, like who delegates to them, blacklist membership and MEV. It also holds a historical record of network-wide metrics.

api.jpool.one Explore ↓
API 01

Solana Validator Toolkit API

For validator monitoring & performance

The API behind SVT. It shows the network the way an operator sees it, and powers SVT's own dashboards and reports.

Open Swagger Docs
api.svt.one/docs
What you read through it
  • APY and MEV yield, per epoch and versus the cluster average
  • Leader and skipped-slot history, plus validator monitoring
  • Per-validator operational stats for recent days, with cluster comparison
  • Validator status and commission, epoch data and SOL/JSOL price history
  • ... and more
Base URLapi.svt.one
AccessKey issued on request: ask on Telegram
API 02

JPool API

For validator research & network history

The API behind JPool's validator and network data. It carries validator detail SVT doesn't, along with a historical record of the network's key metrics.

Open Swagger Docs
api.jpool.one/docs
What you read through it
  • Validator stake, APY and commission
  • Delegation breakdown: who delegates to a validator
  • Blacklist membership and sources, plus MEV data
  • Historical network-wide metrics, including inflation and SOL supply
  • ... and more
Base URLapi.jpool.one
AccessPublic
SDK 01

@jpool/bond-sdk

For building with validator bonds

A TypeScript SDK for programmatic access to the JBond program on Solana. Register validators, manage collateral-backed bonds, and build on-chain bond flows with a package published openly on npm.

View on npm
npmjs.com/package/@jpool/bond-sdk
What you can build with it
  • Register validators and create bond accounts
  • Top up and manage bond collateral in SOL and SPL tokens (JSOL)
  • Set and manage withdrawal authorities
  • Monitor bond status and view transaction history
Install
pnpm add @jpool/bond-sdk
Package@jpool/bond-sdk
AccessPublic on npm
SDK 02

@jpool/incentive-sdk

For on-chain validator incentive campaigns

A typed Solana Kit client for the JPool incentive program. Build reward campaigns, read participant positions, and preview claimable rewards.

View on npm
npmjs.com/package/@jpool/incentive-sdk
What you can build with it
  • Create fixed-rate and proportional reward campaigns
  • Add multiple reward tokens and stepped emission schedules
  • Fetch typed campaign and position accounts, and derive PDAs
  • Preview rewards client-side and build claim instructions
Install
pnpm add @jpool/incentive-sdk @solana/kit
Package@jpool/incentive-sdk
AccessPublic on npm
SDK 03

@jpool/sdk

For JPool liquid staking integrations

A TypeScript SDK for interacting with the JPool liquid staking pool on Solana. Build staking flows and query pool and direct-stake data.

View on npm
npmjs.com/package/@jpool/sdk
View on GitHub
github.com/pointgroup-labs/jpool-ts-sdk
What you can build with it
  • Stake SOL or stake accounts and receive JSOL
  • Withdraw as SOL or a delegated stake account
  • Direct stake to specific validators
  • Query pool state, rates, fees, direct stakes, and wallet bindings
Install
pnpm add @jpool/sdk
Package@jpool/sdk
AccessPublic on npm
Access & fair use

Ask for a key, use it reasonably

The JPool API is public, so no key is needed. The SVT API needs a key, which we issue free on request. Just tell us what you're building on Telegram. There are no hard quotas either way. We only ask that you keep usage to what your product actually needs, so the APIs stay fast for everyone.

What that means in practice
  • One key per project, and keep it yours. Don't share or resell access.
  • Request only the data you use, and cache what doesn't change every second.
  • Poll no faster than the data updates. Validator and pool state changes once per epoch, not every second.
  • Planning something heavy? Say so when you ask for the key and we'll make room for it.

If usage ever threatens availability we'll reach out before changing anything, and any future limit will be published here first.