Solana transaction landing, with a record of every send
Send the transactions you already sign to the Apex endpoint nearest your servers. Apex forwards them to the current leader through our partner validators, TPU or Jito, and records the signature, slot, latency and tip of each one.
Need an access code? Ask us for one.
- POST https://api.mainnet-beta.solana.com+ POST https://fra.apex.orbitflare.com/?api-key=apex_…{
"jsonrpc": "2.0",
"id": 1,
"method": "sendTransaction",
"params": [
"<signed transaction, tip included>",
{ "encoding": "base64" }
]
}How Solana transaction landing works with Apex
Apex answers the same sendTransaction call your code already makes. Switching is a URL change and a tip transfer inside your transaction.
Get access
Sign in, open Apex in the dashboard and enter your access code.
Copy your key and endpoint
Your apex_ key and the URL for every region are on the Apex page. Add an IP whitelist if you want one.
Send as you do today
Point sendTransaction at the nearest endpoint, with a transfer to an Apex tip account inside the transaction.
Check what landed
The Transactions page lists every send with its status, slot, latency and tip. Search by signature.
What the Apex transaction sender includes
Everything on the platform side of sending: keys, limits, tips and a record of every transaction.
Regional endpoints
Send from the endpoint closest to the servers that sign your transactions: Frankfurt, Amsterdam, London, New York City, Salt Lake City, Singapore, Tokyo, Šiauliai and Dublin.
API key with an IP whitelist
One apex_ key per account, created at signup. Leave it open or lock it to the addresses your bots run from, and regenerate it whenever you need to.
Tips inside your transaction
The tip is a transfer to a published Apex tip account in the transaction you sign, so it only moves if the transaction lands. Dedicated tip accounts are available on request.
Per-account TPS limit
Enforced at the endpoint on every request. Tell us what you need and we raise it, with no plan change.
Per-transaction analytics
Every send is recorded with its signature, status, endpoint, slot, tip, first-seen latency and confirmed latency. Filter by status, endpoint, latency and time range.
Send options
JSON-RPC sendTransaction or sendBundle, HTTP endpoints for raw bytes and batches, or QUIC on a persistent connection. MEV protection skips leaders on the Shield blocklist, and you set the retry budget per request.
Who uses Apex
Anyone whose result depends on a transaction reaching the leader, and who wants a record of whether it did.
Traders
Keep your sendTransaction code, send from the region nearest your servers, and check first-seen and confirmed latency for every order.
MEV searchers
Send transactions and bundles to the current leader, turn on MEV protection per request, and tie each send to its slot and tip.
High-volume bots
Lock your key to your bots' IP addresses, send over QUIC or HTTP batches, and ask us to raise your TPS limit as volume grows.
Apex endpoint regions
Pick the endpoint closest to the machines that sign your transactions. Each region has its own URL in your dashboard.
SLCSalt Lake City
slc.apex.orbitflare.com
- NYC
New York City
nyc.apex.orbitflare.com
DUBDublin
dub.apex.orbitflare.com
LONLondon
lon.apex.orbitflare.com
AMSAmsterdam
ams.apex.orbitflare.com
FRAFrankfurt
fra.apex.orbitflare.com
SQQŠiauliai
sqq.apex.orbitflare.com
SGPSingapore
sgp.apex.orbitflare.com
TYOTokyo
tyo.apex.orbitflare.com
Run a Solana validator? Partner with us
We work with validators on transaction landing. If you operate a validator and want to hear what a partnership with OrbitFlare looks like, get in touch.
Apex FAQ
Access, keys, tips and latency. For anything not covered here, ask us.
A service that takes a transaction you have already signed and gets it to the validator that is producing blocks right now, the current leader. Apex receives it at a regional endpoint and forwards it through our partner validators, the leader's TPU port or Jito, then records whether and when it landed.
Two things change. You point sendTransaction at an Apex endpoint instead of your current RPC URL, and the transaction you sign includes one transfer to an Apex tip account. The request body is the standard Solana JSON-RPC call.
Sign in or create an account, open Apex in the dashboard and enter your access code. If you do not have a code yet, contact us and tell us what you plan to send.
Each transaction carries exactly one tip: a transfer to one of the published Apex tip accounts, at or above your tier's minimum. The tip is part of your transaction, so if the transaction does not land the transfer never runs and you pay nothing. A transaction with no tip, two tips or a tip below the minimum is rejected before it is sent. The docs list the tip accounts and the current minimum.
Both are measured from the moment our endpoint receives your transaction. First-seen latency stops when the transaction is first observed on chain at processed commitment. Confirmed latency stops when a supermajority of stake has confirmed it.
One per account. It is created when you sign up, so it is ready as soon as you open Apex. You can restrict it to up to 50 IP addresses and regenerate it from the dashboard at any time.
Apex has endpoints in Frankfurt, Amsterdam, London, New York City, Salt Lake City, Singapore, Tokyo, Šiauliai and Dublin. Use the one closest to the servers that sign your transactions. Your dashboard lists the full URL for each region.
Every account starts with a limit of 5 transactions per second. If you need more, contact us and we will raise the limit on your account.
Start sending with Apex
Sign in, open Apex, and send your first transaction with the API key already on your account.