Jentic publishes the only available OpenAPI specification for Azure Media Services, keeping it validated and agent-ready. This slice of the Azure Media Services control plane manages account-level filters under Microsoft.Media/mediaServices/{accountName}/accountFilters. Account filters declare reusable streaming-time clipping rules — track selection, presentation time ranges, and timestamp filters — that Streaming Endpoints apply to every Asset under the account, so producers can ship the same on-the-fly trims across all assets without re-encoding. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.
5 endpointsJentic publishes the only available OpenAPI specification for MediaServicesManagementClient, keeping it validated and agent-ready. The Azure Media Services management API provisions and operates Media Services accounts that back video encoding, packaging, and streaming workloads. Use it to create accounts, list and update existing ones, manage the storage keys that bind the account to its backing storage, and verify name availability before provisioning. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
10 endpointsStep 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 | shStep 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 instanceJentic 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.