Microsoft Azure APIs

237 APIs4,900 Endpoints17 Categories

API Catalog(6 of 237)

Azure Reservation

Jentic publishes the only available OpenAPI specification for Azure Reservation, keeping it validated and agent-ready. The API manages Microsoft.Capacity reservation orders and the individual reservations within them, the discounted commitment instruments that Azure customers buy to reduce VM, SQL, and other resource costs. It supports calculating prices, listing and reading reservation orders, splitting and merging reservations, updating their applied scopes, and reading revision history.

14 endpoints

CommerceManagementClient

Jentic publishes the only available OpenAPI specification for CommerceManagementClient, keeping it validated and agent-ready. The Admin Commerce Management Client is the Azure Stack admin-side API for retrieving subscriber usage aggregates and rotating the encryption used to protect commerce data in a stamp. It exposes 3 endpoints: a list of supported provider operations, a query over subscriberUsageAggregates by reporting period, and a triggerable updateEncryption action. Use it from an Azure Stack operator context to feed billing pipelines or roll the storage encryption key.

3 endpoints

ConsumptionManagementClient

Jentic publishes the only available OpenAPI specification for ConsumptionManagementClient, keeping it validated and agent-ready. The Consumption Management Client provides read access to consumption resources for Azure Enterprise Subscriptions across 25 endpoints — balances, reservation summaries and details, reservation transactions, reservation recommendations, marketplaces, budgets, charges, forecasts, and more. Use it to feed FinOps dashboards, reservation-utilisation reports, and budget-burn alerts without scraping the cost portal.

25 endpoints

CostManagementClient

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.

13 endpoints

Software Plan RP

Jentic publishes the only available OpenAPI specification for Software Plan RP, keeping it validated and agent-ready. The Azure Software Plan API exposes the Microsoft.SoftwarePlan resource provider so agents can register the provider on a subscription and then create, list, and revise Azure Hybrid Use Benefit (AHB) software plans. AHB plans let customers apply existing on-premises Windows Server, SQL Server, and RHEL/SUSE licenses to Azure VMs to reduce billable compute cost — this API is the control plane for those plan assignments and their revisions.

8 endpoints

UsageManagementClient

Jentic publishes the only available OpenAPI specification for UsageManagementClient, keeping it validated and agent-ready. The Microsoft.Commerce Usage Management Client returns Azure billing telemetry — RateCard data describing the meter catalog and prices for an offer in a region and currency, plus UsageAggregates time-bucketed metered usage for a subscription. Agents use it to forecast cloud spend, attribute costs to resource groups, and feed cost figures into FinOps dashboards. Authentication is Azure Active Directory OAuth 2.0 on management.azure.com.

2 endpoints

Connect Your Agent

Step 1: 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

Step 2: 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.