Microsoft Azure GalleryManagementClient

Name: GalleryManagementClient API
Brand: Azure Stack Gallery Admin
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth21 Endpoints

Install Jentic One Beta

Connect the GalleryManagementClient to your agent

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

List the supported administrative operations for the Microsoft.Gallery.Admin resource provider

Discover gallery management actions available on an Azure Stack Hub instance

Verify which operation surface a given Azure Stack admin region exposes

GET STARTED

Start building with GalleryManagementClient API

Explore with Jentic

View OpenAPI Document

For Agents

List available administrative gallery operations on an Azure Stack Hub deployment so an agent can discover what actions the Microsoft.Gallery.Admin provider supports.

Use for: List all admin gallery operations available on this Azure Stack deployment, Check whether the Microsoft.Gallery.Admin provider is exposed on this stamp, Retrieve the operations catalogue for the Azure Stack gallery, Find what gallery admin actions an operator can perform here

Not supported: Does not create gallery items, sync marketplace content, or manage stamp updates - use for discovering gallery admin operations only.

Jentic publishes the only available OpenAPI specification for GalleryManagementClient, keeping it validated and agent-ready. The Azure Stack Admin Gallery Management API exposes the discoverable operations surface for the marketplace gallery on an Azure Stack Hub deployment. Operators use it to enumerate the administrative actions available against the Microsoft.Gallery.Admin resource provider on a private Azure Stack environment. It runs against the Azure Stack admin endpoint at adminmanagement.local.azurestack.external with Azure AD OAuth2.

Use Cases

Patterns agents use GalleryManagementClient API for, with concrete tasks.

★ Operations discovery on an Azure Stack stamp

An Azure Stack operator needs to know which administrative gallery operations the local stamp supports before scripting against it. Calling Operations_List on Microsoft.Gallery.Admin returns the full catalogue of supported actions so the operator can plan a maintenance script. The endpoint is read-only and safe to call from automation jobs at any time.

Call GET /providers/Microsoft.Gallery.Admin/operations against the Azure Stack admin endpoint and return the list of supported operation names.

Tooling introspection for Azure Stack utilities

Internal tooling that wraps Azure Stack admin APIs uses Operations_List to verify which actions a stamp exposes and dynamically gate UI options. The single-endpoint surface is purpose-built for this kind of reflection. Useful when the same tool runs across stamps with different update levels.

Probe the Azure Stack admin endpoint for the Microsoft.Gallery.Admin operations list and surface any unexpected operation names.

AI agent discovery via Jentic

An agent given an Azure Stack admin endpoint uses Jentic to find the Operations_List call, load its schema, and execute it without holding raw operator credentials. The result is a structured list the agent can reason over to decide which subsequent admin APIs are worth invoking.

Use Jentic to search for 'azure stack gallery operations', load Operations_List, and execute it against the Azure Stack admin endpoint configured for the operator.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Gallery.Admin/operations

List available gallery admin operations

GET

/providers/Microsoft.Gallery.Admin/operations

List available gallery admin operations

Why Jentic?

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

Credential isolation

Your Azure AD admin credentials for the Azure Stack stamp are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The operator secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Azure Stack gallery operations', and Jentic returns the Operations_List operation with its input schema so the agent calls the discovery endpoint without browsing the Azure Stack admin docs.

Time to first call

FAQs

Specific to using GalleryManagementClient API through Jentic.

Why is there no official OpenAPI spec for GalleryManagementClient?

Microsoft Azure does not publish a stand-alone OpenAPI specification for the Azure Stack Admin Gallery Management API. Jentic generates and maintains this spec from the Azure Stack admin REST surface so that AI agents and developers can call GalleryManagementClient 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 Azure Stack Gallery Admin API use?

The API uses Azure AD OAuth2 against the Azure Stack admin endpoint at adminmanagement.local.azurestack.external, declared as the azure_auth security scheme. Through Jentic, operator credentials are stored encrypted in the vault and exchanged for a scoped bearer token at execution time.

What does this API actually do?

It exposes a single GET on /providers/Microsoft.Gallery.Admin/operations that returns the catalogue of administrative actions the gallery resource provider supports on an Azure Stack stamp. It is a discovery endpoint, not a management endpoint - there are no create or delete operations on this client.

What are the rate limits?

Azure Stack admin endpoints inherit ARM-style throttling, typically thousands of reads per hour per subscription. The single Operations_List endpoint is lightweight and unlikely to be rate-limited in normal admin use.

How do I list gallery operations through Jentic?

Run jentic.search('list azure stack gallery operations'), load the Operations_List schema, and execute it with no parameters beyond the bearer token. Jentic returns the JSON catalogue from the Microsoft.Gallery.Admin provider.

Can I limit what my agent is allowed to do with the Azure Stack Gallery Admin API?

Yes. Because Jentic One is self-hosted, you decide which operations and credentials your agent can use, and this API exposes only a single read-only call, Operations_List, a GET on /providers/Microsoft.Gallery.Admin/operations. You can restrict the agent to that one operation, which is all this discovery client provides. That call only enumerates the supported admin actions on the stamp and changes nothing.