Skip to main content

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.
Sender Max is the highest-performance Helius Sender tier, built for submissions that need to land ahead of the competition. It routes your submission across every available high-speed pathway and enters it into a priority tip buffer that favors the highest tips. Sender Max handles both single transactions and bundles. Both use all pathways (Helius, Jito, Harmonic, Rakurai, etc.) — the only difference is the payload: submit one transaction with sendTransaction, or up to four with sendBundle. This tier requires a minimum tip of 0.001 SOL. For cost-optimized sending on a single path, use the SWQOS-only tier instead.

Fastest Landing

Routed across every high-speed pathway for the highest probability of landing

Priority Tip Buffer

Your submission enters a priority tip buffer that prioritizes the highest-tipping submissions — tip more to land first

No Credits

Available on all plans without consuming API credits

0.001 SOL Minimum Tip

The minimum tip required to enter the priority tip buffer and use every routing pathway

How it works

When you tip at least 0.001 SOL, your submission — whether a single transaction or a bundle — is routed across every available high-speed pathway and entered into a priority tip buffer. The buffer favors the highest tips, so raising your tip above the minimum increases your chance of landing first.
Tips below 0.001 SOL do not enter the priority tip buffer — they are sent on a best-effort basis through fewer pathways. For predictable low-latency sending at a lower tip, use the SWQOS-only tier (0.000005 SOL).

When to use Max

Good fit

Highly contested accounts, competitive token launches, liquidations, and any transaction where landing first is worth a higher tip.

Consider SWQOS-only instead

Cost-sensitive or high-volume flows where a single fast path lands reliably.

Requirements

Every Sender Max submission must include:
  • Tip: A SOL transfer of at least 0.001 SOL to a designated tip account. In a bundle, at least one transaction must carry the tip.
  • Priority fee: A compute unit price instruction with a priority fee of at least 5,000 lamports. See Priority fees.
Skipping preflight (skipPreflight: true) is optional but recommended — Preflight checks increase latency.
Transactions missing the tip or priority fee will be rejected. For bundle-specific rules, see Bundles.

Priority fees

Every transaction must include a priority fee of at least 5,000 lamports, and we recommend at least 10,000 lamports for more reliable landing. The tip enters your transaction into the priority tip buffer, while the priority fee raises its priority in the validator’s scheduler — together they maximize your chance of landing. Set a priority fee with a compute unit price instruction. Your total priority fee is the compute unit price (in micro-lamports) multiplied by your compute unit limit:
Use the Helius Priority Fee API for real-time fee recommendations based on current network conditions.

Endpoints

Use the global HTTPS endpoint for frontends, or the regional HTTP endpoint closest to your servers for backends. Frontend / browser (global HTTPS):
Backend / server (regional HTTP):
See the Sender endpoints reference for connection warming and details.
Want to avoid validators linked to sandwich attacks? Add mev-protect=true to the endpoint URL — it works for both sendTransaction and sendBundle: https://sender.helius-rpc.com/fast?mev-protect=true.

Code Example

For competitive transactions, the 0.001 SOL minimum is unlikely to be competitive. Price your tip closer to the value of the transaction you’re trying to land — the more a successful landing is worth to you, the higher you should tip. The minimum is a floor, not a target.

Bundles

A bundle is just another payload Sender Max accepts. Submit up to 4 fully-signed transactions and they execute atomically (all-or-nothing) in order, entered into the same priority tip buffer as a single transaction — the buffer prioritizes the highest-tipping bundles for the fastest landing.
Provide only the 0.001 SOL Sender tip. Sender Max routes your bundle across every high-speed pathway and adds any pathway tips on your behalf — you don’t add a separate Jito tip, use Jito tip accounts, or set the jito-region header. Those apply only to basic bundles.

Requirements

  • Up to 4 transactions, fully signed. They execute sequentially and atomically — if any fails, the whole bundle is rejected.
  • Tip: at least one transaction must transfer at least 0.001 SOL to a designated Sender tip account. This is the same Sender tip used for single transactions — Helius adds any pathway tips (including Jito) for you, so you don’t add a separate Jito tip.
  • Priority fee: each transaction must include a priority fee of at least 5,000 lamports.

Submit

Send to the Sender endpoint with method: "sendBundle". Use the global HTTPS endpoint for frontends, or any regional endpoint for backends — all Sender regions are supported.

Track landing

Track a bundle the same way you track a single transaction — by watching for each transaction’s signature to land. Because the bundle is atomic, confirming any one transaction means the whole bundle landed. You do not use getBundleStatuses or a bundle ID. Use whichever method fits your stack:

Best Practices

  • Endpoint selection: Use https://sender.helius-rpc.com/fast for frontend apps to avoid CORS issues. For backend apps, use the regional HTTP endpoint closest to your servers.
  • Dynamic tipping: Raise your tip above 0.001 SOL for highly contested transactions to improve your priority in the tip buffer.
  • Connection warming: Use the /ping endpoint during idle periods longer than 5 seconds.
  • Priority fees: Use the Helius Priority Fee API for real-time recommendations.
  • Retries: Set maxRetries: 0 and implement your own retry logic.

Sender Overview

Shared concepts: endpoints, connection warming, rate limits, and custom TPS.

SWQOS-Only Tier

Cost-optimized low-latency sending on a single path (0.000005 SOL min tip).

MEV Protect

Route around validators statistically linked to sandwich attacks.