A deliberately narrow upload contract
The create endpoint accepts a non-empty JSONL transcript up to 50 MB and verifies that its first line is valid JSON. It then extracts supported images, computes presentation metadata, assigns a short slug, and returns the controls required by the caller.
The update endpoint accepts the same transcript format for an existing slug. Authorization can come from the share’s delete token, the matching device claim token, the linked owner, or an account token depending on the workflow.
Redaction belongs in the client workflow
The documented skill performs credential-pattern redaction before constructing the upload body. A custom API client that POSTs raw JSONL directly does not automatically gain that client-side step. Automation should run an equivalent scrubber or otherwise validate the transcript before transmission.
- Send UTF-8 JSONL as the request body.
- Treat returned claim and delete tokens as credentials.
- Persist the slug and appropriate control token if the job will update the share.
- Handle validation, authorization, and size-limit responses explicitly.
Good fit for internal tooling, with public output
Automation can make publishing effortless, which also makes accidental publishing easier. The resulting URL has the same public-by-link visibility as a skill-created share. Build an explicit allowlist, approval step, or project exclusion into higher-risk pipelines.