Microsoft Azure Marketplace RP Service

Name: Marketplace RP Service API
Brand: Marketplace RP Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth29 Endpoints

Install Jentic One Beta

Connect the Marketplace RP Service to your agent

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

Create or update a tenant-scoped private store to control which marketplace offers users see

List the private stores configured for the current tenant

Admit a specific marketplace offer to a private store so it becomes deployable

GET STARTED

Start building with Marketplace RP Service API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Marketplace RP Service API for, with concrete tasks.

★ Curate a private marketplace catalog

Procurement and platform teams use the API to create a tenant-level private store and admit only the marketplace offers the organisation has reviewed and approved. This restricts what end users can deploy from the Azure portal marketplace, removing the risk of unvetted third-party software entering production subscriptions while still letting teams self-serve approved offers.

PUT /providers/Microsoft.Marketplace/privateStores/{PrivateStoreId} to create the store, then PUT /providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId} for each approved offer.

Audit which marketplace offers are deployable

Compliance teams query the offers list under a private store to confirm which marketplace items users can deploy and trace back the publishers behind each one. Combining the list output with internal procurement records produces an attestation that only approved software is reachable through self-service marketplace deployment.

GET /providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers and emit a CSV of offer IDs and publisher IDs cross-checked against the approved-software list.

Revoke an approved marketplace offer

When an offer is deprecated or fails a renewed security review, the agent removes it from the private store with a single DELETE. Existing deployments remain in place, but new deployments of the offer through the Azure portal are blocked because the store no longer admits it.

DELETE /providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId} for the offer and confirm the offer no longer appears in PrivateStoreOffers_List.

Agent-driven catalog management

Through Jentic, an AI agent can react to a procurement ticket and admit or revoke marketplace offers automatically. The agent searches Jentic for 'admit marketplace offer to private store', loads the input schema, and executes with the private store ID and offer ID. Jentic injects the Azure AD token at execution time, so the agent never sees raw secrets.

Use Jentic search 'admit azure marketplace offer', load PrivateStoreOffer_CreateOrUpdate, supply private store ID and offer ID, and execute.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for marketplace rp service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}

Create or update a private store

GET

/providers/Microsoft.Marketplace/privateStores

List private stores in the tenant

GET

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}

Get a private store by ID

PUT

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId}

Admit an offer to a private store

GET

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers

List admitted offers

DELETE

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId}

Revoke an admitted offer

PUT

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}

Create or update a private store

GET

/providers/Microsoft.Marketplace/privateStores

List private stores in the tenant

GET

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}

Get a private store by ID

PUT

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId}

Admit an offer to a private store

GET

/providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers

List admitted offers

Why Jentic?

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

Credential isolation

Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. The raw secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'admit a marketplace offer to an azure private store' or 'list admitted offers', and Jentic returns the matching PrivateStore or PrivateStoreOffer operation with its input schema so the agent calls the right endpoint without reading the Azure REST docs.

Time to first call

FAQs

Specific to using Marketplace RP Service API through Jentic.

Why is there no official OpenAPI spec for Marketplace RP Service?

Microsoft Azure does not publish a standalone OpenAPI specification for the marketplace private store resource provider. Jentic generates and maintains this spec so that AI agents and developers can call Marketplace RP Service 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 Marketplace RP Service use?

The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Through Jentic, your Azure AD application credentials are stored encrypted in your Jentic One instance and exchanged for a short-lived bearer token at execution time.

Can I admit a marketplace offer to a private store with this API?

Yes. Call PUT /providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId} with a body that identifies the offer. Once admitted, end users in the tenant can deploy that offer from the Azure portal marketplace; non-admitted offers are filtered out of their view.

What are the rate limits for the Marketplace API?

The endpoints inherit the standard Azure Resource Manager throttle quotas, surfaced through x-ms-ratelimit-remaining-* response headers. Bulk admit operations should respect those headers and back off when the remaining quota approaches zero.

How do I curate a private store through Jentic?

Search Jentic for 'create azure private store', load PrivateStore_CreateOrUpdate, supply the desired store name and tenant settings, then execute. Chain PrivateStoreOffer_CreateOrUpdate for each offer you want admitted, then verify with PrivateStoreOffers_List.

Does revoking an offer remove existing deployments?

No. DELETE /providers/Microsoft.Marketplace/privateStores/{PrivateStoreId}/offers/{OfferId} removes the offer from the admitted list, blocking new deployments through the marketplace. Resources already deployed from that offer continue to run normally and must be retired through their own resource provider APIs.

Is the Marketplace API free?

The control-plane API itself does not incur charges. Costs apply to the marketplace offers users actually deploy, billed under each offer's marketplace pricing. Standard Azure operational charges apply to those workloads.

Can I limit what my agent is allowed to do with the Microsoft Azure Marketplace Private Store API?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call and which credentials it may use. The private store ID and offer ID travel in the URL path, so a rule can pin the agent to admitting and listing offers under one named private store while leaving other stores untouched. You choose the exact operations it can run, so revoking an admitted offer is excluded unless you explicitly grant it, and your Azure AD credentials are only ever exchanged for a short-lived token at execution time.

Microsoft Azure Marketplace RP Service

Connect the Marketplace RP Service to your agent

Capabilities

Start building with Marketplace RP Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs