Trading Bot Backend

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.

APIs to integrate
1
not 4+
Vendors replaced
4+
typical stack
Integration surface
1
one SDK, one key
Feeds
Realtime
pool + price SSE
Code sample

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.

bot-loop.ts
// 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)
}
Every layer

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.

01 · POOL STATE

Pool state layer

Real-time decoded pool state over SSE. Replaces raw webhooks, raw streams, and custom account decoding layers.

02 · PRICES

Pricing layer

SSE token price streams from Pyth + DEX oracles. Replaces: Birdeye polling, Pyth Hermes wrappers, CoinGecko.

03 · ROUTING

Routing & build layer

Multi-hop swap routing across major DEXes with a cleaner quote / build / submit flow.

04 · SUBMIT

Submission layer

Transaction landing and send flows without stitching raw RPC and custom relay logic together.

05 · CONFIRM

Confirmation layer

Transaction lifecycle status for bot-facing and user-facing flows. Replaces polling-heavy status checks and ad hoc confirmation logic.

06 · AGENT

Agent-ready

MCP server, Skills packs, and CLI expose the same stack to coding and trading agents without extra glue.

The stitched stack vs one API

Four vendors, or one.

Typical Solana bot stacks integrate multiple vendors. Each adds another quota, key, SLA, and failure mode.

Stack pieceHelius + Jupiter + Triton + BirdeyeVenum
Pool state streamingHelius webhooks + custom decoderBuilt in
Token price feedsBirdeye / Pyth HermesBuilt in
Multi-DEX swap routingJupiter Quote APIBuilt in
Composable instructionsReverse-engineer Jupiter blobBuilt in
Bundle submissionJito SDK + multi-region setupBuilt in
Tx confirmationgetSignatureStatuses pollingPre-confirmation tracking
Vendors to manage4–61
Failure modes to debugOne per vendorOne

Ship a bot this week, not this quarter.

One key. The pieces you would otherwise build yourself.