Microsoft Azure CostManagementClient
Browse all Azure APIs43
AI ReadinessFoundational (D-)43/100
Agent-ready OpenAPI document · curated by JenticFinanceExpense Managementoauth213 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create and manage Azure Cost Management budgets and saved cost views across subscription, resource group, and billing scopes, with 13 operations on the Microsoft.CostManagement resource provider.
Use for: I need to create a $5,000 monthly budget on a subscription with a 90% alert, I want to delete a saved cost view that is no longer needed, List all budgets currently configured on a billing account scope, Get the current spend against the 'prod-monthly' budget
Not supported: Does not return actual cost or usage data, run cost queries, or expose pricing - use for managing budgets and saved cost views only.
Jentic publishes the only available OpenAPI specification for CostManagementClient, keeping it validated and agent-ready. The Azure Cost Management REST API exposes 13 operations across 7 paths for managing budgets and saved cost views at the subscription, resource group, billing account, department, enrollment account, and management group scope. Use it to create spending budgets with cost thresholds and notifications, manage shared and private cost analysis views, and list cost-management metadata to drive automated cost-control workflows on Azure spend.
Install Jentic One Beta
Connect the CostManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CostManagementClient, 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-cost-management" | sh2
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-cost-management" | 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.
Capabilities
What an agent can do with CostManagementClient API.
Create and update budgets with monthly, quarterly, or annual cost thresholds at any Azure scope
Configure budget notifications that fire when actual or forecast spend crosses defined percentages
List and delete saved cost analysis views at the global and per-scope level
Retrieve a specific budget by name to inspect current consumption versus its threshold
Enumerate available Microsoft.CostManagement resource provider operations for permission checks
Manage cost views shared across an organisation versus views scoped to a single subscription
Use Cases
Patterns agents use CostManagementClient API for, with concrete tasks.
★ Automated Subscription Budget Enforcement
Create per-subscription cost budgets with multi-tier notification thresholds (50%, 80%, 100%, 110%) so finance and engineering teams are alerted before overruns. The CreateOrUpdate budget endpoint accepts an amount, time grain, and a notifications map keyed by threshold percentage with email recipients and contact role lists. Pair with scheduled checks to confirm budgets stay in place across new subscriptions during landing-zone provisioning.
Create a budget named 'prod-monthly' on subscription /subscriptions/{id} with $5,000 monthly amount and email notifications at 80% actual and 100% forecast to finance@example.com
Curated Cost Analysis Views
Save reusable cost analysis views with predefined dimensions, filters, and chart types so teams open the same breakdown each month without rebuilding queries. Views can be created at the global level (visible across the tenant) or scoped to a billing account, subscription, or resource group. The API supports listing, retrieving, and deleting views by name to keep the view catalogue tidy as ownership changes.
List all cost views at the subscription scope and delete any view whose name starts with 'temp-'
FinOps Reconciliation Workflows
Programmatically inventory budgets across all in-scope subscriptions and management groups to confirm every workload has a budget guardrail. Combine the budget list endpoint with the consumption usage details endpoint (separate API) to reconcile actual spend against budget thresholds and surface unbudgeted spend. The control-plane API itself does not return usage data, so this use case requires pairing with the consumption API.
List all budgets at scope /subscriptions/{id} and report which budgets have notifications below the 80% threshold
AI Agent Cost Governance
An AI agent supporting a cloud platform team can stand up budgets and cost views on demand. Through Jentic the agent searches by intent ('create azure budget'), receives the Budgets_CreateOrUpdate operation schema, and executes the call with managed Azure credentials. The same flow handles deletion of stale views and listing of budgets across scopes for governance reports.
Search Jentic for 'create an Azure budget', load the Budgets_CreateOrUpdate schema, and execute it with the user-supplied scope, amount, and notification thresholds
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for costmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/{scope}/providers/Microsoft.CostManagement/budgets
List budgets at a given Azure scope
DELETE
/{scope}/providers/Microsoft.CostManagement/budgets/{budgetName}
Delete a budget at a scope
GET
/providers/Microsoft.CostManagement/views
List all global cost views
DELETE
/providers/Microsoft.CostManagement/views/{viewName}
Delete a global cost view
GET
/{scope}/providers/Microsoft.CostManagement/views
List cost views scoped to a billing account, subscription, or resource group
GET
/providers/Microsoft.CostManagement/operations
List Microsoft.CostManagement operations
GET
/{scope}/providers/Microsoft.CostManagement/budgets
List budgets at a given Azure scope
DELETE
/{scope}/providers/Microsoft.CostManagement/budgets/{budgetName}
Delete a budget at a scope
GET
/providers/Microsoft.CostManagement/views
List all global cost views
DELETE
/providers/Microsoft.CostManagement/views/{viewName}
Delete a global cost view
GET
/{scope}/providers/Microsoft.CostManagement/views
List cost views scoped to a billing account, subscription, or resource group
GET
/providers/Microsoft.CostManagement/operations
List Microsoft.CostManagement operations
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
CostManagementClient
- Foundational (D-)43/100
71
Foundational Compliance63
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
85%
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.
63
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.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
81%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Azure Cost Management by hand means an Azure AD app registration for the OAuth implicit flow against management.azure.com, MSAL token handling, and marshalling the budget body and its threshold notifications map yourself. Through Jentic you install once, import Cost Management from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The scope and budget name travel in the URL path (/{scope}/providers/Microsoft.CostManagement/budgets/{budgetName}), so a rule can pin the agent to one subscription or resource group scope. You choose the operations it may call, so destructive ones like deleting a budget or a saved cost view are not included unless you add them.
Credential isolation
Your Azure service principal credentials are stored once, encrypted, by your own Jentic One instance and injected as a short-lived ARM bearer token 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 cost budget with a 90 percent alert' or 'list cost views at a subscription scope', and Jentic returns the matching CostManagement operation such as Budgets_CreateOrUpdate with its schema so the agent calls the right endpoint without loading all 13 operations.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CostManagementClient API through Jentic.
Why is there no official OpenAPI spec for CostManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CostManagementClient 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 CostManagementClient API use?
It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. Through Jentic the service principal credentials live in the encrypted vault and the agent only ever sees a short-lived ARM bearer token.
Can I create budgets at multiple scope levels with this API?
Yes. The Budgets endpoints accept a {scope} path segment that supports subscription, resource group, billing account, department, enrollment account, and management group scopes. The same CreateOrUpdate body shape works at every scope.
What are the rate limits for the CostManagementClient API?
Azure Resource Manager applies subscription-level read and write throttling (typically 1,200 reads and 1,200 writes per hour). Cost Management additionally throttles list and query operations under heavy load with a 429 response and a Retry-After header.
How do I create a budget through Jentic?
Run pip install jentic and search for 'create azure budget'. Jentic returns the Budgets_CreateOrUpdate operation; load its schema and execute with the scope, budgetName, amount, timeGrain, and notifications map. Verify with Budgets_Get.
Does this API return actual cost or usage data?
No. This API manages budgets and saved views - it does not return spend or usage detail. Use the Consumption Management API (consumptionmanagementclient) for actual usage records and cost details.
Can I limit what my agent is allowed to do with the Microsoft Azure Cost Management API?
Yes. Because you run Jentic One yourself, your own rules decide which of the 13 operations the agent may call, so you can allow read operations like listing budgets and cost views while withholding destructive ones such as deleting a budget or deleting a saved cost view. The scope and budget name travel in the URL path (/{scope}/providers/Microsoft.CostManagement/budgets/{budgetName}), so you can pin the agent to a single subscription or resource group scope. The Azure service principal credentials stay under your control and are injected only at execution time, so the agent never touches them directly.
GET STARTED