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 / CognitiveServicesManagementClient
CognitiveServicesManagementClient logo

Microsoft Azure CognitiveServicesManagementClient

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

Know of an official OpenAPI document? Contribute it →

For Agents

Provision Azure Cognitive Services accounts, list and regenerate their access keys, and check SKU and domain availability across regions.

Use for: I need to provision a new Azure Cognitive Services account for a vision workload, Regenerate the primary key for a Cognitive Services account that may have leaked, List all Cognitive Services accounts in a resource group, Check whether the account name 'agent-vision-prod' is available in westeurope

Not supported: Does not call Vision, Speech, Language, or Decision data-plane endpoints, run inference, or manage billing - use for provisioning and key management of Cognitive Services accounts only.

Jentic publishes the only available OpenAPI specification for CognitiveServicesManagementClient, keeping it validated and agent-ready. The Cognitive Services Management Client is the Azure Resource Manager API for provisioning and administering Cognitive Services accounts under a subscription. It exposes 14 endpoints for creating accounts, regenerating subscription keys, listing available SKUs by location, checking domain name availability, and enumerating supported account kinds. Use it to spin up Vision, Language, Speech, or Decision resource accounts and rotate their keys without touching the Azure Portal.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the CognitiveServicesManagementClient to your agent

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

Create and update Cognitive Services accounts under a resource group with a chosen SKU and kind

List the access keys for a Cognitive Services account and regenerate Key1 or Key2 on demand

Check whether a desired account name is available in a region before provisioning

Enumerate the SKUs and kinds available for a given location and account type

Retrieve subscription-wide usage of Cognitive Services account quotas

Delete a Cognitive Services account and free its assigned name and resources

Use Cases

Patterns agents use CognitiveServicesManagementClient API for, with concrete tasks.

★ Provision Cognitive Services for a new agent project

Spin up a Cognitive Services account on demand when an agent project needs vision, speech, or language capabilities. The Management Client creates the account, returns the endpoint and access keys, and exposes the chosen SKU so the consuming workload can call the data-plane API straight away. This avoids manual Azure Portal clicks and keeps account creation reproducible across environments.

Create a Cognitive Services account named 'agent-vision-prod' of kind ComputerVision with SKU S1 in resource group ai-rg, then return the endpoint and Key1.

Rotate Cognitive Services subscription keys

When a Cognitive Services key is suspected of being exposed, an operator needs to rotate it without downtime. The Management Client lists the two keys for an account and regenerates either Key1 or Key2 individually so traffic can be cut over to the surviving key first. This pattern supports zero-downtime rotation aligned with Azure's two-key model.

List the access keys for account 'agent-vision-prod' in resource group ai-rg, regenerate Key2, and return the new Key2 value.

Pre-flight checks before deployment

Before an infrastructure-as-code deployment runs, an agent can verify that the desired account name is free in the target region and that the SKU it plans to request is offered there. The Management Client exposes domain availability and SKU availability checks so the deployment can fail fast with a clear message instead of a partial rollout.

Check whether the SKU 'S2' for kind 'TextAnalytics' is available in westeurope, and whether the name 'agent-text-prod' is available globally.

Agent-driven account inventory and cleanup

An AI agent integrated through Jentic can walk a subscription and resource group, list all Cognitive Services accounts, identify those that are unused or out of date, and delete them. Discovery happens through Jentic's intent search so the agent does not need to memorise Azure Resource Manager paths, and credential isolation keeps the OAuth token scoped to the operation.

List all Cognitive Services accounts in subscription 00000000-0000-0000-0000-000000000000, filter to those tagged env=dev with no usage in 30 days, and delete each one.

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for cognitiveservicesmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/accounts

List all Cognitive Services accounts in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}

Create or update a Cognitive Services account

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}

Delete a Cognitive Services account

POST

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/checkDomainAvailability

Check whether an account domain name is available

POST

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/locations/{location}/checkSkuAvailability

Check SKU availability for a location and kind

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/skus

List supported SKUs for the resource provider

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/accounts

List all Cognitive Services accounts in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}

Create or update a Cognitive Services account

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}

Delete a Cognitive Services account

POST

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/checkDomainAvailability

Check whether an account domain name is available

POST

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/locations/{location}/checkSkuAvailability

Check SKU availability for a location and kind

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CognitiveServices/skus

List supported SKUs for the resource provider

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.

C

CognitiveServicesManagementClient

- Foundational (D)
45/100
66
Foundational Compliance
59
Developer Experience & Jentic Compatibility
24
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
66

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 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).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

59

Developer Experience & Jentic Compatibility

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

Grade: C+Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

43%

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.

24

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
82%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

14%

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 CognitiveServicesManagementClient by hand means configuring Azure AD OAuth2 against management.azure.com, keeping to the control plane so you provision accounts and manage keys rather than call Vision or Speech data-plane endpoints, and threading account name ids through every Microsoft.CognitiveServices path yourself. Through Jentic you install once, import the CognitiveServicesManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the account name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}), so a rule can pin your agent to one Cognitive Services account. You choose the operations it may call, so destructive ones like deleting an account or overwriting one with PUT are not included unless you add them.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'provision a Cognitive Services account' or 'check SKU availability in a region', and Jentic returns the matching Accounts operation with its input schema so the agent calls the right ARM path without browsing the Microsoft.CognitiveServices reference.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Compute Management Client

→

Provisions virtual machines that often host workloads consuming Cognitive Services

Choose Compute Management Client when the agent also needs to provision the VMs that will call the Cognitive Services endpoints

Alternative

Machine Learning Compute Management Client

→

Manages Azure Machine Learning compute targets when custom models are needed instead of pre-built Cognitive Services

Choose Machine Learning Compute when the agent needs to train or deploy custom models rather than consume Microsoft's pre-built AI services

Complementary

Consumption Management Client

→

Reports billing and usage for the Cognitive Services accounts created here

Choose Consumption Management when the agent needs to report cost or usage of provisioned Cognitive Services accounts

FAQs

Specific to using CognitiveServicesManagementClient API through Jentic.

Why is there no official OpenAPI spec for CognitiveServicesManagementClient?

Microsoft Azure does not publish a single consolidated OpenAPI specification for the Cognitive Services Management Client. Jentic generates and maintains this spec so that AI agents and developers can call CognitiveServicesManagementClient 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 CognitiveServicesManagementClient use?

It uses Azure Active Directory OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. Through Jentic, the AAD token is held in the encrypted vault and the agent receives a scoped access token instead of the raw bearer credential.

Can I create a Cognitive Services account with the CognitiveServicesManagementClient?

Yes. Issue PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName} with the desired SKU, kind (for example ComputerVision or TextAnalytics), and location. The response contains the endpoint and provisioning state for the new account.

What are the rate limits for the CognitiveServicesManagementClient?

Azure Resource Manager applies subscription-level read and write throttling - typically 12,000 reads and 1,200 writes per hour per subscription. The CognitiveServicesManagementClient inherits these limits; the spec does not declare separate rate-limit headers.

How do I rotate a Cognitive Services key through Jentic?

Search Jentic for 'regenerate cognitive services key', load the schema for POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}/regenerateKey, and execute it with keyName set to Key1 or Key2. Run pip install jentic to get the SDK.

Is the CognitiveServicesManagementClient free?

Calling the management API itself is free, but each Cognitive Services account you provision is billed against its chosen SKU (F0 free tier, S0/S1/S2 paid tiers) and on usage of the underlying data-plane API.

Can I limit what my agent is allowed to do with the CognitiveServicesManagementClient?

Yes. Because you run Jentic One yourself, you decide which operations your agent may call, so read-only work like listing accounts, checking domain and SKU availability, or listing keys can be allowed while destructive ones such as deleting an account or overwriting it with PUT stay out unless you add them. This API also puts the account name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}), so your own rule can pin the agent to a single Cognitive Services account. Your Azure AD credential is stored once by your instance and injected only at execution time, never entering the agent's prompt or logs.

GET STARTED

Start building with CognitiveServicesManagementClient API

Explore with Jentic One
View OpenAPI Document