Pricing, Rate Limits & Support

Plans

	Public (Tip-Based)	Private (API Key)
Tip requirement	Required (minimum 100,000 lamports)	Required (minimum 50,000 lamports)
Authentication	Tip required in transaction	API key + tip in transaction
Endpoint	`/public`	`/` or `/rpc`
Supported methods	`sendTransaction` only	All Solana RPC methods
Default rate limit	1 TPS per IP	50 TPS per client (custom for dedicated)

Tip accounts:

BPZrtYhdoAhiHWV5EgGLoV7bZFbMamBZurGDq4DmST8v
7D5pdbkV75Sr73M1YFNZwXMed6DenwkdfbJwVWrX6drQ
ELpn2NryEW4B3psG36eSjF45YcGMQpGGuu9J2AgAccbV
FnckAPC9PitnRpGZM2M4WLwb3w9odRLJ7EDRZDngjvd6
3ZnDTgvVfwzqwWoqAUmDkgVtXvXqjmeb5t9zxD5pMbmv
3SLDFcdCzMbcFNguZhzmV4zqEAUvcPoKY13akpE4Tq1p
48tT6LJqrsoFrLpzZSHkjGdGTWtsJ1PvjgWZjh8qF1RK
7GM9fpVMHHcrK4cgzfVdzJvjiy1bSyfwSYzhxvgbfVLg
CBd8GE3ffMJKf3iCCcNNBEifMxH1WpgtTzRnXPxxbjGE

Rate limits

How it works

Algorithm: Fixed 1-second window counter
Private endpoint: Rate limited per client
Public endpoint: Rate limited per source IP address

Default limits

Endpoint	Default TPS	Customizable?
Public	1 per IP	No
Private	50 per client	Yes (per client)

Rate limit response

When the limit is exceeded, you receive an HTTP 429 response with rate limit headers:

HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 0
Retry-After: 1
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32005,
    "message": "Rate limit exceeded"
  },
  "id": 1
}

Wait for the number of seconds indicated by Retry-After before sending the next request.

FAQ

What encoding should I use for transactions?

Base64 (recommended). Always pass {"encoding": "base64"} in the params. The transaction bytes should be the serialized, signed transaction encoded as a base64 string.

Can I use Syncro Sender for read-only RPC calls?

Yes, on private endpoints when this capability is enabled on your client profile. This proxies standard Solana RPC methods (e.g., getBalance, getTransaction, getSlot) through Syncro Sender’s RPC backend.

What happens if my tip is too low?

You’ll receive an error response with code -32602:

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32602,
    "message": "Insufficient tip: provided 50000 lamports, required 100000 lamports"
  },
  "id": 1
}

The error message includes both the amount you provided and the required minimum, so you can adjust accordingly.

How do I check if my transaction landed?

Use any standard Solana RPC’s getSignatureStatuses method: Syncro Sender handles delivery — it sends your transaction to validator leaders through multiple channels. Confirmation tracking should be done separately.

Contact & support

Telegram: support.p2p.org
Email support@p2p.org

Introduction

Using AI Tools

API Products

Widget

Syncro Products

SDK Products

Deep Dive

Support

Pricing, Rate Limits & Support

Plans

Rate limits

How it works

Default limits

Rate limit response

FAQ

What encoding should I use for transactions?

Can I use Syncro Sender for read-only RPC calls?

What happens if my tip is too low?

How do I check if my transaction landed?

Contact & support

​Plans

​Rate limits

​How it works

​Default limits

​Rate limit response

​FAQ

​What encoding should I use for transactions?

​Can I use Syncro Sender for read-only RPC calls?

​What happens if my tip is too low?

​How do I check if my transaction landed?

​Contact & support

Plans

Rate limits

How it works

Default limits

Rate limit response

FAQ

What encoding should I use for transactions?

Can I use Syncro Sender for read-only RPC calls?

What happens if my tip is too low?

How do I check if my transaction landed?

Contact & support