Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / ContainerInstanceManagementClient
ContainerInstanceManagementClient logo

Microsoft Azure ContainerInstanceManagementClient

Browse all Azure APIs
54
AI ReadinessFoundational (C)54/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureContainer Orchestrationoauth216 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run, stop, restart, and exec into serverless container groups on Azure Container Instances; pull logs and inspect cached image availability per region.

Use for: I need to run a one-shot container that processes a CSV and exits, Restart container group 'agent-worker' in resource group prod-rg, Pull the last 100 log lines from container 'sidecar' in group 'agent-worker', Exec the command '/bin/sh -c env' inside a running container

Not supported: Does not orchestrate Kubernetes clusters, manage container images in a registry, or run VMs - use for serverless single-container-group workloads on Azure Container Instances only.

Jentic publishes the only available OpenAPI specification for ContainerInstanceManagementClient, keeping it validated and agent-ready. The Container Instance Management Client is the Azure Resource Manager API for Azure Container Instances (ACI) - running serverless container groups without managing a Kubernetes cluster. It exposes 16 endpoints covering container group create/update/delete, restart, stop, log retrieval, command execution, cached image lookup, and per-region capabilities and usage. Use it when an agent needs to run a one-shot container, exec into a running container, or pull logs.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the ContainerInstanceManagementClient to your agent

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

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcontainer-instance-management-client" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcontainer-instance-management-client" | 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 ContainerInstanceManagementClient API.

Create or update a container group with one or more containers, image, ports, and environment variables

Restart, stop, or delete a running container group from a single ARM call

Pull stdout and stderr logs from a named container in a group, with an optional tail line count

Execute a command inside a running container and stream the response over a websocket URL

List cached container images per region to predict cold-start latency

Query per-region capabilities and usage to size container group requests against quota

Use Cases

Patterns agents use ContainerInstanceManagementClient API for, with concrete tasks.

★ Run an agent task as a one-shot container

When an agent needs to run a sandboxed workload - a build, a data transform, or a model inference call - Azure Container Instances lets it spin up a container group, run the task, and tear it down without owning a cluster. The Container Instance Management Client creates the group with image, command, env, and resources, returns the public IP or DNS, and exposes Stop and Delete to clean up.

PUT /subscriptions/{subscriptionId}/resourceGroups/agent-rg/providers/Microsoft.ContainerInstance/containerGroups/agent-job-001 with a Linux container image and command, then DELETE the group when the task exits.

Pull logs from a running container

Operators debugging a failing container group need stdout and stderr without SSHing into a host. The logs endpoint takes a container group, container name, and optional tail line count and returns the most recent log buffer, which can be streamed to an incident response channel or attached to a ticket.

GET the logs subresource for container 'sidecar' in container group 'agent-worker' with tail=200 and post the response to the incident channel.

Exec a command for live debugging

ACI exposes a websocket-based exec channel so an operator can attach a shell to a running container without redeploying. The exec endpoint returns a websocket URI and a password; an agent can use this to run an env dump, inspect a process list, or rerun a failing migration step.

POST the exec subresource on container 'sidecar' in container group 'agent-worker' with command '/bin/sh -c "ps aux"' and capture the websocket response.

Quota-aware scheduling

Azure Container Instances quotas vary per region. Before submitting many container groups, an agent should query usages and capabilities per location to confirm the requested vCPU and memory profile is available - this prevents wasted PUTs that 429 or 409 against subscription quota.

GET /subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/eastus/usages and refuse to schedule new groups if vCPU usage > 80% of quota.

Agent-driven sandboxed execution via Jentic

An AI agent integrated through Jentic can use Azure Container Instances as a sandboxed runtime - pulling an image, running it with the agent's task as the entrypoint, fetching logs, and tearing the group down. Jentic's intent search exposes the right ACI operation for each phase and the AAD token never leaves the vault.

Spin up an ACI container group with image 'mcr.microsoft.com/python:3.11', run the supplied script as the entrypoint, stream logs back, then delete the group.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/containerGroups

List container groups in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerInstance/containerGroups

List container groups in a resource group

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/{location}/cachedImages

List cached images for a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/{location}/capabilities

List ACI capabilities for a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/{location}/usages

Get ACI usage and quota for a region

GET

/providers/Microsoft.ContainerInstance/operations

List Microsoft.ContainerInstance provider operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/containerGroups

List container groups in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerInstance/containerGroups

List container groups in a resource group

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/{location}/cachedImages

List cached images for a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/{location}/capabilities

List ACI capabilities for a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.ContainerInstance/locations/{location}/usages

Get ACI usage and quota for a region

GET

/providers/Microsoft.ContainerInstance/operations

List Microsoft.ContainerInstance provider operations

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

ContainerInstanceManagementClient

- Foundational (C)
54/100
65
Foundational Compliance
63
Developer Experience & Jentic Compatibility
37
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
65

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4
84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

37

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
87%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

12%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

48%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Azure Container Instances by hand means an Azure AD app registration for the OAuth implicit flow against management.azure.com, Contributor on the resource group, and building both the container group ARM body and the websocket exec channel yourself. Through Jentic you install once, import ContainerInstanceManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The subscription, resource group, and container group name are all URL path parameters (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerInstance/containerGroups/{containerGroupName}), so a rule can pin the agent to one resource group and its container groups. You choose the operations it may call, so destructive ones like deleting a container group or exec-ing a command inside one are not included unless you add them.

Credential isolation

Your Azure AD token for the user_impersonation scope is stored once, encrypted, by your own Jentic One instance and injected at execution time. It, along with any image-pull credentials, never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'run a one-shot container on Azure' or 'pull logs from a container group', and Jentic returns the matching ACI operation with its input schema, including the container group and exec subresource shapes, so the agent calls the right endpoint directly.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Container Registry Management Client

→

Manages the Azure Container Registry that ACI typically pulls images from

Choose Container Registry Management when the agent also needs to push, retag, or scan the image before running it on ACI

Alternative

Container Service Client

→

Provisions full Kubernetes clusters when one-shot ACI groups are not enough

Choose Container Service when the agent needs orchestration, autoscaling, or service meshes that ACI does not provide

Alternative

Compute Management Client

→

Standard VM-based compute when containers are the wrong abstraction

Choose Compute Management when the workload requires a full VM, a custom kernel, or features ACI does not support

FAQs

Specific to using ContainerInstanceManagementClient API through Jentic.

Why is there no official OpenAPI spec for ContainerInstanceManagementClient?

Microsoft Azure does not publish a single consolidated OpenAPI specification for the Container Instance Management Client. Jentic generates and maintains this spec so that AI agents and developers can call ContainerInstanceManagementClient 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 ContainerInstanceManagementClient 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 needs Contributor on the resource group. Through Jentic the AAD token sits in the encrypted vault.

Can I exec into a running container with this API?

Yes. POST the exec subresource on a named container in a container group with a command and terminal size. The response contains a websocket URI and a one-time password - open the websocket to attach to the container session.

What are the rate limits for the ContainerInstanceManagementClient?

ARM applies subscription-level read and write throttling (typically 12,000 reads and 1,200 writes per hour per subscription). Container instances also have per-region vCPU and memory quotas - call the usages endpoint to check current consumption against quota.

How do I run a one-shot container through Jentic?

Search Jentic for 'create azure container group', load the schema for PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerInstance/containerGroups/{containerGroupName}, and execute it with image, command, and resources in the body. Run pip install jentic to get the SDK.

Is the ContainerInstanceManagementClient free?

Calling the management API itself is free, but each container group is billed per second on vCPU and memory allocated for the lifetime of the group. Standard ACI pricing applies; the spec does not change billing.

Can I limit what my agent is allowed to do with the Azure Container Instances API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The subscription, resource group, and container group name are URL path parameters, so a rule can pin the agent to a single resource group and its container groups. You also choose which operations it may call, so destructive ones such as deleting a container group or exec-ing a command inside a running container are excluded unless you add them.

GET STARTED

Start building with ContainerInstanceManagementClient API

Explore with Jentic One
View OpenAPI Document