Microsoft Azure Azure Media Services

Name: Azure Media Services API
Brand: Azure Media Services
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processingoauth25 EndpointsREST

For Agents

Manage Azure Media Services account-level filters that apply streaming-time track and time-range clipping rules across every Asset in a Media Services account.

Use for: I need to create an account-level filter on my Media Services account, List all account filters on a Media Services account, Retrieve a single account filter by name, Update the time range on an existing account filter

Not supported: Does not upload assets, run encoding jobs, or stream content — use for Media Services account-level filter management only.

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.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Azure Media Services to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Media Services, 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 Azure Media Services API.

Create or update an account-level filter on a Media Services account

List every account filter attached to a Media Services account

Retrieve a single account filter's track and presentation time properties

Update an existing filter's first quality, time range, or track selections

Delete an account filter that is no longer used

Use Cases

Patterns agents use Azure Media Services API for, with concrete tasks.

★ Reusable Clip Rules Across Assets

Producers ship the same streaming-time trim across every Asset in a Media Services account by defining an account filter once. The PUT on /accountFilters/{filterName} accepts presentationTimeRange, firstQuality, and trackSelections; Streaming Endpoints then apply the filter to manifest requests via filter query parameters, so producers do not re-encode assets to remove trailers or limit bitrates.

Create account filter 'no-intro' on Media Services account 'amsaccount' in resource group 'rg-media' with presentationTimeRange.startTimestamp=0 and presentationTimeRange.endTimestamp=600000000 (60 seconds in 100ns units).

Bitrate Floor Enforcement via firstQuality

When you want every player to start at a minimum bitrate, an account filter's firstQuality.bitrate sets the lowest manifest entry the Streaming Endpoint will return. Updating the value via PATCH (PUT replace) lets operators raise or lower the floor across the whole account without touching individual assets.

Update account filter 'min-bitrate' on account 'amsaccount' to set firstQuality.bitrate to 1500000 and verify via GET.

Filter Cleanup Before Account Decommission

Before removing or rebuilding a Media Services account, operators enumerate and delete any leftover account filters so reused filter names do not collide. The GET on /accountFilters lists all filters; DELETE removes them one at a time. This avoids stale filters being inadvertently re-applied if the account is recreated under the same name.

List account filters on 'amsaccount' and delete every filter whose name matches the prefix 'temp-'.

Agent-Driven Filter Audit

An AI agent through Jentic can enumerate account filters across Media Services accounts in a subscription, compare each filter's track selections and time ranges against a desired-state config, and queue PUT or DELETE calls to bring them into compliance. Jentic returns the per-filter operation schema so the agent never browses the Microsoft.Media docs.

List filters on every Media Services account in subscription '00000000-0000-0000-0000-000000000000' and report any without a presentationTimeRange.endTimestamp set.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for azure media services, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters

List account filters on a Media Services account

PUT