Overview
Pricing update: Sender Max now uses a 0.001 SOL minimum tip. This
enters you into a priority tip buffer for top of block — tip more to land first. The cost-optimized
SWQOS-only tier remains at 0.000005
SOL.
No Credits
Available on all plans without consuming API credits. You pay per send with
a SOL tip.
Multi-Path Routing
Submits across all pathways (Helius, Jito, Harmonic, Rakurai, etc.) for the fastest possible inclusion
Global Endpoints
HTTPS endpoint auto-routes to the nearest location for frontends, regional
HTTP for backends
50 TPS (Default)
Need more? Request higher limits and custom tip arrangements
Choose your tier
Sender offers two tiers. Both are low-latency and credit-free — the difference is how many pathways your transaction takes and the minimum tip required.Tips between 0.000005 SOL and 0.001 SOL are accepted but do not enter the
priority tip buffer — they are sent on a best-effort basis through fewer
pathways. To get buffer priority and every routing pathway, tip at least 0.001
SOL.
Sender Max (fastest landing)
Routed across every pathway and entered into a priority tip buffer for the
most competitive submissions. Handles both transactions and bundles.
SWQOS-only (cost-optimized)
Lowest tip, single fast path. Add
?swqos_only=true to any endpoint URL.Quickstart Guide
Ready to submit your first ultra-low latency Solana transaction? This guide gets you started in minutes. The best part: you don’t need any paid plan or special access — Sender is available to all users and doesn’t consume API credits. The example below uses the Sender Max tier (0.001 SOL tip). For the lowest-tip option, see SWQOS-only.Create Your Free Helius Account
Start by creating your free account at the Helius Dashboard. Sender is available on all plans, including the free tier, and doesn’t consume any API credits.
Get Your API Key
Go to the API Keys section and copy your key. Use this for getting blockhashes and transaction confirmation. Sender will handle transaction submission.
Send Your First Transaction
Let’s send a simple SOL transfer using Sender. This example includes the required tip and priority fee, and skips preflight for lower latency (optional).
- @solana/web3.js
- @solana/kit
Success! Understanding What Happened
You’ve successfully submitted a transaction via Sender! Here’s what made it work:
- No credits consumed: Sender is credit-free for all users
- Multi-path routing: Your transaction was submitted across all pathways (Helius, Jito, Harmonic, Rakurai, etc.) simultaneously
- Required tip: A 0.001 SOL tip enters the priority tip buffer and uses every routing pathway. See tiers for the lower-tip SWQOS-only option
- Priority fee: Signals validators your willingness to pay for priority processing
- Skipped preflight (optional): Trades validation for speed — Sender also supports preflight checks
Requirements
skipPreflight is optional — Sender supports preflight checks. Set
skipPreflight: true to trade validation for lower latency.Tips and priority fees
All transactions submitted through Sender must include both a tip and a priority fee:- Tip: A SOL transfer to a designated tip account. Minimum 0.001 SOL for Sender Max, or 0.000005 SOL for SWQOS-only.
- Priority fee: Compute unit pricing via
ComputeBudgetProgram.setComputeUnitPriceto prioritize your transaction in the validator queue.
Designated Tip Accounts (mainnet-beta)
Designated Tip Accounts (mainnet-beta)
Why both are required
- Tips: Give you access to all of Sender’s routing pathways (Helius, Jito, Harmonic, Rakurai, etc.) and the priority tip buffer
- Priority fees: Signal to validators your willingness to pay for priority processing through Solana’s native prioritization system
- Together: Tips maximize the pathways your transaction can take, while priority fees improve its priority with validators — together they maximize inclusion probability
Endpoints
Sender endpoints are available in multiple configurations depending on your use case:- Frontend/Browser Applications
- Backend/Server Applications
- Connection Warming
Recommended for frontend applications to avoid CORS issues:
The HTTPS endpoint resolves CORS preflight failures that occur with
browser-based applications when using the regional HTTP endpoints. This
endpoint automatically routes to the nearest location for optimal
performance. Use this for frontend/browser use cases.
Connection Warming
For applications with long periods between transaction submissions, use the ping endpoint to maintain warm connections and reduce cold start latency. The ping endpoint accepts simple GET requests and returns a basic response to keep connections alive:Use connection warming when your application has gaps longer than 5 seconds
between transactions to maintain optimal submission latency.
Request Format
Sender accepts two methods on the same endpoint. Every submission must include both a tip and a priority fee; skipping preflight is optional (it lowers latency).sendTransaction
Submit a single transaction. It must contain both a SOL transfer with the minimum tip to a designated tip account and a compute unit price instruction — without both, it will be rejected.sendTransaction example.
sendBundle
Submit up to 4 fully-signed transactions for atomic, all-or-nothing execution. At least one transaction must carry the tip.MEV Protect (optional)
To route around validators statistically linked to sandwich attacks, add themev-protect=true query parameter to the endpoint URL. It works on both Sender tiers and on both sendTransaction and sendBundle, with no changes to your request body.
API Reference
View the complete Sender API reference with request/response schemas and
parameters.
Rate Limits and Scaling
- Default Rate Limit: 50 transactions per second
- No Credit Usage: Sender transactions don’t consume API credits from your plan
- Higher Limits: Professional plan users can request significant rate limit increases to support high-throughput trading applications
Custom TPS with API Key Authentication
This section is only relevant if you have been granted increased TPS limits
and received an API key from the Helius team. Standard users can skip this
section.
- Frontend/Browser Applications
- Backend/Server Applications