Automate the net without handing over the keys.

1. Smoke test a key

$Shard = "https://your-shard.example.com"
$Key = "scok_your_key_here"

Invoke-RestMethod "$Shard/api/v1/status" `
  -Headers @{ Authorization = "Bearer $Key" }

Use a key with read:status. If this works, the key, shard URL, and reverse proxy path are all sane.

2. Assign a user to a net

$Headers = @{
  Authorization = "Bearer $Key"
  "Content-Type" = "application/json"
}

$Body = @{
  userId = "123456789012345678"
  netUid = "net_jmqbkeg5s74cjkezqybwkhny"
  action = "assign"
} | ConvertTo-Json -Depth 5

Invoke-RestMethod "$Shard/api/v1/assignments" `
  -Method POST -Headers $Headers -Body $Body

Requires write:assignments. Use action = "unassign" to remove the same assignment.

3. Map Discord roles to nets

$Body = @{
  rules = @(
    @{
      roleId = "1505521308744679464"
      netUids = @("net_jmqbkeg5s74cjkezqybwkhny")
    }
  )
} | ConvertTo-Json -Depth 6

Invoke-RestMethod "$Shard/api/v1/rules" `
  -Method POST -Headers $Headers -Body $Body

Requires write:rules. Connected clients receive effective assignments from their Discord roles.

Who can run it

The requester must hold either the Command Net Supporter role or the Infrastructure Supporter role in the Star Comms support Discord.

The requester must also be the owner of the target Discord server or hold a Discord role with Administrator in that server.

What the form asks for

Target Discord guild ID, shard public URL, shard display name, host/runtime note, and the requester user ID. The owner user ID must match the person submitting the form.

The target guild should already be configured with Star Comms through the normal setup flow.

How the token behaves

The token is non-expiring by date and shown only once. If the supporter role is removed, the shard entitlement disables; if the role returns, the same token reactivates.

Safeguards prevent one supporter from claiming multiple shards and prevent one guild from being claimed by multiple supporters.