Authentication
Blockspace doesn't hand out one master key. Each product ships its own access model, so find the row below that matches what you're using and follow that quickstart.
| Product | How you authenticate | Provisioned in |
|---|---|---|
| ShredStream | gRPC x-token metadata, per subscription | Dashboard, self-serve |
| Direct Shreds | Source-IP allowlist on a dedicated link | Dashboard, ~30 min provisioning |
| SWQOS | No token — open endpoint; tip transfer in the tx (HTTP) or QUIC keypair allowlist | Dashboard, self-serve (both HTTP and QUIC) |
| Relayer/TPU | Token + signing-pubkey allowlist, application-based | Application review |
Account-level "API keys" don't exist here. Tokens and allowlists are scoped to the product that governs them, and live on that product's own page.
Where to get credentials
Start at the dashboard and sign in. From there, subscribe — or apply, if the product is application-gated. Once you're in, open the product page: the connection details (endpoint, token, region, allowlist form) are all right there.
Rotating credentials
Each product page has its own rotate flow. For token-based products it's generate, deploy, revoke, in that order: spin up a new token, roll it out, then kill the old one. Both stay valid mid-swap, so nothing goes down while you migrate.