Authentication, Keys & Scopes
Every request entering LaunchVerse & Helix enforces explicit least-privilege credential boundaries, constant-time token verification, and workspace-scoped isolation.
Key Prefixes & Security Boundaries
| Prefix | Intended Runtime | Allowed Scopes & Restrictions |
|---|---|---|
| Session Cookie | Helix Web (launchverse.app) | Interactive workspace member authentication managed by session auth. |
hx_live_* | Backend servers, CI/CD runners, REST, MCP | Full workspace programmatic access capped only by key permissions & RPM/RPD limits. |
hx_test_* | CI smoke checks & staging sandboxes | Runs dry-run simulations where external writes are blocked; logs audit entries with isTest: true. |
hx_embed_* | Customer browser Web Components | Pinned to exactly one external principalId; blocks cross-tenant queries and rejects /api/webhooks/platform + key minting (403 principal_escalation_denied). |
hx_bridge_* | Outbound Private VPC Bridge daemon | Permits tunneling strictly to hosts explicitly listed in the bridge allow-list. |
lvse_* | Team Owner automation CLI | Owner-level deployment & billing automation token. |
Required HTTP Headers
Send your key via standard bearer Authorization alongside the pinned API version header:
Authorization: Bearer hx_live_your_secret_key
Helix-Version: 2026-11-16
Content-Type: application/jsonOptional workspace disambiguation header (when one key spans multiple workspaces):
X-Helix-Workspace: ws_01J...Rate Limits & Monthly Token Budgets
Keys minted under Developer Console -> API Keys carry optional hardware/cost guardrails:
rate_limit_rpm— requests per minute burst caprate_limit_rpd— requests per rolling 24h captoken_budget_monthly— hard monthly inference token ceiling
When a ceiling triggers, the gateway responds immediately with HTTP 429:
{
"error": "rate_limit_exceeded",
"retryAfterSeconds": 18,
"limit": "60 rpm"
}Key Rotation Without Downtime
- Open Developer Console -> API Keys -> Create Key to mint a replacement secret.
- Deploy the new secret to your CI / backend environment and confirm live requests succeed.
- Click Revoke on the legacy key ID (
DELETE /api/helix/keys?id=...). Revocation takes effect immediately across every edge worker and gateway. - For workspace secrets (database URLs, cloud tokens, webhooks), configure encrypted environment variables in Environments (
AES-256-GCMsealed at rest; decrypted exclusively inside running sandboxes).

