CostManagementClient

Name: CostManagementClient API
Brand: Cost Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceExpense Managementoauth213 EndpointsREST

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.

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.

Install Jentic One Beta (Self-Hosted)

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

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

GET STARTED

Start building with CostManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CostManagementClient, keeping it validated and agent-ready.

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.

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure service principal credentials are encrypted in the Jentic vault. Agents receive scoped ARM bearer tokens at runtime; the client secret never enters the agent context.

Intent-based discovery

Agents search by intent ('create azure budget' or 'list cost views') and Jentic returns the matching CostManagement operation with its schema, avoiding the need to load all 13 endpoints.

Time to first call

Direct ARM integration: 1-2 days for AAD app registration, MSAL token handling, and budget schema marshalling. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Consumption Management

Returns actual usage and cost data to pair with the budgets defined here.

Use Consumption Management when an agent needs real spend or usage records; use CostManagementClient when defining budgets or saved views.

Complementary

Policy Tracked Resources

Track policy-compliant resources alongside cost budgets for governance dashboards.

Use when an agent needs policy compliance signals to combine with cost guardrails.

Alternative

Azure Monitor Management

Configure metric-based budget-style alerts via Azure Monitor instead of cost-management notifications.

Choose Monitor when alerting on resource-level metrics; choose CostManagementClient when alerting on aggregate spend thresholds.

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 at https://app.jentic.com/sign-up.

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.