Rung

Docs

Encode API

Public place-value surface. Integers in, compact rungs out. This is not the full composed-rung system — that stays closed, under NDA.

Auth

Sign in, mint a key on API, then send it as a bearer token. Keys start with rung_.

POST /api/v1/encode

Header
Authorization: Bearer rung_…
Alt header
x-api-key: rung_…
Body
{ "values": number[], "width"?: 1–32 }
Limit
1–256 unsigned integers, 0…2³²−1
{
  "encoding": "place_value",
  "width": 16,
  "values": [512, 1023],
  "vectors": [
    [0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0],
    [1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0]
  ],
  "one_hot_slots_to_name_max": 1024
}

curl

curl -s https://HOST/api/v1/encode \
  -H "Authorization: Bearer rung_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"values":[512,1023],"width":16}'

What this is not

One-hot has no slot for a magnitude it never named. Learned embeddings memorize the training range. Place value already has the next column. The live bench on this site is a public miniature of that fact. The composed-rung encoder is not in this API.