Transcribe Desk / API
Get a token

Driving Transcribe Desk from code

Everything the web app does is available over HTTP. The base URL is https://api.skillsafe.ai/v1/app-api, every request carries Authorization: Bearer <token>, and every response is the same envelope.

The task field comes first

This app has five lanes behind one endpoint. Every run body must carry a task field naming the lane - it is what the system prompt routes on. Send the wrong one and you get a valid package of the wrong kind; omit it and the model picks the closest lane and tells you which it chose.

One more shape trap: the run body is the input object. Do not wrap it in an {"input": ...} envelope - that returns 200 while hiding task from the model, which is the most confusing way this API can fail.

taskLaneFieldsSections returned
planSize the job before you spend itbrief, knownSummary, The Sheet, The Numbers, Reasoning, Next Step
checkWhether this job costs what you think, and lands where you thinksheet, worrySummary, Verdict, Findings, Corrected Sheet, Next Step
splitWhat has to be split, and wheresheetSummary, The Ceiling, Where To Cut, What Splitting Costs, Next Step
timesWhat the timestamps can land onsheetSummary, The Two Grids, Cue By Cue, What A Conform Absorbs, Next Step
deliverDecide what changes: the format, the audio, or nothingsheet, fixedSummary, A Format Change Fixes, Only Removing Audio Fixes, Nothing Fixes, Next Step

Only task and the lane's own required fields are mandatory: sheet on check, split, times and deliver; brief on plan. Every field is a string - there are no number fields on this app. The sheet is one KEY: value per line, in any order, and the grammar is in /llms.txt and in the free panel on the app itself.

The sheet takes JOB, DURATION, SPEECH, FILE, FORMAT, PATH, RTF, WPM, OVERLAP, FPS, TRIM, and any number of SILENCE and CUE lines. DURATION is the only one the engine cannot do without: the window count is ceil(duration / 30) and every other figure follows from it.

A bare number in DURATION is SECONDS, because that is what a media tool prints. 1:12:34 is hours, 12:34 is minutes, and 12m 30s works too. A bare number in SPEECH is a PERCENTAGE - 68, 68% and 0.68 all mean the same thing, and a value over 100 can only be a duration and is read as one.

FILE is read in binary units. 66 MB is 69,206,016 bytes, the same as 66 MiB, because that is how a file browser reports it. The hosted ceiling is read the same way - 25 x 1,048,576 bytes - so a file within a few per cent of the line should be treated as over it.

FORMAT is priced, never guessed. PCM is rate x channels x bits / 8 exactly and constant-bitrate audio is kbps / 8 exactly, so pcm 48000 2 24 and mp3 128 both have real byte rates. A lossless codec's rate follows the content, so flac has no rate at all here - state FILE and the engine uses the file you have rather than inventing a compression ratio.

FPS takes the exact fraction. 29.97 is read as 30000/1001 and 23.976 as 24000/1001, because the whole grid answer turns on that distinction: the model's timestamps are multiples of 20 ms, and where that grid meets a frame grid is the rational LCM of the two. At 25 fps every frame boundary is a time the model can name; at 24 fps one in 12 is; at 30000/1001 one in 600 is.

OVERLAP: 0 is a decision and not a default. Leaving OVERLAP out is read as undecided and reported as such; stating 0 says fixed stride, no surcharge, and you accept the cut words at the window boundaries.

A DURATION is reported as 1:12:34 over a minute and as 26 s under it. A SHARE is reported to one place. A byte size is reported in MiB, and a byte RATE in bytes per second, because that is the unit the ceiling divides.

Add $model to any body to choose the model for that run: gpt-5.6-luna, gpt-5.6-terra (the default) or gpt-5.6-sol. Luna caps output at 4,096 tokens and will fail the check, split and times lanes rather than shorten them - a findings table, a corrected sheet, or a row per part or per cue, is several thousand characters before the reasoning starts.

The response envelope

Success and failure have the same outer shape, so one check covers both.

{
  "ok": true,
  "data": {
    "...": "the result"
  }
}
{
  "ok": false,
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "seconds should be number, got string",
    "details": {}
  }
}
HTTPerror.codeWhat it means
400VALIDATION_ERRORThe body was not a JSON object, or a declared field had the wrong type. A number field sent as a string is the usual cause.
401UNAUTHORIZEDNo token, or a token that has expired or been revoked. Mint a new one.
402INSUFFICIENT_CREDITSThe balance is below the run's minimum. Call /estimate first and compare hold_credits against /me.
404NOT_FOUNDWrong path, or a job id that does not belong to this token.
409CONFLICTAn Idempotency-Key replay whose body differs from the original request.
429RATE_LIMITEDToo many requests. Back off; do not tight-loop.
503UPSTREAM_UNAVAILABLEThe model provider is unavailable. Retry with backoff.

1. Get a token

Open /tokens.html in a browser and copy the token this app already holds - no developer console needed. A guest token is minted automatically and is enough for /me and /estimate; writing a package is metered and needs a personal token, which comes from signing in on that page.

Keep it in an environment variable rather than in source:

export SKILLSAFE_TOKEN="YOUR_TOKEN"

2. Check the session and the balance

GET /me is free. It returns only three fields: subject_type, subject_id and credits. Signed-in means subject_type == "user" - there is no username or email to test.

curl -sS -X GET "https://api.skillsafe.ai/v1/app-api/me" \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN"

3. Price the run before making it

POST /estimate costs nothing, creates no job, and returns the worst-case cost. Compare hold_credits against the balance from step 2 before you submit: a 402 after the fact is avoidable. hold_credits is a reservation priced at the full output cap - the actual charge is usually far lower.

It also echoes model, model_alias and markup_bps, which is the authoritative check that a run is bound to the model you think it is. Estimate each lane separately: their prompts and caps differ, so their holds do.

curl -sS -X POST "https://api.skillsafe.ai/v1/app-api/estimate" \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "task": "check",
  "sheet": "<a job sheet - DURATION at minimum; the grammar is in /llms.txt>",
  "worry": "it graded fine last time and this one will not come clean",
  "rules": "<the working rules for this lane, sent by the app>"
}'

4. Write a package

POST /run submits the job. Always send an Idempotency-Key: a network blip that replays the same request must not bill twice. A replay with the same key returns the stored result and is not charged again; a replay with the same key but a different body is a 409.

The response carries output.output (the Markdown package), charged_credits and truncated. If truncated is true the balance sat between min_credits and hold_credits and the output was cut short - render what arrived and say so rather than presenting it as complete.

curl -sS -X POST "https://api.skillsafe.ai/v1/app-api/run" \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "task": "check",
  "sheet": "<a job sheet - DURATION at minimum; the grammar is in /llms.txt>",
  "worry": "it graded fine last time and this one will not come clean",
  "rules": "<the working rules for this lane, sent by the app>"
}'

5. Stream a run

POST /run-stream is the same call with a text/event-stream response. Worth knowing before you build on it: from a server or from cURL you get event: delta frames carrying the output token by token; from a browser you get event: tick heartbeats and then one event: done with the whole output. Handle both, and treat ticks as liveness rather than progress.

Frame types are job (the job id), delta ({"text": "..."}), tick ({"t": seconds}), done, and error. An idempotent replay returns plain JSON with no stream at all, so check the content type before you start reading frames.

curl -sS -N -X POST "https://api.skillsafe.ai/v1/app-api/run-stream" \
  -H "Authorization: Bearer $SKILLSAFE_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: text/event-stream" \
  -H "Idempotency-Key: cbd-$(date +%s)" \
  -d '{
  "task": "check",
  "sheet": "<a job sheet - DURATION at minimum; the grammar is in /llms.txt>",
  "worry": "it graded fine last time and this one will not come clean",
  "rules": "<the working rules for this lane, sent by the app>"
}'

6. Read the result

output.output is Markdown in the envelope this app's system prompt guarantees: every section is a level-two heading spelled exactly as listed in the lane table above, in that order; tables are GitHub pipe tables with the declared columns; prompts are in fenced blocks opened with three backticks and the word text; checklists are - [x] lines.

So parsing is a split on /^## / - but do it fence-aware, because a prompt block can legitimately contain a line starting with ##. Count the sections you got against the ones the lane declares: a short list means the run was truncated, not that the contract changed.

def sections(md):
    out, name, buf, fence = {}, None, [], False
    for line in md.split("\n"):
        if line.lstrip().startswith("```"):
            fence = not fence
        if not fence and line.startswith("## "):
            if name:
                out[name] = "\n".join(buf).strip()
            name, buf = line[3:].strip(), []
            continue
        if name:
            buf.append(line)
    if name:
        out[name] = "\n".join(buf).strip()
    return out

The artifact most callers want is the fenced text block inside ## The Sheet or ## Corrected Sheet - that is a complete sheet in the grammar above, so it can be fed straight back into another lane with nothing carried alongside it. Every other section is prose and tables meant to be read.

Rate limits and good manners