AttestationClient

Name: AttestationClient API
Brand: AttestationClient
Availability: InStock

★ Only Publicly Available SpecSecurityComplianceoauth26 EndpointsREST

For Agents

Verify trusted execution environment attestations and manage attestation policies for Intel SGX and TPM-backed workloads on Azure from an AI agent.

Quickstart

Get started with AttestationClient in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get Azure Attestation signing certificates"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AttestationClient API.

Retrieve the OpenID Connect discovery metadata for the attestation tenant

Fetch the signing certificate set used to verify attestation tokens

Read the current attestation policy for an attestation type

Update the attestation policy that governs how attestation requests are evaluated

GET STARTED

Start building with AttestationClient API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for AttestationClient, keeping it validated and agent-ready.

AttestationClient is the per-tenant Azure Attestation Service API used to verify the integrity of trusted execution environments such as Intel SGX enclaves and TPM-backed workloads. It exposes the OpenID Connect discovery document, the signing certificate set used to verify attestation tokens, and the policy management endpoints that govern how attestation requests are evaluated. Use this client to validate confidential compute workloads or to maintain attestation policy.

Use Cases

Patterns agents use AttestationClient API for, with concrete tasks.

★ Confidential Compute Token Verification

Applications that consume attestation tokens issued by Azure Attestation must verify the token signature against the tenant's certificate set before trusting the enclave identity it claims. The /certs endpoint returns the JWKS, which a JWT library uses to verify the token. The /.well-known/openid-configuration endpoint provides the issuer and JWKS URI for standards-based JWT verification.

GET /.well-known/openid-configuration to discover the JWKS URI, GET /certs to fetch the signing keys, then verify the attestation JWT signature using the matching key by kid.

Attestation Policy Governance

Security teams operating confidential workloads need to control which enclave images and configurations are accepted by the attestation tenant. The policy endpoints expose the current policy text and allow signed updates so audit trails are preserved. Updates are applied per attestation type (SGX, OpenEnclave, TPM, VBS).

Read the current policy via /operations/policy/current, prepare a new policy document signed with the policy management key, and POST to /operations/policy/updatepolicy.

Enclave Identity Validation Pipeline

A relying party that issues secrets to confidential VMs only after validating the enclave's measurements relies on the attestation tenant to certify those measurements. Calling the certs and OIDC endpoints during startup (and refreshing on a cadence) keeps the verification path stateless and reproducible across instances.

On service startup, fetch and cache /.well-known/openid-configuration and /certs; on each attestation request, verify the JWT against the cached key by kid before releasing the secret.

Agent-Driven Attestation Audit via Jentic

A security AI agent auditing a tenant's confidential compute posture can use Jentic to retrieve the current attestation policy without holding the tenant's policy management credentials. Jentic returns the policy schema and current text for review, supporting compliance documentation generation against published policy baselines.

Search Jentic for 'get current Azure Attestation policy', execute against the tenant for each attestation type, and compare the returned policy against the organisation's documented baseline.

Key Endpoints

6 endpoints — attestationclient is the per-tenant azure attestation service api used to verify the integrity of trusted execution environments such as intel sgx enclaves and tpm-backed workloads.

METHOD

PATH

DESCRIPTION

GET

/.well-known/openid-configuration

Retrieve the OpenID Connect discovery document for the attestation tenant

GET

/certs

Fetch the signing certificate set (JWKS) used to verify attestation tokens

GET

/operations/policy/current

Read the current attestation policy

POST

/operations/policy/updatepolicy

Update the attestation policy for an attestation type

GET

/.well-known/openid-configuration

Retrieve the OpenID Connect discovery document for the attestation tenant

GET

/certs

Fetch the signing certificate set (JWKS) used to verify attestation tokens

GET

/operations/policy/current

Read the current attestation policy

POST

/operations/policy/updatepolicy

Update the attestation policy for an attestation type

Why though Jentic?

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

Credential isolation

AAD bearer tokens authorised for attestation policy management are stored in the Jentic vault. Agents receive a scoped session at call time and never hold the policy signing key or AAD client secret.

Intent-based discovery

Agents search by intent ('verify an Azure attestation token') and Jentic returns the matching operation with its parameter schema, so the agent does not have to discover the JWKS or OIDC discovery URL separately.

Time to first call

Direct integration: half a day to wire OIDC discovery, JWKS fetch, and JWT verification, longer if also handling policy updates. Through Jentic: under 30 minutes for verification flows; policy updates remain signed-payload operations regardless.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Key Vault Client

Release secrets to enclaves only after attestation succeeds

Pair Key Vault with Attestation when an agent needs to gate secret release on a verified TEE identity.

Complementary

Authorization Management Client

Manage RBAC role assignments for the attestation tenant

Use Authorization Management to grant policy management roles on the attestation provider resource.

Alternative

Policy Client

Azure Policy for general resource governance, not TEE attestation

Choose Policy Client for resource-level governance; choose Attestation for verifying enclave or TPM identity.

FAQs

Specific to using AttestationClient API through Jentic.

What authentication does the AttestationClient use?

Azure Active Directory OAuth 2.0 bearer tokens for the policy management endpoints. The /.well-known/openid-configuration and /certs endpoints are anonymous, since they are needed to verify tokens before any authenticated call. Jentic vaults the AAD token used for policy operations and issues a scoped session at call time.

Can I update the SGX attestation policy through this API?

Yes. POST a signed policy document to /operations/policy/updatepolicy with the attestation type set to SGX-IntelSDK or OpenEnclave. The policy must be signed with a key that the tenant has authorised for policy management; the service rejects unsigned or improperly signed updates.

What are the rate limits for the AttestationClient?

The discovery and JWKS endpoints are designed for high-frequency cached use and have generous limits. Policy management endpoints are infrequent administrative calls and are not a typical bottleneck. Specific quotas are not surfaced in the 2018-09-01-preview spec; consult Azure Attestation service quotas for current values.

How do I verify an attestation token with this API through Jentic?

Search Jentic for 'get Azure Attestation signing certificates'. Jentic returns the schema for GET /certs. Execute it once and cache the JWKS, then use a JWT library to verify each attestation token's signature against the matching key by kid.

Is Azure Attestation free?

Azure Attestation has a free tier covering a base volume of attestation calls per month, with paid tiers for higher throughput. The /.well-known/openid-configuration and /certs endpoints used for token verification are not metered. See Azure Attestation pricing for current call quotas.

Where is the JWKS endpoint for verifying attestation tokens?

The JWKS is served from /certs on the per-tenant attestation URL. The discovery document at /.well-known/openid-configuration also references the JWKS URI under the jwks_uri field, which is the recommended way to locate the keys per OpenID Connect convention.