Three Paths at Once
Stake-weighted validator clients, Jito bundles, and direct TPU
8 Regions
Apex endpoints in Europe, the US, and Asia
Pay Only on Landing
The tip lives inside your transaction
URL Swap
Standard
sendTransaction, plus binary HTTP and QUICApex is in beta and invite only. Once your account is enabled, create API keys in the OrbitFlare dashboard under Dashboard > Apex. To request access, reach out on Discord.
What Apex Does
Apex is OrbitFlare’s Solana transaction landing service. You send one signed transaction that carries a tip. The Apex endpoint that receives it races the transaction to the current and upcoming leaders through three paths at the same time:
Whichever path gets there first wins. The others are deduplicated by signature, so your transaction executes once. Apex keeps retrying until the transaction lands or its blockhash expires.
How a Send Works
1
Build and sign
Build your transaction as usual and add one SystemProgram transfer to an Apex tip account. Set a compute unit limit and price too. See Tips.
2
Send to the nearest Apex endpoint
Use JSON-RPC
sendTransaction, the binary HTTP routes, or a persistent QUIC connection. See Sending transactions.3
Apex validates and races it
The endpoint checks your API key, rate limit, the transaction, and the tip, then sends it down all three paths and retries until it lands or the blockhash expires.
4
Confirm
Accepted does not mean landed. Poll
getSignatureStatuses on any Solana RPC to confirm. See Best practices.Why the Tip Costs Nothing on a Miss
The tip is an instruction inside your transaction. If the transaction never lands, the tip never executes, so you pay nothing. There is no subscription fee per send and no charge for a rejected or expired transaction.Transports
The transport does not change routing or priority. The tip and your priority fee do.
Explore the Docs
Quickstart
Send your first tipped transaction with cURL, JavaScript, Python, or Rust.
Endpoints and regions
Hostnames, ports, and how to choose an Apex endpoint.
Tips
The tip rule, tip accounts, floors, and how the tip is used.
Sending transactions
JSON-RPC, HTTP binary and batch, and QUIC.
Bundles
Atomic groups of 1 to 4 transactions.
Rust client
The
apex-sender-client crate: QUIC, 0-RTT, and HTTP helpers.