Sinister Obfuscator

Optional product line for obfuscating your own Lua source through Sinister's luaObfuscator pipeline. Separate from Sinister Script (SSB-*).

Do you have access?

Your subscription tier must include obfuscator access. Staff can check plans.json for access_obfuscator: true on your plan.

If unsure, ask support. There is no Discord slash command for obfuscator jobs today.

What you get

• API key (X-Obf-Key header)
• Daily job quota and max source size
• Preset ceiling (Standard through Enterprise)

Presets control rename depth, control flow, VM layers, and optional bind-to-key for tier_c.

Tiers snapshot

GET /api/v1/obfuscate/plans on your Sinister host lists public tier names derived from active plans. No auth required for that list.

Typical workflow

1. Staff issues an obfuscator API key
2. GET /api/v1/obfuscate/quota to see remaining jobs and allowed presets
3. POST /api/v1/obfuscate with JSON { "source": "...", "preset": "standard" }
4. Poll GET /api/v1/obfuscate/jobs/{jobId} until status is ready
5. Read output field from the poll response

See Presets and tiers for what each obfuscation level does. Request examples: API quickstart.

Limits

Limit	On exceed
Daily jobs	HTTP 429
Max bytes	HTTP 400 at submit
Preset above your cap	Clamped to your max preset

Not the same as

Product	Key prefix	Purpose
Reseller resolve API	SSW-*	Username resolves for resellers
Sinister Script	SSB-*	Licensed in-game product
Obfuscator	Obf API key	Obfuscate arbitrary Lua you own

Support

Include your API key id (not the secret), job id, and preset when opening a ticket.