Solana Trader API

The Solana Trading API provides blazing-fast transaction propagation on Solana network, as well as additional features, such as MEV protection while utilizing Bloxroute's infrastructure under the hood.

To use the API along with RPC Fast's dedicated node, you need to purchase a Professional or any other tier from bloXroute directly: https://bloxroute.com/pricing/. Select a tier based on your application's expected load profile. Below, you'll find an instruction on how to use the integration.

How to enable Trader API?

• Add blxr_enable=1 query arg, i.e. https://solana-rpc.rpcfast.net/?blxr_enable=1

• Or add /trader to request path, i.e. https://solana-rpc.rpcfast.net/trader

Authentication options

• via HTTP header X-TOKEN: your_token

• via HTTP query argument api_key=your_token

Submit transaction via API

Example request with curl

curl -XPOST -H 'X-TOKEN: your_token' \
https://solana-rpc.rpcfast.net/trader?tx_submit_mode=fastest&tip_amount=1000000 -d '
{
	"jsonrpc": "2.0",
	"method": "sendTransaction",
	"params": [
		"your_signed_transaction",
		{
			"encoding": "base64"
		}
	],
	"id": 1
}'

Query parameters

Parameter	Description	Allowed values	Required
blxr_enable	Enable Trader API	1	yes, except when using /trader endpoint
tx_submit_mode	Transaction submission mode	fastest, mev_protect, balanced	no
tip_amount	Tip amount in Lamports	min. 1000000	yes, when tx_submit_mode is defined
fallback	Whether to fallback to default sendTransaction on reaching CU limit	true, false	no

Transaction submission modes

Default mode

The default transaction submission mode is used when you omit the tx_submit_mode argument.

Even in default mode, you'll get faster transaction propagation speed compared to standard RPC providers, because request is routed through BloXroute's BDN.

Modes which require additional tip

These transaction submission modes require an additional tip (min. 0.001 SOL) for every request.

Mode	Description
fastest	Transaction is send to staked RPCs allowing for the fastest propagation
mev_protect	Enable front-running protection in cost of slower transaction propagation
balanced	Balanced mode between speed and front-running protection

Tip for paid submission modes

Tip should be specified in lamports (1 SOL = 1,000,000,000 lamports).

The minimum required tip amount is 0.001 SOL or 1,000,000 Lamports.

Setting a higher tip will increase propagation speed.

To check most up-to-date recommended tip amount, consider subscribing to websocket endpoint.

Transaction priority fee

Prioritization Fees are an optional fee, priced in micro-lamports per Compute Unit (e.g. small amounts of SOL), appended to transactions to make them economically compelling for validator nodes to include in blocks on the network.

Please check official Solana documentation on how to add priority fee to your transaction.

To receive up-to-date priority fees consider subscribing to priority fee stream websocket.

Pricing

• requests with default submit mode (no tip required) - 1 CU per request

• requests which require tip - 25 CU per 1,000,000 lamports.

Package Price	Total CU included	Requests with minimal tip	Requests without tip
0.5 SOL	12,500 CU	500 requests	12,500 requests
2 SOL	50,000 CU	2,000 requests	50,000 requests
5 SOL	125,000 CU	5,000 requests	125,000 requests

If you need bigger amount of requests, please contact us.

When you reach your CU limit, sending transactions via Trader API will become unavailable and we will respond with an error, like this:

{
	"jsonrpc": "2.0",
	"id": 1,
	"error": {
		"code": -32600,
		"message": "You have reached CU limit. Please contact RPCFast support, or add fallback=true parameter to send the txs through the RPC node on reaching CU limit."
	}
}

If you still want to forward transaction to standard Solana's sendTransaction even when CU limit reached, you can add fallback=true query argument.