asciinema Server API

Name: asciinema Server API
Brand: asciinema Server API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybasic7 EndpointsREST

For Agents

Upload, update, and delete terminal session recordings and live streams on an asciinema server.

Install Jentic One Beta

Connect the asciinema Server API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the asciinema Server API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with asciinema Server API.

Upload a new terminal session recording to an asciinema server

Update title and description metadata on an existing recording

Delete recordings the authenticated user owns

GET STARTED

Start building with asciinema Server API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use asciinema Server API for, with concrete tasks.

★ CI Terminal Recording Capture

Capture interesting CI runs as terminal recordings and upload them to asciinema for later debugging or sharing. The POST /api/v1/recordings endpoint accepts the .cast file produced by the asciinema CLI, returning the public URL. Reduces the friction of sharing reproducible terminal output between engineers compared to copying scrollback.

Upload the recording.cast file produced by the deploy job to asciinema, set the title to 'Production deploy 2026-06-09', and return the recording URL

Live Demo Streaming

Spin up an asciinema live stream for a developer demo or pair-programming session, so remote viewers can watch the terminal in real time. The POST /api/v1/streams endpoint creates the stream, and PATCH/DELETE manage its lifecycle. Suitable for distributed teams running interactive walkthroughs.

Create a new asciinema stream titled 'Pair debug session', return the stream URL and broadcast token, then list all current streams to confirm

Recording Library Cleanup

Audit and prune a backlog of old asciinema recordings using PATCH for metadata fixes and DELETE for removal. Useful for self-hosted asciinema instances where storage and discoverability matter. Agents can reconcile the user's stream list against an external catalogue.

List the authenticated user's streams and delete any whose titles contain 'test-' to clean up draft broadcasts

AI Agent for Terminal Knowledge Capture

An agent integrated through Jentic can listen for shell session events, automatically upload notable recordings to asciinema, and update titles based on what was demonstrated. Jentic stores the asciinema basic-auth credentials in its vault so the agent never sees the raw username and password.

Through Jentic, upload the latest .cast file from the demo session and set its description to a summary generated from the transcript

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for asciinema server api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/recordings

Create a new recording

PATCH

/api/v1/recordings/{id}

Update recording metadata

DELETE

/api/v1/recordings/{id}

Delete a recording

POST

/api/v1/streams

Create a new live stream

PATCH

/api/v1/streams/{id}

Update stream metadata

DELETE

/api/v1/streams/{id}

Delete a stream

GET

/api/v1/user/streams

List user streams

POST

/api/v1/recordings

Create a new recording

PATCH

/api/v1/recordings/{id}

Update recording metadata

DELETE

/api/v1/recordings/{id}

Delete a recording

POST

/api/v1/streams

Create a new live stream

PATCH

/api/v1/streams/{id}

Update stream metadata

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

asciinema basic-auth credentials (install ID and API token) are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw username and password never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'upload a terminal recording') and Jentic returns the matching asciinema operation with its input schema, so the agent can call POST /api/v1/recordings without reading docs.

Time to first call

Direct asciinema integration: a couple of hours to wire basic auth and multipart upload. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using asciinema Server API through Jentic.

Why is there no official OpenAPI spec for asciinema Server API?

asciinema does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call asciinema Server API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the asciinema Server API use?

The API uses HTTP basic authentication. The username is your asciinema install ID and the password is the API token shown in the asciinema CLI 'auth' command output. Jentic stores both as a single basic-auth credential in its vault and injects them at execution time.

Can I upload a terminal recording through the asciinema API?

Yes. POST /api/v1/recordings accepts a multipart upload of a .cast file produced by the asciinema CLI. The response returns the public URL of the recording on the server.

Does the asciinema API support live streaming?

Yes. POST /api/v1/streams creates a new live stream, PATCH /api/v1/streams/{id} updates its metadata, and DELETE /api/v1/streams/{id} removes it. GET /api/v1/user/streams returns all streams owned by the authenticated user.

What are the rate limits for the asciinema Server API?

The OpenAPI specification does not document explicit rate limits. asciinema.org is community-operated, so be conservative — implement backoff on HTTP 429 and avoid bulk uploads. For heavy use, run a self-hosted asciinema server.

How do I upload a recording through Jentic?

Search Jentic for 'upload an asciinema terminal recording' — POST /api/v1/recordings will be returned. Load the operation schema, supply the .cast file, and execute. Jentic handles basic-auth credentials and returns the recording URL.

asciinema Server API

Connect the asciinema Server API to your agent

Capabilities

Start building with asciinema Server API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs