Ship the bestWeb3 experienceson Solana.

One widget. Three API calls. No RPC glue.

The same flow that powers Venum Swap is a public, composable API. Quote, build, submit. No aggregator black box and no raw-RPC glue code.

swap.venum.devLIVE

AUTO · 100 BPS

SELL—

USDC▼

—

BUY

SOL▼

 

—

ROUTE—

MIN RECEIVED—

MULTI-ROUTE FAST BROADCAST

SWAP

POST /v1/quoteLIVE

Loading a real quote from api.venum.dev...

TS SDKHTTP

swap.tsCopy

import { VenumClient, solToLamports } from '@venumdev/sdk'

const venum = new VenumClient({ apiKey: API_KEY })

// 01. Get a quote
const quote = await venum.quote({
  inputMint: 'SOL',
  outputMint: 'USDC',
  amount: solToLamports(1),
  slippageBps: 50,
})

// 02. Build a transaction you can inspect
const build = await venum.buildSwap({
  inputMint: 'SOL',
  outputMint: 'USDC',
  amount: solToLamports(1),
  userPublicKey: wallet.publicKey.toBase58(),
})

// 03. Sign and submit
const signed = await wallet.signTransaction(build.transaction)
const { signature } = await venum.submitSwap({
  quoteId: build.quoteId,
  signedTransaction: signed,
})

The most cost-efficient way to build on Solana.

Flat-rate pricing, composable execution, and a surface designed to remove the most expensive parts of a typical Solana stack before you ever hit a rate limit.

One execution layer. Every surface you need.

Web3 apps, traders, bots, agents, and developers all plug into the same composable layer through the surface that fits their workflow.

Humans, scripts, or agents. Pick your interface.

The same execution layer exposed through the surface that fits your workflow. Reuse the real products that already ship today.

One execution layer. Two RPC products.

A clean Solana RPC for the server side. A separate URL per dApp for the browser side. Both share the same backend; each ships with the gates that fit how it's actually consumed.

// rpc.venum.dev — JSON-RPC, key-gated, all standard methods
const conn = new Connection('https://rpc.venum.dev', {
  commitment: 'confirmed',
  fetchMiddleware: (url, init, fetch) => {
    init.headers = { ...init.headers, 'X-API-Key': API_KEY }
    return fetch(url, init)
  },
})

const slot = await conn.getSlot()
const info = await conn.getAccountInfo(new PublicKey(mint))

// www-rpc.venum.dev/v1/<your-id> — for dApp frontends
// Origin allowlist + abuse filtering at the edge.
const conn = new Connection(
  'https://www-rpc.venum.dev/v1/abc123',
  'confirmed',
)

const price = await conn.getAccountInfo(poolAddress)

Why two products: the threat model differs. Server-side code holds the key in env, so X-API-Key is the right gate. Browser-side code can't hold a secret — anyone who opens devtools steals it — so the gate has to be the request shape itself.

A more cost-efficient execution stack.

Most Solana infra spend comes from polling state, fetching prices, and stitching together plumbing. Venum removes the most expensive patterns first.

Simple, honest, flat-rate.

No swap fees. No hidden costs. No per-call billing surprises. Just a flat monthly line item and the execution surface you need.

No swap fees on any tier. Cancel anytime. Enterprise plans on request.