swqos.com documentation

swqos.com forwards already-signed transactions over warm stake-weighted QoS connections. The default price for a landed balance-funded transaction is 0.00015 SOL; non-landed balance-funded sends are fully refunded.

What it does#

You build and sign a Solana transaction with your own keypair, exactly as you do now. Instead of handing it to a general purpose RPC, you hand the serialized bytes to swqos.com. We validate the envelope, reserve the price from your prepaid balance, and write those unchanged bytes to a stake-weighted QoS connection that is already open and warm.

There is no blockhash fetch, simulation, or status check in the forwarding path. We keep 4upstream connections warm at all times, so your transaction never waits on a handshake. The relay reads your bytes, validates the envelope, reserves payment, and forwards. That is the whole critical path, and there is nothing in it that has to wait on anything else.

What it guarantees, and what it does not#

This is the most important paragraph in these docs, so it comes early rather than buried in a billing page.

What an accepted receipt does tell you is precise and useful: your bytes were valid, payment was authorized, and an upstream connection acknowledged the stream. It is not a final charge. A balance reservation is fully refunded if the transaction provably does not land.

The shape of an integration#

Four steps, and only the third one involves us.

1. Build and sign the transaction with the library you already use.
2. Serialize it and base64 encode it, or write the raw bytes to a QUIC stream.
3. Submit it to https://send.swqos.com/v1/transactions or to send.swqos.com:11000.
4. Read the receipt, and confirm landing yourself if your use case needs certainty.

The quickstart walks through all four in TypeScript, Python, Rust and Go, with complete programs rather than fragments.

Checking we are up#

The health route is public and needs no credential. It reports each component independently, so a degraded billing ledger is distinguishable from a degraded forwarding path.

1curl -sS https://send.swqos.com/v1/health
2 
3# {"ok":true,"status":"healthy","billing_ledger":"healthy",
4#  "audit_ledger":"healthy","upstream":"healthy"}

It returns HTTP 503 if any required component is unhealthy. Poll it every fifteen seconds with a three second timeout and alert after three consecutive failures.

Everything in these docs#