This is a different credential from the API keys above — those are for pushing script updates (see below). To read the SDN catalog and pull the newest compiled jar, use whatever this PC's agent already has: its shared fleet token (FLEET_TOKEN in its config.bat / launcher.properties), a per-agent enrollment key from PCs → Add a PC, or a scoped Discord-login token. Any of those three work in the same X-Fleet-Token header — no SDN API key needed just to read.

# 1. List everything currently in the SDN - name, size, and last-modified time for each script.
#    Compare lastModifiedMillis against what you have locally to know if a newer build is waiting.
curl "/api/sdn/scripts" \
     -H "X-Fleet-Token: <FLEET_TOKEN_OR_ENROLLMENT_KEY>"

# 2. Download the current compiled jar for one script by name (always the latest - there is only
#    ever one live jar per script name, whatever the most recent push left there).
curl -o "<ScriptName>.jar" \
     "/api/sdn/scripts/<ScriptName>/download" \
     -H "X-Fleet-Token: <FLEET_TOKEN_OR_ENROLLMENT_KEY>"

# Optional: add ?profileId=<clientProfileId> to #1 to see exactly what that one account is
# allowed to run (per-account script grants), instead of the full catalog.

A running client's own Script Manager does this automatically on every poll - this is only for a separate agent/script-dev machine that wants the latest source/jar without running a full client.

Send the key in the X-Fleet-Token header. Upload a compiled jar (recommended — no server-side compile):

curl -X POST "/api/sdn-admin/upload?name=<ScriptName>"      -H "X-Fleet-Token: <YOUR_API_KEY>"      -H "X-Change-Author: <agent / PC name>"      -H "X-Change-Note-B64: $(printf '%s' "$NOTES" | base64 -w0)"      --data-binary @<ScriptName>.jar
# FULL CHANGE NOTES ARE REQUIRED on every upload / compile / source push (60+ chars, any caller):
# what was broken, the cause, what you changed (classes/methods), how it was tested, what is left.
# Plain one-line notes can go in X-Change-Note; use X-Change-Note-B64 (base64 UTF-8) for multi-line.
# BEFORE editing a script read what the other agents already did:
curl "/api/sdn-admin/changelog?name=<ScriptName>" -H "X-Fleet-Token: <YOUR_API_KEY>"
# Every push also returns "recentChanges" (the last 5 before yours). History button per script in the panel.

# toggle a script on/off for every client's SDN
curl -X POST "/api/sdn-admin/set-enabled"      -H "X-Fleet-Token: <YOUR_API_KEY>" -H "Content-Type: application/json"      -d '{"name":"<ScriptName>","enabled":true}'

# compile from a source folder on the server, or delete a script
# POST /api/sdn-admin/compile   {"name":"...","src":"C:\path\to\src"}
# POST /api/sdn-admin/delete    {"name":"..."}

After a push, restart the running script (Stop/Start) so it reloads the new jar — no client relaunch needed. A push here is exactly what the pull commands above will see as the new "most recent" jar.

Use the central SDN hub at https://dbcrimson.com and an SDN API key allowed to edit the script. Publishing a JAR does not upload its source. Source revisions are separate from Git commits and never run on the server.

Publish the COMPLETE current source for <ScriptName> to the central SDN using your existing SDN API key. Do not substitute an older source version just because it compiles.

0. Read the script's change history first: GET https://dbcrimson.com/api/sdn-admin/changelog?name=<ScriptName> with X-Fleet-Token. It lists every push with the full change notes of whoever made it - build on those fixes, do not undo them.
1. Download GET https://dbcrimson.com/api/sdn-admin/source?name=<ScriptName> with X-Fleet-Token. Check matchesPublishedJar. A 404 means no source has been shared yet: locate the source used for the live build before editing.
2. Download its source ZIP from GET /api/sdn-admin/source/download?name=<ScriptName>. Use &revision=<revision> to retrieve an older revision. GET /api/sdn-admin/source/versions?name=<ScriptName> lists history.
3. Include all Java files, resources and build instructions in the source ZIP. Exclude .git, compiled classes, JARs, caches and credentials. Build the JAR from exactly this source. Preserve other agents' changes and push the source Git commit too when that repository is available.
4. Upload the source ZIP with POST /api/sdn-admin/source?name=<ScriptName>. Headers: X-Fleet-Token: your key; X-Change-Note (or X-Change-Note-B64 for multi-line): FULL change notes - symptom, cause, fix, files, testing, open issues (required, 60+ chars); X-Jar-SHA256: SHA-256 of the matching JAR. Body: raw ZIP bytes. Save the returned revision and sourceSha256.
5. Upload that JAR with POST /api/sdn-admin/upload?name=<ScriptName>, X-Fleet-Token and X-Change-Note, body = raw JAR bytes. Uploads apply to the SDN immediately; do this only after the build and checks pass.
6. Read the source metadata again and verify matchesPublishedJar=true. Download the source ZIP and JAR and compare their hashes to your local files. Report the script version, source revision, Git commit when available, checks run and JAR hash. The user can then Stop/Start the script to load the published build.

For CrimsonRedFarm: upload the newest source matching the live CrimsonRedFarm build. The old cCRedFarm 0.2 source is not the newer CrimsonRedFarm 1.1 implementation.

PowerShell example (set SDN_API_KEY privately in your environment):

$hub = 'https://dbcrimson.com'
$name = 'CrimsonRedFarm'
$headers = @{
  'X-Fleet-Token' = $env:SDN_API_KEY
  # FULL change notes are required (60+ chars): symptom, cause, fix, files, testing, open issues
  'X-Change-Note-B64' = [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes((Get-Content .\CHANGES.txt -Raw)))
  'X-Change-Author' = $env:COMPUTERNAME
  'X-Jar-SHA256' = (Get-FileHash "$name.jar" -Algorithm SHA256).Hash.ToLowerInvariant()
}
Invoke-RestMethod "$hub/api/sdn-admin/source?name=$name" -Method Post -Headers $headers -ContentType 'application/zip' -InFile "$name-source.zip"
Invoke-RestMethod "$hub/api/sdn-admin/upload?name=$name" -Method Post -Headers $headers -ContentType 'application/java-archive' -InFile "$name.jar"
Invoke-RestMethod "$hub/api/sdn-admin/source?name=$name" -Headers $headers