A dedicated submission path
Send signed transactions through Apex. Regional ingress routes them toward the leader through partner validators, direct TPU or Jito.
OrbitFlare products / Apex
The transaction layer
in your Solana stack.
Read the chain. Respond to the signal. Send your transaction. Apex connects the last step to the rest of your OrbitFlare infrastructure, with dedicated transaction submission and a record of what happened next.
Start with 5 TPS. Contact us to request a higher limit for larger volumes.
Where Apex fits
A record of every send
Inspect transaction signatures, slots, tips and latency in your OrbitFlare dashboard. Track first-seen and confirmed outcomes separately.
Part of your existing stack
Keep your RPC for reads, blockhashes, simulation and confirmation. Apex handles submission using the familiar sendTransaction method.
Read. React. Submit.
01 / Solana RPC
Fetch account state and blockhashes before signing. After Apex accepts a transaction, use your RPC to confirm its signature and check for execution errors.
Explore Solana RPC nodes02 / Streaming data
Feed trading and monitoring systems with chain updates. Choose the data stream your application needs, then construct and sign transactions in your own stack.
Explore Solana gRPC03 / Apex
Include a qualifying Apex tip, sign, and submit. Choose global routing or a named regional endpoint, then inspect the transaction in your dashboard.
Choose an Apex endpointBuild your next send with Apex.
Find endpoint addresses, submission examples, tip requirements and a ready-to-copy prompt for your coding assistant on the Apex site.