Guides

Endpoints & Regions

Trading Boost has nodes deployed across four global regions. Choose the region closest to you for lowest latency.

Endpoint List

RegionHTTP (Recommended, faster)HTTPS
Singaporehttp://booster-sg.zan.top/node/v1/solana/mainnet/{apiKey}/tipshttps://booster-sg.zan.top/node/v1/solana/mainnet/{apiKey}/tips
Hong Konghttp://booster-hk.zan.top/node/v1/solana/mainnet/{apiKey}/tipshttps://booster-hk.zan.top/node/v1/solana/mainnet/{apiKey}/tips
Germanyhttp://booster-de.zan.top/node/v1/solana/mainnet/{apiKey}/tipshttps://booster-de.zan.top/node/v1/solana/mainnet/{apiKey}/tips
North Americahttp://booster-us.zan.top/node/v1/solana/mainnet/{apiKey}/tipshttps://booster-us.zan.top/node/v1/solana/mainnet/{apiKey}/tips
Global Gatewayhttps://api.zan.top/node/v1/solana/mainnet/{apiKey}/tipshttps://api.zan.top/node/v1/solana/mainnet/{apiKey}/tips

MEV Protection

Append ?anti-mev=true to any endpoint:

http://booster-sg.zan.top/node/v1/solana/mainnet/<AK>/tips?anti-mev=true

Standard RPC Endpoints (Read Operations)

Use standard ZAN RPC endpoints for all read-type RPC methods (getLatestBlockhash, getBalance, simulateTransaction, etc.):

https://api.zan.top/node/v1/solana/mainnet/<YOUR_API_KEY>

Trading Boost endpoints only support sendTransaction.

Protocol Selection

ProtocolUse CaseDescription
HTTPBackend services, bots, latency-sensitive scenariosEliminates TLS handshake overhead; recommended for backend
HTTPSFrontend/browser applications, security/compliance requirementsEncrypted transmission; suitable for user-facing applications

Network Selection Recommendations

ProtocolUse CaseDescription
HTTPBackend services, bots, latency-sensitive scenariosEliminates TLS handshake overhead; recommended for backend
HTTPSFrontend/browser applications, security/compliance requirementsEncrypted transmission; suitable for user-facing applications
📘

Note:

Testnet: Not currently supported. Trading Boost is only available on Solana Mainnet.


Updated about 2 hours ago