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 / InstanceMetadataClient
InstanceMetadataClient logo

Microsoft Azure InstanceMetadataClient

Browse all Azure APIs
32
AI ReadinessNon-Ready (F)32/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputebasic4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read Azure VM instance metadata and obtain managed identity OAuth tokens from inside the VM via the Azure Instance Metadata Service.

Use for: Get the metadata of the Azure VM I am running on, Retrieve a managed identity access token for an Azure resource, Find the client id of the managed identity assigned to this VM, Get an attested document to prove this VM's identity

Not supported: Does not handle Azure Resource Manager calls, secret storage, or cross-VM discovery - use for in-VM metadata reads and managed identity token issuance only.

Jentic publishes the only available OpenAPI specification for InstanceMetadataClient, keeping it validated and agent-ready. The Azure Instance Metadata Service (IMDS) is a non-routable endpoint reachable from inside an Azure VM at 169.254.169.254 that returns information about the running instance and issues managed identity tokens. It exposes 4 endpoints to fetch instance metadata, an attested document, managed identity info, and an OAuth 2.0 access token for the VM's assigned identity.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the InstanceMetadataClient to your agent

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

Retrieve compute, network, and tag metadata for the running Azure VM

Fetch an attested document signed by Azure to prove VM identity to relying parties

Look up the managed identity client and tenant ids assigned to the VM

Obtain an OAuth 2.0 access token for a managed identity scoped to a target resource

Operate without storing credentials by relying on the VM's IMDS endpoint

Use Cases

Patterns agents use InstanceMetadataClient API for, with concrete tasks.

★ Credential-Free Azure SDK Auth

Workloads running on Azure VMs avoid embedded secrets by calling /identity/oauth2/token to obtain a managed identity bearer token, then passing it to other Azure APIs. The IMDS endpoint is reachable only from the VM itself, so no inbound network rules are needed. Adopting this pattern typically takes a couple of hours per workload and removes a class of secret-rotation problems.

Call /identity/oauth2/token with resource=https://management.azure.com/ from the VM and return the bearer token.

VM Self-Description for Tagging and Routing

Bootstrap scripts read /instance to discover the VM's region, vmSize, resourceGroupName, and tags, then configure their behaviour accordingly - for example, registering with a region-specific service discovery system. Because IMDS is local, the call is fast and does not depend on AAD. This is the standard way to make Azure VMs self-aware without baking config into images.

GET /instance and return the compute.location, compute.vmSize, and the value of the tag named 'environment'.

Attested VM Identity for Zero-Trust

Relying parties verify VM identity by fetching the /attested/document, which returns a JWT signed by Azure that includes the subscriptionId, vmId, and other compute fields. The receiving service validates the signature and checks the claims before granting access. This is the foundation for zero-trust admission to internal services that should only accept calls from sanctioned Azure VMs.

GET /attested/document?api-version=2019-08-15 and return the signed JWT.

Agent-Driven IMDS Calls via Jentic

An AI agent running on (or proxying to) an Azure VM can fetch metadata and tokens through Jentic without code that hard-codes the IMDS host. The agent searches Jentic for 'get an azure managed identity token', loads the operation schema, and executes against the local IMDS. Jentic mediates the request shape and surfaces the response into the agent's context.

Use the Jentic MCP tool azure_imds_get_token to fetch a managed identity token for resource https://vault.azure.net and return the access_token.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/instance

Return compute, network, and tag metadata for the running VM

GET

/identity/info

Return managed identity client and tenant ids for the VM

GET

/identity/oauth2/token

Issue a managed identity OAuth 2.0 access token for a target resource

GET

/attested/document

Return a signed attested document for the VM

GET

/instance

Return compute, network, and tag metadata for the running VM

GET

/identity/info

Return managed identity client and tenant ids for the VM

GET

/identity/oauth2/token

Issue a managed identity OAuth 2.0 access token for a target resource

GET

/attested/document

Return a signed attested document for the VM

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.

I

InstanceMetadataClient

- Non-Ready (F)
32/100
70
Foundational Compliance
63
Developer Experience & Jentic Compatibility
22
AI-Readiness & Agent Experience
94
Agent Usability
10
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
70

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
82%

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).

100%

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.

22

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
89%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

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

0%

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.

10

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
10%

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 the Azure Instance Metadata Service by hand means remembering the link-local 169.254.169.254 address, attaching the required Metadata header to every request, and handling the managed-identity token flow yourself. Through Jentic you install once, import InstanceMetadataClient from the API Directory, and your agent calls it over a Jentic-mediated path that supplies the Metadata header, since IMDS authorizes by the request originating inside the VM rather than by a stored credential.

Permission scoping

IMDS is a read surface reached from inside the VM, so limit the agent to the operations it needs, such as reading /instance metadata or requesting a managed-identity token from /identity/oauth2/token. You choose the operations it may call, so the attested document read is not included unless you add it.

Credential isolation

IMDS itself needs no stored credential because it trusts the in-VM origin, and any managed-identity token it issues is held once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get an Azure managed identity token' or 'read this VM's instance metadata', and Jentic returns the matching IMDS operation with its input schema so the agent calls the right endpoint without remembering the link-local URL or required headers.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Key Vault

→

A managed identity token from IMDS is the standard credential for calling Key Vault from a VM.

Use Key Vault when the workload needs secrets after authenticating with the IMDS-issued token.

Complementary

Azure IoT Hub

→

VMs that gateway to IoT Hub can authenticate with managed identity tokens issued by IMDS.

Use IoT Hub when the VM acts as an edge gateway and needs an MI token to talk to the hub.

Alternative

Azure HybridData Management

→

HybridData targets cross-environment data movement rather than VM self-description.

Choose HybridData when the goal is moving data between sites, not introspecting an Azure VM.

FAQs

Specific to using InstanceMetadataClient API through Jentic.

Why is there no official OpenAPI spec for InstanceMetadataClient?

Microsoft documents IMDS as a REST surface but does not publish a maintained OpenAPI 3 specification for it. Jentic generates and maintains this spec so that AI agents and developers can call InstanceMetadataClient 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 InstanceMetadataClient use?

IMDS itself is reachable only from the VM at 169.254.169.254 and requires the request header Metadata: true on every call. Through Jentic the request shape including this header is handled automatically. The /identity/oauth2/token endpoint then issues a bearer token for downstream Azure services.

Can I get a managed identity token from this API?

Yes. GET /identity/oauth2/token with the api-version query parameter and a resource parameter (e.g. resource=https://management.azure.com/) returns an access_token, expires_in, and the client_id of the identity. Use the token as a Bearer credential for the target Azure service.

What are the rate limits for IMDS?

IMDS is a per-VM local service and does not publish a per-second rate cap, but Microsoft recommends caching tokens until close to expiry rather than calling /identity/oauth2/token on every request. Treat repeated calls within a few seconds as wasteful, not as a hard limit.

How do I retrieve VM metadata through Jentic?

Run pip install jentic, then search Jentic with 'get azure vm instance metadata', load the /instance operation, and execute it. Jentic returns the compute, network, and tag JSON exactly as IMDS produces it, so downstream code reads .compute.location and friends directly.

Does IMDS work from outside the VM?

No. The endpoint 169.254.169.254 is link-local and only reachable from inside the Azure VM. For workloads outside the VM that need similar token issuance, use Azure AD app registrations or workload identity federation instead.

Can I limit what my agent is allowed to do with the Azure Instance Metadata Service?

Yes. Because you run Jentic One yourself, your own rules decide which IMDS operations the agent may call, so you can allow only reading instance metadata from /instance while blocking the managed-identity token request at /identity/oauth2/token, or the reverse. The attested document read at /attested/document is not available to the agent unless you explicitly add it. IMDS trusts the in-VM origin rather than a stored credential, and any managed-identity token it issues is held by your own Jentic One instance and injected at execution time rather than exposed to the agent.

GET STARTED

Start building with InstanceMetadataClient API

Explore with Jentic One
View OpenAPI Document