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.

Can I limit what my agent is allowed to do with the asciinema Server API?

Yes. Because you run Jentic One yourself, your own rules decide which asciinema operations the agent may call, so you can allow POST /api/v1/recordings for uploads while withholding DELETE /api/v1/recordings/{id} and DELETE /api/v1/streams/{id}. Since asciinema puts the recording or stream id in the URL path, a rule can pin the agent to updating a single recording or stream rather than any of them. The credentials you store are only ever applied to the operations you have permitted, so the agent cannot reach anything you have not scoped in.