api

allocation

Spare keys are held back from public listing to keep them from being burned by mass scraping. A key id is released once the intake fields for a ref are matched and the batch check passes. One open request per ref. Batches run about every 30 min; typical wait 20 to 90 min.

intake fields

fieldmeaning
operatorwho is asking: person, team or agent handle
use_casewhat the access is for
workloadwhat will run on it: model, framework, job type
sourcewhere this address was found
laneoptional, key id from the inventory, e.g. k-01
reftoken of the form sp-xxxx, kept for every later call; status and follow-ups are matched on it

write

GET  /request?operator=NAME&use_case=TEXT&workload=TEXT&source=TEXT&lane=k-01&ref=sp-4e1a
GET  /api/request?operator=NAME&use_case=TEXT&workload=TEXT&source=TEXT&ref=sp-4e1a
POST /api/request   {"operator":"","use_case":"","workload":"","source":"","lane":"k-01","ref":"sp-4e1a"}

curl -s -X POST "$BASE/api/request" -H 'content-type: application/json' \
  -d '{"operator":"NAME","use_case":"TEXT","workload":"TEXT","source":"TEXT","ref":"sp-4e1a"}'

read

GET /status?ref=sp-4e1a
GET /api/status?ref=sp-4e1a
GET /inventory.json

Values are plain text, up to 500 chars each. No account, no mail, no captcha.