Microsoft Azure CommerceManagementClient

Name: CommerceManagementClient API
Brand: CommerceManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingoauth23 EndpointsREST

For Agents

Pull subscriber usage aggregates and trigger encryption rotation on an Azure Stack stamp's commerce subsystem.

Install Jentic One Beta

Connect the CommerceManagementClient to your agent

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

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.

Capabilities

What an agent can do with CommerceManagementClient API.

Pull subscriber usage aggregates for a reporting window to feed downstream billing or chargeback systems

Trigger an updateEncryption action to rotate the encryption protecting commerce data on the stamp

List the supported provider operations exposed by Microsoft.Commerce.Admin

GET STARTED

Start building with CommerceManagementClient API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use CommerceManagementClient API for, with concrete tasks.

★ Feed Azure Stack usage into a chargeback pipeline

Operators of an Azure Stack stamp need to bill internal tenants for the resources they consume. The Commerce Management Client returns subscriberUsageAggregates for a chosen reporting period, which can be flattened into a chargeback ledger and reconciled against tenant-side records. This avoids hand-extracting usage from the Azure Stack portal.

Retrieve subscriberUsageAggregates from the stamp for the previous calendar month and emit a CSV grouped by subscriptionId.

Rotate commerce encryption on schedule

Compliance regimes commonly require encryption-at-rest keys to be rotated on a fixed cadence. The Commerce Management Client exposes an updateEncryption action that triggers a stamp-side key rotation, so an operator can run rotation as a scheduled job rather than a manual portal task.

Invoke POST /subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/updateEncryption on the stamp and confirm the operation status reaches Succeeded.

Discover available admin operations

Before automating an Azure Stack workflow an operator needs to know which Microsoft.Commerce.Admin operations the stamp actually advertises. The operations endpoint returns the registered set, which can be diffed across stamp versions to detect deprecated or newly available actions.

GET /providers/Microsoft.Commerce.Admin/operations and return the names of all supported operations.

Agent-driven Azure Stack billing extraction

An AI agent integrated through Jentic can run a monthly job that pulls subscriberUsageAggregates from the stamp, normalises the records, and posts them to a chargeback system or a finance warehouse. Jentic's intent search exposes the right CommerceManagementClient operation and the AAD token stays scoped through the vault.

On the first of each month, call subscriberUsageAggregates for the prior month and POST the JSON to the finance warehouse webhook.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Commerce.Admin/operations

List supported Microsoft.Commerce.Admin operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/subscriberUsageAggregates

Retrieve subscriber usage aggregates for a reporting period

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/updateEncryption

Rotate the encryption protecting commerce data

GET

/providers/Microsoft.Commerce.Admin/operations

List supported Microsoft.Commerce.Admin operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/subscriberUsageAggregates

Retrieve subscriber usage aggregates for a reporting period

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/updateEncryption

Rotate the encryption protecting commerce data

Why Jentic?

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

Credential isolation

Azure AD operator tokens are stored encrypted in the Jentic vault. Agents receive a scoped access token tied to the Azure Stack stamp — refresh tokens never enter the agent context.

Intent-based discovery

Agents search by intent (for example 'pull azure stack usage' or 'rotate commerce encryption') and Jentic returns the matching Microsoft.Commerce.Admin operation with its input schema, so the agent does not have to memorise Azure Stack admin paths.

Time to first call

Direct integration: 1-2 days for AAD operator-token plumbing and Azure Stack endpoint discovery. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using CommerceManagementClient API through Jentic.

Why is there no official OpenAPI spec for CommerceManagementClient?

Microsoft Azure does not publish a consolidated OpenAPI specification for the Azure Stack Commerce Admin API. Jentic generates and maintains this spec so that AI agents and developers can call CommerceManagementClient 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 CommerceManagementClient use?

It uses Azure Active Directory OAuth 2.0 with the implicit flow at https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. The caller must hold an Azure Stack operator role. Through Jentic the AAD token sits in the encrypted vault and never enters the agent context.

Can I pull billing data with the CommerceManagementClient?

Yes — issue GET /subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/subscriberUsageAggregates with reportedStartTime and reportedEndTime query parameters. The response contains usage records aggregated per subscriber for the reporting window.

What are the rate limits for the CommerceManagementClient?

The Azure Stack admin endpoints inherit Azure Resource Manager throttling (subscription-level read and write quotas). The spec does not declare separate rate-limit headers; expect ARM 429 responses if a billing job hammers the stamp.

How do I rotate commerce encryption through Jentic?

Search Jentic for 'rotate azure stack commerce encryption', load the schema for POST /subscriptions/{subscriptionId}/providers/Microsoft.Commerce.Admin/updateEncryption, and execute it. Run pip install jentic to get the SDK.

Is the CommerceManagementClient free?

The admin endpoints themselves are free; you must hold an Azure Stack operator role. Costs come from running the Azure Stack stamp, not from calling this management API.