One signed transaction. Two fast paths to Solana.
UltraSend accepts an already-signed Solana transaction and forwards those exact bytes through managed transaction-delivery infrastructure. Use the HTTPS endpoint when you want a simple request-and-receipt integration, or keep one authenticated QUIC connection open for a latency-sensitive sender. UltraSend does not simulate, rebuild, resign, or change your blockhash. Your application remains responsible for constructing a valid transaction and choosing its normal network and priority fees. Each account uses prepaid SOL balance. The relay charges 0.0002 SOL only after it durably commits billing and receives a transport acknowledgement; a forwarding failure reverses that charge. Relay acceptance is not a claim that the transaction landed or succeeded on-chain, so the dashboard tracks the delivery receipt and Solana confirmation as separate states. During the launch promotion, the normally $100 per month add-on is included for eligible paid-plan customers. Per-submission usage remains prepaid.
One submission, tracked through distinct states
delivery acknowledgement and on-chain confirmation are never presented as the same result
| Event | Type | Description | Frequency |
|---|---|---|---|
| Signed locally | event | Your application constructs and signs the complete Solana transaction before UltraSend sees it. | Very high |
| Validated | event | The relay validates size, encoding, account state, balance, and duplicate submission state. | Very high |
| Billing committed | event | The fixed relay submission fee is committed before the transaction is forwarded. | Very high |
| Transport acknowledged | event | The forwarding path acknowledges receipt and UltraSend returns an accepted receipt. | Very high |
| Observed on-chain | event | NoLimitNodes RPC independently checks whether the signature becomes processed, confirmed, or finalized. | High |
| Finalized result | event | The dashboard separates finalized success, finalized chain error, and transactions that were never observed. | High |
Pricing and protocol limits
last reviewed 2026-08-24
The monthly add-on is included. Relay usage is prepaid.
UltraSend normally costs $100 per month or is included with Enterprise. During the launch promotion, active Pro and Ultra customers receive the add-on at no monthly cost. When the promotion ends, NoLimitNodes will not begin charging automatically. Continuing under a paid add-on requires explicit approval.
The relay submission fee remains 0.0002 SOL. A 0.01 SOL balance covers approximately 50 accepted submissions, 0.1 SOL covers 500, and 1 SOL covers 5,000. Normal Solana transaction and priority fees are separate.
- Monthly add-on during launch
- $0
- Accepted submission
- 0.0002 SOL
Choose the transport that fits your sender.
HTTPS
The smallest integration surface. POST one Base64-encoded signed transaction and receive a structured receipt. Use bounded timeouts and resend the exact same signed bytes after an ambiguous network failure.
Persistent QUIC
Keep one authenticated connection open for latency-sensitive systems. Open one bidirectional stream per transaction and read the receipt without repeating the handshake.
Accepted and landed are different states.
UltraSend bills the delivery attempt after durable accounting and a forwarding acknowledgement. Invalid transactions, disabled accounts, insufficient balance, and duplicates are not charged. If forwarding fails, the charge is reversed.
A transaction can be accepted by the relay and still expire, lose blockhash validity, or fail on-chain. Those accepted submissions remain charged. The dashboard therefore shows relay outcome and on-chain status side by side instead of calling an acknowledgement “landed.”
Read the retry and error guide before putting UltraSend in a production send loop.
Frequently asked questions
Related products
Send signed transactions through UltraSend
Activate the included launch add-on from your dashboard, fund a prepaid balance, and choose HTTPS or persistent QUIC.