Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Media / Azure / Azure Media Services
Azure Media Services logo

Microsoft Azure Azure Media Services

Browse all Azure APIs
56
AI ReadinessFoundational (C)56/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticMediaVideo Processingoauth25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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 GithubView 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-media-services" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-media-services" | 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

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

Create or update an account filter

GET

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

Get an account filter by name

PATCH

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

Patch an account filter's properties

DELETE

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

Delete an account filter

GET

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

List account filters on a Media Services account

PUT

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

Create or update an account filter

GET

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

Get an account filter by name

PATCH

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

Patch an account filter's properties

DELETE

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

Delete an account filter

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Azure Media Services

- Foundational (C)
56/100
73
Foundational Compliance
62
Developer Experience & Jentic Compatibility
39
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

62

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

39

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
85%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

71%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Microsoft.Media account filter control plane by hand means registering an Azure AD app, acquiring bearer tokens for management.azure.com, and hand-building the presentationTimeRange, firstQuality, and trackSelections bodies against ARM throttling. Through Jentic you install once, import Azure Media Services from the API Directory, store the Azure AD service principal credentials once, and your agent calls it.

Permission scoping

This surface puts the subscription, resource group, account, and filter name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}), so a rule can pin your agent to filters on one Media Services account. You choose the operations it may call, so ones like deleting a filter or patching its time range are not included unless you add them.

Credential isolation

Your Azure AD service principal credentials are stored once, encrypted, by your own Jentic One instance and injected as a bearer token scoped to management.azure.com at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Azure Media Services account filter' or 'list account filters', and Jentic returns the matching Microsoft.Media operation with its input schema so the agent calls the right endpoint without reading the provider docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Media Services Management Client

→

Manages the Media Services account, Streaming Endpoints, Transforms, and Jobs that consume these filters.

Use to provision the Media Services account and Streaming Endpoint that account filters apply to.

Complementary

Azure Monitor Management Client

→

Configure metric alerts and diagnostic settings on the Media Services account.

Use to monitor Streaming Endpoint and encoding job health alongside filter management.

Complementary

Azure Log Analytics

→

Centralise diagnostic logs from the Media Services account in a Log Analytics workspace.

Pair with this API to retain and query Streaming Endpoint and key delivery logs.

FAQs

Specific to using Azure Media Services API through Jentic.

Why is there no official OpenAPI spec for Azure Media Services?

Microsoft Azure does not publish a single consolidated OpenAPI specification for the Microsoft.Media account filter control plane at this revision. Jentic generates and maintains this spec so that AI agents and developers can call Azure Media Services via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does this API use?

The API uses Azure Active Directory OAuth 2.0; agents acquire a token for the https://management.azure.com/ resource and pass it as a Bearer token. Jentic stores the service principal credentials in its vault and injects scoped tokens at call time.

Does this API let me upload videos or transcode assets?

No. This slice of the Media Services API only manages account-level filters. To upload assets, run encoding jobs, or stream content you call the Asset, Transform, Job, and StreamingEndpoint endpoints elsewhere in the Microsoft.Media control plane and the data-plane streaming URLs.

How do I create an account filter through Jentic?

Search Jentic for 'create an Azure Media Services account filter', load the resulting PUT operation on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/accountFilters/{filterName}, then execute it with the filter name and presentationTimeRange or firstQuality body. Install with pip install jentic and run the async search-load-execute flow.

What is the difference between an account filter and an asset filter?

Account filters apply to every Asset in the Media Services account; asset filters scope to a single Asset. This API exposes account filters only - asset filters live under the Asset resource path of the broader Media Services control plane.

What are the rate limits for this API?

Azure Resource Manager applies subscription-level throttling - typically 12,000 reads and 1,200 writes per hour per subscription. Filter CRUD is light and rarely hits these limits in practice.

Can I limit what my agent is allowed to do with the Azure Media Services API?

Yes. Because you run Jentic One yourself, your own rules decide which account filter operations the agent may call, so you can grant listing and reading filters while withholding the create, patch, and delete operations. The subscription, resource group, account name, and filter name all sit in the request path, letting a rule pin the agent to filters on a single Media Services account. You also control the stored Azure AD service principal credentials the agent uses, so it can only reach the account filters you have authorized.

GET STARTED

Start building with Azure Media Services API

Explore with Jentic One
View OpenAPI Document