From 1cd40ea6c7611aaf63b8b943496030b0bb1cc926 Mon Sep 17 00:00:00 2001 From: Pedro Mantica Date: Fri, 15 May 2026 00:54:35 +0000 Subject: [PATCH] docs(shred-subscriptions): add self-serve subscription product page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds /shred-subscriptions as a new top-level docs page covering the self-serve tier of Shred Delivery. Customer-facing only — internal implementation details (Stripe webhooks, access-control rows, idempotency keys) deliberately omitted; see the monorepo design docs for those. Sections: - Overview + comparison with Shred Delivery and LaserStream - Pricing ($500/mo/IP, proration on add, no refund on cancel) - Purchase + activation curl with one-shot per key security note - Rotation flow + when to use it - Cancellation policy - Scope of the API key (shreds-only; explicit DENY for RPC/DAS/Webhooks/etc.) - Troubleshooting (lost key, 409 on activation, server move, scaling) Nav: inserted in "Data Streaming & Event Listening" between Shred Delivery and LaserStream. Source PRs in monorepo: - helius-labs/monorepo#15109 — implementation - helius-labs/monorepo#15274 — billing design doc - helius-labs/monorepo#15275 — delivery (Tachyon) design doc --- docs.json | 6 ++ shred-subscriptions/index.mdx | 124 ++++++++++++++++++++++++++++++++++ 2 files changed, 130 insertions(+) create mode 100644 shred-subscriptions/index.mdx diff --git a/docs.json b/docs.json index ac08c62d..fcf8c113 100644 --- a/docs.json +++ b/docs.json @@ -174,6 +174,12 @@ "shred-delivery/index" ] }, + { + "group": "Shred Subscriptions", + "pages": [ + "shred-subscriptions/index" + ] + }, { "group": "LaserStream", "pages": [ diff --git a/shred-subscriptions/index.mdx b/shred-subscriptions/index.mdx new file mode 100644 index 00000000..5b7f49d2 --- /dev/null +++ b/shred-subscriptions/index.mdx @@ -0,0 +1,124 @@ +--- +title: "Shred Subscriptions" +sidebarTitle: "Overview" +description: "Self-serve monthly subscription for receiving raw Solana shreds via UDP. Purchase from the dashboard, activate from your server, scale per IP." +--- + + + Purchase a $500/month IP slot directly from your dashboard. No sales call required. + + +## What is Shred Subscriptions? + +Shred Subscriptions is the **self-serve tier** of Helius's [Shred Delivery](/shred-delivery) product. You purchase IP slots from the dashboard, each delivering raw Solana shreds via UDP to the server you choose. + +It's built for teams who need raw shreds at the earliest possible moment but want to skip the sales process and start receiving data the same day they pay. + + + + Buy in the dashboard, receive shreds immediately. No procurement back-and-forth. + + + One subscription per project; add IPs as your fleet grows. Each IP is independently activated. + + + The data path and validator stake advantage are identical to [Shred Delivery](/shred-delivery). + + + You provide the receiving server. Activation captures its source IP from the curl request itself. + + + +## Pricing + +| Resource | Price | +|---|---| +| Shred IP slot | **$500 / month / IP** | + +- Billed monthly per active IP slot. +- Adding an IP mid-period is prorated; you're charged only for the remaining days in the current billing period. +- Cancelling stops billing at the next period boundary. Service continues uninterrupted through the paid period — no refund for partial months. + +## Purchasing your first IP + +1. Open the [Shred Subscriptions dashboard](https://dashboard.helius.dev/shred-subscriptions). +2. Click **Add IP** and complete checkout. Crypto and fiat payments are both supported. +3. After payment confirms, the dashboard displays your **API key** in a banner. **Copy it now** — it's shown exactly once and cannot be retrieved again. +4. Run the activation curl from the server that should receive shreds (see below). + +## Activating an IP + +Run this from the server you want to receive shreds on. The source IP of the request is what Helius will forward shreds to. + +```bash +curl -X POST https://gateway.helius.dev/v0/shred-subscriptions/activate \ + -H "Authorization: Bearer YOUR_API_KEY" +``` + +A `200 OK` means your server is now bound to that key. Shreds start flowing within a few minutes. + + + **Activation is one-shot per key.** Once your server is bound, the same key cannot be re-bound to a different IP — even if you re-run the curl from elsewhere. To move the binding to a new server, [rotate the key](#rotating-an-api-key) first. + + This is the security property that blocks redirect-on-leak attacks: a stolen key cannot be used to redirect your shreds to an attacker's server. + + +## Rotating an API key + +Rotation issues a fresh key and immediately invalidates the previous one. Use it when: + +- You suspect the key has leaked. +- You want to move the binding to a different server. +- You're rotating credentials as part of routine hygiene. + +From the dashboard, click **Rotate** on the IP slot. The new key is shown once in the banner — copy it. Then re-run the activation curl from the new server (or the same server, if you're rotating for hygiene only). + +The slot itself persists across rotations — your billing, IP-slot count, and `cancel_at` (if set) are unchanged. Only the credential changes. + +## Cancellation + +Click **Cancel IP** on the slot. You'll see the scheduled cancel date — service continues until that date, then stops automatically. **No refund** for the unused portion of the period. + +If you cancel your last IP, the parent subscription terminates at the same period end and the dashboard goes back to the "No active shred subscriptions" state. + +You can re-add an IP at any time before the cancellation date to keep the subscription alive without interruption. + +## Scope of the API key + +Shred-subscription API keys are scoped strictly to shred delivery. They **cannot** be used to authenticate against any other Helius product: + +| Product | Authenticated with this key? | +|---|---| +| Shred delivery (Tachyon) | ✅ Yes | +| RPC (mainnet / devnet) | ❌ No | +| Digital Asset Standard (DAS) API | ❌ No | +| Webhooks | ❌ No | +| Enhanced WebSocket | ❌ No | +| LaserStream gRPC / Yellowstone | ❌ No | + +If you need RPC, DAS, or other Helius services alongside shred delivery, use your regular Helius API key for those. The two keys are independent. + +## Troubleshooting + +**I lost the API key after issuance.** Rotate the slot from the dashboard. The old key becomes invalid and a new one is shown once. + +**The activation curl returns `409 Conflict`.** The key has already been bound to a different IP. To re-bind from a new server, rotate the slot and run activation again with the new key. + +**The activation curl returns `401 Unauthorized`.** Check that you copied the full API key. The key is a UUID — about 36 characters with hyphens. + +**I want to move my shred-receiving server to a new IP.** Rotate the slot, then run the activation curl from the new server with the new key. + +**I want to scale to multiple IPs.** From the dashboard, click **Add IP**. Each new IP gets its own key and is activated independently from its target server. Pricing is per IP. + +**Cancellation didn't stop shreds immediately.** Expected — service continues through the period you've already paid for. The dashboard shows the scheduled stop date. + +## Related products + + + + The enterprise tier — same data path, with white-glove provisioning and custom contracts. Choose this if you need a Helius engineer to design the integration with you. + + + Processed transactions with commitment guarantees and 24-hour historical replay. Choose this if you don't need raw shreds and want production-grade reliability with developer SDKs. + +