One API.The whole stack.
Stop stitching raw RPC, price feeds, swap routing, and TX tracking every time you ship a bot. Venum gives you pool state, pricing, routing, and submission behind one API.
The core loop, without the stitched stack.
This is the useful promise on this page: prices, routing, submission, and confirmation exposed through one surface, instead of wiring separate vendors for each step.
// One API for the core bot loop: price, quote, build, submit, confirm
import { VenumClient, solToLamports } from '@venumdev/sdk'
// Plain HTTP — server-to-server skips the TLS handshake
const venum = new VenumClient({ baseUrl: 'http://api.venum.dev' })
for await (const msg of venum.iteratePrices(['SOL', 'JUP'])) {
if (msg.type !== 'price') continue
if (!shouldTrade(msg.price.token, msg.price.priceUsd)) continue
const result = await venum.swap({
inputMint: 'SOL',
outputMint: 'USDC',
amount: solToLamports(1),
slippageBps: 50,
signer: walletSigner,
waitFor: 'confirmed',
})
console.log(result.signature, result.landed?.slot)
}The pieces every bot ends up rebuilding.
Each of these is a system someone on your team would otherwise write, maintain, and page for. Venum ships them as one product.
Pool state layer
Real-time decoded pool state over SSE. Replaces raw webhooks, raw streams, and custom account decoding layers.
Pricing layer
SSE token price streams from Pyth + DEX oracles. Replaces: Birdeye polling, Pyth Hermes wrappers, CoinGecko.
Routing & build layer
Multi-hop swap routing across major DEXes with a cleaner quote / build / submit flow.
Submission layer
Transaction landing and send flows without stitching raw RPC and custom relay logic together.
Confirmation layer
Transaction lifecycle status for bot-facing and user-facing flows. Replaces polling-heavy status checks and ad hoc confirmation logic.
Agent-ready
MCP server, Skills packs, and CLI expose the same stack to coding and trading agents without extra glue.
Four vendors, or one.
Typical Solana bot stacks integrate multiple vendors. Each adds another quota, key, SLA, and failure mode.
| Stack piece | Helius + Jupiter + Triton + Birdeye | Venum |
|---|---|---|
| Pool state streaming | Helius webhooks + custom decoder | Built in |
| Token price feeds | Birdeye / Pyth Hermes | Built in |
| Multi-DEX swap routing | Jupiter Quote API | Built in |
| Composable instructions | Reverse-engineer Jupiter blob | Built in |
| Bundle submission | Jito SDK + multi-region setup | Built in |
| Tx confirmation | getSignatureStatuses polling | Pre-confirmation tracking |
| Vendors to manage | 4–6 | 1 |
| Failure modes to debug | One per vendor | One |
Common questions.
What does the Trading Bot Backend actually replace?+
The four-vendor stack most teams stitch together: a paid RPC for reads, a price feed (CoinGecko / Pyth direct / their own poller), a per-DEX SDK collection for swap building, and a Jito or RPC-based submission layer. Venum collapses those into one API with one key — quotes, build, send, prices, and pool state — without the typical per-call billing.
Is the backend opinionated about strategy?+
No. Venum is execution infrastructure, not a bot. Your strategy logic, signing, and risk management stay in your code. Venum exposes the primitives — quotes, transaction building, real-time pool state, transaction landing — and you compose them however your bot needs.
Can I run my bot fully server-side without a frontend?+
Yes — that's the typical setup. Use `rpc.venum.dev` for any RPC reads your strategy needs, the Swap API for quote / build / send, and `/v1/stream/prices` or `/v1/stream/pools` for live state. No browser involved.
How does pricing work for high-volume bot traffic?+
Flat-rate per-minute caps, not per-call. Free / Starter / Pro tiers cover most bot workloads; Enterprise quote available if you exceed Pro's per-minute caps sustained. The cost predictability is one of the main reasons teams move off pay-per-call RPC.
Do I keep custody of keys and wallets?+
Yes, always. Venum returns unsigned transactions; your bot signs them. Private keys never leave your environment, the API never sees them.
Which DEXes are routed for swaps?+
Orca Whirlpool, Raydium CLMM / AMM v4 / CPMM, Meteora DLMM / Dynamic, PumpSwap, Phoenix, Saber, and more. The router picks the best venue per quote from streaming pool state, no per-DEX SDK to maintain on your side.
Ship a bot this week, not this quarter.
One key. The pieces you would otherwise build yourself.