APEX

SOLANA TRANSACTION LANDING

Solana transactions.
Built to land.

OrbitFlare Apex is a Solana transaction landing service with global and regional endpoints, leader-directed routing, and visibility into every send.

Start with Apex Explore the integration

Your transactions. Your signing keys. Our landing infrastructure.

Building with an AI assistant? Get the integration prompt →

+ THE PATH TO YOUR NEXT BLOCK 01 — TRANSACTION ROUTING

Your app Signed transaction

Apex Regional endpoint

Partner validators Direct TPU Jito

The next block Current leader

→ Leader-directed routing Conceptual flow · block inclusion is not guaranteed

Built for the way
you execute.

Trading bots Market makers Trading terminals DeFi protocols

THE APEX ADVANTAGE

From send
to seen on-chain.

Your strategy does the hard work.
Give it a dedicated path to the leader, and a clear record of what happened next.

01 / ROUTING

Closer to the leader.

Submit to a regional endpoint near your servers. Apex forwards your transaction through partner validators, direct TPU or Jito.

02 / VISIBILITY

Know how every send landed.

Trace the signature, slot, tip and latency of each transaction. Separate first-seen from confirmed, right in your dashboard.

Transaction activity ILLUSTRATIVE

Signature Status Commitment

5wQk…a9Lf ✓ Landed Confirmed

8nRm…t2Xs ✓ Landed Processed

3pJv…e7Kn → Accepted Pending

03 / INTEGRATION

A familiar way to send.

Keep your JSON-RPC workflow. Send through Apex with one qualifying tip. Keep your regular RPC for reads and confirmation.

See the request

04 / CONTROL

Your key. Your boundaries.

Restrict API access by IP, regenerate your key, and view your account’s throughput limit from one place.

Open the dashboard

Illustrative product flows

MADE FOR YOUR STACK

Same method.
New destination.

You already know sendTransaction.
Put Apex behind it.

01

Get your API key.

Sign in to OrbitFlare and open Apex to get your API key and regional endpoints.
02

Choose your endpoint.

Copy your API key and the regional URL closest to your signing servers.
03

Add a tip. Sign. Send.

Include exactly one Apex tip at or above your tier’s minimum, then submit your signed transaction.

Keep your regular Solana RPC for blockhashes, account reads, simulation and confirmation.

Read the integration guide

POST Your regional endpoint · x-api-key header

# Already signed, with one qualifying Apex tip.
# APEX_RPC is your regional dashboard endpoint.
curl "$APEX_RPC" \
  -H 'Content-Type: application/json' \
  -H "x-api-key: $APEX_API_KEY" \
  --data @- <<EOF
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "sendTransaction",
  "params": [
    "$SIGNED_TRANSACTION_BASE64",
    { "encoding": "base64" },
    false
  ]
}
EOF

A returned signature means accepted, not confirmed. Confirm on your Solana RPC.

More ways to send HTTP · Bundles · QUIC

BUILD WITH YOUR AI ASSISTANT

One prompt.
Your stack, connected.

Give your coding assistant the docs, the requirements and a clear starting point for integrating Apex.

For Cursor, Claude Code, Codex, or the assistant you already use.

apex-integration.md READY TO COPY

Integrate OrbitFlare Apex into this project. Inspect the existing stack, read the current Apex docs, and implement transaction submission with one qualifying tip…

Official docs Tip requirements Confirmation handling

Copy, paste into your assistant, then let it work with your codebase.

Read the full prompt

Integrate OrbitFlare Apex transaction submission into this project.

First inspect the existing language, Solana SDK, transaction construction and signing flow. Adapt the integration to the current stack rather than replacing it.

Read the current official documentation before coding:
- Quickstart: https://docs.orbitflare.com/apex/quickstart
- Sending transactions: https://docs.orbitflare.com/apex/sending-transactions
- Tips: https://docs.orbitflare.com/apex/tips
- Regional endpoints: https://docs.orbitflare.com/apex/endpoints
- Errors and rate limits: https://docs.orbitflare.com/apex/errors-and-rate-limits

Requirements:
1. Use Apex only for transaction submission. Retain the existing Solana RPC for blockhashes, account reads, simulation and confirmation.
2. Configure the regional endpoint and API key through server-side environment variables, such as APEX_RPC and APEX_API_KEY. Use the documented x-api-key header. Never expose API keys or signing secrets in client bundles, source control or logs.
3. Fetch current tip accounts using getTipAccounts. Before signing, include exactly one top-level SystemProgram transfer to a published Apex tip account, funded by a signer. Use a static account key for the tip recipient, not an address lookup table. Do not add a separate Jito tip.
4. The standard minimum Apex tip is 0.001 SOL (1,000,000 lamports). Verify the actual floor for the configured API key's tier and meet or exceed it. Keep the Apex tip separate from Solana network and priority fees.
5. Preserve the application's signing and custody model. Submit the signed base64 transaction using JSON-RPC sendTransaction and the current documented parameters. Explicitly configure the mevProtect option based on the application requirements; do not invent endpoint URLs or SDK methods.
6. Treat a returned signature as acceptance only. Confirm it through getSignatureStatuses on the regular Solana RPC, and handle execution errors, blockhash expiry, timeouts, rate limits and JSON-RPC/HTTP errors. Avoid blind retries that could duplicate a business operation.
7. Add focused tests using mocked requests and document the required environment variables and integration steps. Do not broadcast real transactions as part of this implementation task.

Deliver the code changes, a concise explanation of the send/confirmation flow, and any remaining configuration needed. If a required product detail is unclear in the current docs, ask rather than guessing.

Download prompt

STANDARD MINIMUM TIP

0.001 SOL

1,000,000 lamports / transaction

One Apex tip.
All three landing paths.

BUILT INTO THE TRANSACTION

Your tip moves
when your transaction lands.

The Apex tip is part of the transaction you sign. If it is rejected, expires or is dropped, you pay no Apex tip.

Your key’s tier may have a different minimum. Solana network and priority fees are separate.

How Apex tips work

REGIONAL INGRESS GLOBAL ROUTING. NINE NAMED REGIONS.

Send from
closer to home.

Use global routing to select a nearby endpoint, or choose a named region for a fixed host. Every region routes toward the upcoming leaders.

Global endpoint

One address. Your nearest region.

Geolocated routing selects the Apex endpoint nearest your sender.

http://global.apex.orbitflare.com

Europe 05

🇩🇪Frankfurt FRA

http://fra.apex.orbitflare.com
🇳🇱Amsterdam AMS

http://ams.apex.orbitflare.com
🇬🇧London LON

http://lon.apex.orbitflare.com
🇮🇪Dublin DUB

http://dub.apex.orbitflare.com
🇱🇹Šiauliai SQQ

http://sqq.apex.orbitflare.com

North America 02

🇺🇸New York NYC

http://nyc.apex.orbitflare.com
🇺🇸Salt Lake City SLC

http://slc.apex.orbitflare.com

Asia Pacific 02

🇸🇬Singapore SGP

http://sgp.apex.orbitflare.com
🇯🇵Tokyo TYO

http://tyo.apex.orbitflare.com

Select a transport, then copy an endpoint.

BEFORE YOUR FIRST SEND

A few things
worth knowing.

Working on something specific?

Talk to the team

What does Apex actually do?

Apex takes a Solana transaction you have already signed, receives it at a regional endpoint, and forwards it toward the current leader through partner validators, direct TPU or Jito. You can then inspect how it landed in your dashboard.

How is Apex different from a Solana RPC?

Apex is a transaction sender, not a full RPC service. Use Apex to submit signed transactions; keep your regular Solana RPC for account reads, recent blockhashes, simulation and confirmation. Read the Apex integration quickstart.

How do Apex tips differ from priority fees?

An Apex tip is a transfer inside your transaction to a published Apex tip account. The standard minimum is 0.001 SOL; your key’s tier may differ. Solana network and priority fees are separate. Include exactly one qualifying Apex tip before signing. Read the Apex tip requirements.

Should I use the global endpoint or a named region?

Use global.apex.orbitflare.com for geolocated routing to a nearby Apex endpoint. Choose a named region when you want a fixed host near your signing servers. Both submit through Apex’s landing infrastructure. Choose and copy an Apex endpoint.

Do I need to rewrite my integration?

For JSON-RPC, change your submission endpoint and include exactly one transfer to a published Apex tip account before signing. Authenticate with your API key. Your request still uses the standard sendTransaction method. Keep your regular RPC for blockhashes, reads, simulation and confirmation. Follow the docs for your tier’s minimum tip and supported options.

How do I get started?

Sign in to your OrbitFlare account and open Apex. Copy your API key and a regional endpoint, then follow the quickstart or use the integration prompt on this page. Contact the team if you need help choosing your setup.

What is the starting TPS limit?

All users start with 5 transactions per second (TPS). If you need more throughput for larger volumes, contact our team to request a higher limit.

Does a signature mean my transaction landed?

No. It means Apex accepted the transaction. Confirm the signature with getSignatureStatuses on your regular Solana RPC and check for execution errors. Follow the submission and confirmation quickstart.

Does Apex guarantee block inclusion?

No. Landing depends on transaction validity, network conditions, fees and leader behavior. Apex provides submission infrastructure and transaction visibility; it does not guarantee a particular slot or landing time.

What do the latency measurements mean?

Both begin when Apex receives your transaction. First-seen latency ends when the transaction is observed on-chain at processed commitment. Confirmed latency ends when a supermajority of stake has confirmed it.

YOUR STRATEGY. OUR INFRASTRUCTURE.

Make your
next move count.

Give your Solana transactions a dedicated path to landing.

Start with Apex Talk to the team

Built for Solana · Built by OrbitFlare

Solana transactions. Built to land.

From sendto seen on-chain.

Closer to the leader.

Know how every send landed.

A familiar way to send.

Your key. Your boundaries.

Same method. New destination.

Get your API key.

Choose your endpoint.

Add a tip. Sign. Send.

One prompt. Your stack, connected.

Your tip moveswhen your transaction lands.

Send from closer to home.