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 / AI/ML / Azure / Azure ML Web Services Management Client
Azure ML Web Services Management Client logo

Microsoft Azure Azure ML Web Services Management Client

Browse all Azure APIs
42
AI ReadinessFoundational (D-)42/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticAI/MLMl Inferenceoauth29 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Deploy, patch, and inspect Azure Machine Learning web services and retrieve their access keys so an agent can manage classic ML inference endpoints programmatically.

Use for: Deploy a new Azure ML web service from a package, I want to retrieve the access keys for an Azure ML web service, List all Azure ML web services in a resource group, Patch the title of a deployed Azure ML web service

Not supported: Does not handle model training, dataset management, or modern Azure ML online endpoints - use for ML Studio (classic) web service deployment, key, and inventory operations only.

Jentic publishes the only available OpenAPI specification for Azure ML Web Services Management Client, keeping it validated and agent-ready. The API manages Azure Machine Learning web services published from ML Studio (classic), supporting create-or-update, get, patch, delete, region-blob creation, and key retrieval under the Microsoft.MachineLearning provider. It is the control surface for deploying inference endpoints, rotating their access keys, and listing every web service in a resource group or subscription.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Azure ML Web Services Management Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure ML Web Services Management Client, 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-ml-web-services-management-client" | 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-ml-web-services-management-client" | 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 ML Web Services Management Client API.

Create or update an Azure ML web service with its package, properties, and runtime configuration

Patch a deployed web service to update properties without a full redeploy

Retrieve the primary and secondary access keys for an Azure ML web service

List every Azure ML web service in a subscription or scoped to a resource group

Create a regional blob upload location for staging a web service package before deployment

Delete an Azure ML web service when its inference endpoint is decommissioned

Use Cases

Patterns agents use Azure ML Web Services Management Client API for, with concrete tasks.

★ Deploy an ML Studio Web Service from CI

Trigger an Azure ML web service deployment from a continuous integration pipeline once a new model package has been built. The PUT on /webServices/{webServiceName} accepts the package payload, properties, and the runtime tier, and the operation returns a long-running operation handle so the pipeline can poll until the service is ready. This avoids manual ML Studio publishing and keeps deployments versioned alongside code.

Create or update the Azure ML web service 'fraud-scorer-v3' in resource group 'ml-rg' with the latest package payload and poll until provisioningState is Succeeded

Rotate Web Service Access Keys

Periodically rotate the primary and secondary access keys for an Azure ML web service so that consumer applications can switch between keys with no downtime. The listKeys action returns both keys for a single web service, allowing the caller to update downstream consumers before regenerating. This is critical for SOC 2 and ISO 27001 controls that require regular credential rotation on production inference endpoints.

Call POST listKeys on web service 'fraud-scorer-v3' in resource group 'ml-rg' and return both primary and secondary keys for downstream rotation

Inventory and Tag Web Services for Cost Allocation

List every Azure ML web service in a subscription and patch tags on each so that cost reports can attribute inference spend to the correct cost centre. The subscription-scoped GET returns paginated web services across all resource groups, and PATCH on /webServices/{webServiceName} applies tag updates without modifying the deployed package. This produces a complete inventory in seconds rather than walking resource groups by hand.

List every Azure ML web service in subscription '00000000-0000-0000-0000-000000000000' and patch each one to add the tag costCentre=ml-platform

Agent-Driven ML Endpoint Audit via Jentic

An AI agent uses Jentic to discover every Azure ML web service in a tenant, fetch each endpoint's keys via listKeys, and emit an audit report covering deployment age, location, and access key rotation status. The agent searches Jentic for 'list azure ml web services', loads the schema, and chains the call into per-service listKeys requests. Azure AD bearer tokens are sourced from your Jentic One instance per call.

Search Jentic for 'list azure ml web services', list every web service in the subscription, then call listKeys on each and emit an audit report ranking endpoints by last-modified date

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for azure ml web services management client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Create or update a web service

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Get a web service

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Patch a web service

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Delete a web service

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}/listKeys

List access keys for a web service

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MachineLearning/webServices

List web services in a subscription

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}/CreateRegionalBlob

Create a regional blob for package staging

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Create or update a web service

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Get a web service

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Patch a web service

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}

Delete a web service

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}/listKeys

List access keys for a web service

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MachineLearning/webServices

List web services in a subscription

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}/CreateRegionalBlob

Create a regional blob for package staging

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 ML Web Services Management Client

- Foundational (D-)
42/100
57
Foundational Compliance
55
Developer Experience & Jentic Compatibility
22
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
57

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4
87%

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

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

55

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

22

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
88%

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.

0%

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 Azure ML Web Services client by hand means registering an Azure AD app, minting tokens for https://management.azure.com/, and polling the long-running deployment operations while handling ARM throttling and key retrieval yourself. Through Jentic you install once, import Azure ML Web Services Management Client from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The web service id travels in the URL path (/webServices/{webServiceName}/...), so a rule can pin your agent to one web service: it can read that service and list its keys and nothing else. You choose the operations it may call, so destructive ones like deleting a web service are not included unless you add them.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list azure ml web services' or 'rotate an ML web service access key', and Jentic returns the matching Microsoft.MachineLearning operation with its input schema so the agent calls the right endpoint without browsing the ARM reference.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure ML Commitment Plans Management Client

→

Manages the commitment plans that web services attach to for committed-capacity pricing.

Use alongside this API when the agent needs to bind a deployed web service to committed capacity rather than pay-as-you-go billing.

Alternative

Azure Machine Learning Workspaces

→

Modern Azure ML workspaces API - the successor surface for current Azure ML deployments.

Choose this for current Azure ML workspaces, online endpoints, and registered models; web services are the legacy ML Studio (classic) deployment surface.

Complementary

Azure Machine Learning Model Management Service

→

Registers and versions models that can be deployed as web services.

Use to register and version a model artefact before publishing it through the web services API.

FAQs

Specific to using Azure ML Web Services Management Client API through Jentic.

Why is there no official OpenAPI spec for Azure ML Web Services Management Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure ML Web Services Management Client 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 the Azure ML Web Services Management Client use?

The API uses Azure Active Directory OAuth 2.0 (the azure_auth scheme) with the user_impersonation scope on https://management.azure.com/. Through Jentic, the bearer token is fetched from your Jentic One instance and injected at call time so the agent never sees the raw client secret.

How do I retrieve the access keys for a deployed Azure ML web service?

POST to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearning/webServices/{webServiceName}/listKeys. The response contains both primary and secondary keys, which you can rotate by updating consumers and then regenerating one key at a time.

What are the rate limits for the Azure ML Web Services Management Client?

The spec does not declare per-API limits; calls are throttled by Azure Resource Manager's per-subscription budget for read and write operations on Microsoft.MachineLearning. Honour the Retry-After header on HTTP 429 before retrying.

How do I deploy a new ML web service through Jentic?

Search Jentic for 'deploy an azure ml web service', load the schema for PUT /webServices/{webServiceName}, supply your package payload, and execute. Jentic injects the Azure AD bearer token automatically so the agent only handles the deployment payload.

Is the Azure ML Web Services API free?

Control plane calls are free. The deployed web services bill against either pay-as-you-go transactions and compute or against an attached Azure ML commitment plan; both are charged at standard Azure ML rates.

Can I limit what my agent is allowed to do with the Azure ML Web Services Management Client API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the web service id travels in the URL path, so a rule can pin the agent to a single web service. You choose the exact operations it may call, so you can grant read-only access such as getting a web service and calling listKeys while excluding destructive ones like deleting or patching a web service unless you add them. The stored Azure AD credential is exchanged for a short-lived bearer token at call time and never enters the agent's prompt or logs.

GET STARTED

Start building with Azure ML Web Services Management Client API

Explore with Jentic One
View OpenAPI Document