What is the Syncro Sender dedicated (private) endpoint, and how does it differ from the public endpoint?
Dedicated endpoint overview
The Syncro Sender dedicated endpoint is a private, API-key-authenticated access point designed for production trading systems and applications. It provides higher throughput, dedicated infrastructure, and additional functionality beyond what the public endpoint offers.
Key differences from the public endpoint
Authentication: the dedicated endpoint requires an API key bound to the client's account. The public endpoint requires no authentication beyond tip inclusion.
Rate limit: up to 50 requests per second on the dedicated endpoint, compared to 1 RPS on the public endpoint.
RPC proxy capability: the dedicated endpoint supports both sendTransaction calls and standard RPC read operations (getBalance, getAccountInfo, getSlot, etc.). Non-transaction requests are proxied to standard RPC nodes, allowing clients to use Syncro Sender as their single connection for both reads and writes. The public endpoint handles sendTransaction only.
Tip amount: the standard tip for the dedicated endpoint is 0.001 SOL per landed transaction, compared to 0.0001 SOL on the public endpoint.
Support: dedicated endpoint users receive dedicated support and can arrange custom service terms.
First-month benchmark period
New dedicated endpoint users can run production volume at the reduced public-endpoint rate (0.0001 SOL per landed transaction) for the first month, subject to applicable terms. This benchmark period allows teams to evaluate Syncro Sender's landing performance against their current infrastructure on real transactions before moving to standard pricing.
How the request flow works
Step 1: The request hits the dedicated endpoint and is authenticated via API key.
Step 2: If the request is a sendTransaction call, the transaction is validated for tip amount and proceeds to multi-path submission. If it is a read operation (e.g., getBalance), it is proxied to RPC nodes and the response is returned.
Step 3: For sendTransaction calls, the transaction is broadcast through all parallel channels: direct leader submission, SWQoS TPU, relayer, and RPC fallback.
Custom tiers
Teams needing more than 50 RPS or custom terms can request a customized arrangement through P2P.org's business development team.
This article is for informational purposes only and does not constitute a service agreement. Use of Syncro Sender is governed by the Terms of Service: https://www.p2p.org/syncro-terms