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 / Domains API Client
Domains API Client logo

Microsoft Azure Domains API Client

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

Know of an official OpenAPI document? Contribute it →

For Agents

Check domain availability, get name recommendations, and register, renew, or manage Azure-purchased domain names along with their ownership identifiers.

Use for: I need to check whether example.com is available to register on Azure, Get domain name recommendations for a coffee shop in Berlin, Register the domain mybrand.app through Azure App Service Domains, Renew the domain example.com before it expires

Not supported: Does not manage DNS records, SSL certificates, or App Service custom domain bindings - use for Azure App Service Domain registration, renewal, and ownership only.

Jentic publishes the only available OpenAPI specification for Domains API Client, keeping it validated and agent-ready. The Azure Domains API Client manages domain names purchased through Azure App Service Domains. It exposes 15 endpoints covering domain availability checks, recommendation lookups, domain CRUD, renewal, ownership identifiers, and a single sign-on request endpoint that hands off to the App Service domain control center.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Domains API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Domains API Client, 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%2Fazure-domains-api-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%2Fazure-domains-api-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 Domains API Client API.

Check whether a candidate domain name is available for registration

Generate domain name recommendations from seed keywords

Register a new domain through Azure App Service Domains

Renew an existing Azure-purchased domain

Manage domain ownership identifiers used to prove control

List every Azure-purchased domain in a subscription or resource group

Generate a single sign-on URL for the domain control center

Use Cases

Patterns agents use Domains API Client API for, with concrete tasks.

★ Programmatic Domain Acquisition

When a product team needs a domain for a new launch, the Domains API lets an automation agent check availability with Domains_CheckAvailability, gather alternatives via Domains_ListRecommendations, and complete the purchase through Domains_CreateOrUpdate without anyone opening the portal. Domain ownership lives in the same subscription as the App Service that will consume it, so DNS can be wired up in the same automation run.

Call Domains_CheckAvailability for newproduct.com; if available, call Domains_CreateOrUpdate to register it in resource group brand-rg with consent provided.

Bulk Domain Renewal

Companies with portfolios of dozens or hundreds of brand domains lose money to lapsed registrations. The Domains API exposes Domains_List to enumerate every domain the subscription owns and Domains_Renew to extend each one in a single batch. Combined with the expiry date returned by Domains_Get, an agent can flag any domain expiring in the next 30 days and renew automatically.

List every domain in subscription X and renew any whose expirationTime is within 30 days of today.

Domain Ownership Verification at Scale

Some integrations require proof that a domain is owned by a specific Azure resource - for example, configuring a custom domain on App Service. The Domains API exposes ownership identifier endpoints so an agent can create or update a verification token, store the linked Azure resource ID, and confirm ownership without the portal flow.

Create a domain ownership identifier named appservice-verify on example.com pointing at the resource ID of the App Service that needs to claim the domain.

AI Agent Domain Concierge via Jentic

An assistant integrated through Jentic can resolve a request like buy a sensible .com for our new fintech product end-to-end. It searches Jentic for check azure domain availability, loops through Domains_CheckAvailability for shortlisted names, calls Domains_ListRecommendations for alternatives, and completes the purchase via Domains_CreateOrUpdate. Credentials never leave your Jentic One instance.

Through Jentic, search for register a domain on azure, load Domains_CreateOrUpdate, and register newbrand.app in resource group launch-rg.

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for domains api client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/checkDomainAvailability

Check if a domain is available for registration

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/listDomainRecommendations

Get domain name recommendations

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}

Register or update a domain

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}/renew

Renew a domain

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/domains

List all domains in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/generateSsoRequest

Generate a single sign-on request to the domain control center

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/checkDomainAvailability

Check if a domain is available for registration

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/listDomainRecommendations

Get domain name recommendations

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}

Register or update a domain

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}/renew

Renew a domain

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/domains

List all domains in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/generateSsoRequest

Generate a single sign-on request to the domain control center

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.

D

Domains API Client

- Foundational (C)
55/100
71
Foundational Compliance
62
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
71

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
86%

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.

62

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.

48%

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
86%

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.

62%

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 the Microsoft.DomainRegistration domains API by hand means acquiring Azure AD OAuth 2.0 bearer tokens, building the ARM URLs under management.azure.com, and polling the asynchronous registrar handshake on registration and renewal yourself. Through Jentic you install once, import the Domains API Client from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The domain id sits in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}), so a rule can pin your agent to one subscription and resource group and the domains inside it. You choose the operations it may call, so ones like registering or deleting a domain are not included unless you add them.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected as a short-lived bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'register a domain on azure' or 'check domain availability', and Jentic returns the matching Domains operation with its domain-name, contact, and consent input schema so the agent calls the right endpoint without browsing ARM docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DNS Management Client

→

Hosts DNS records on the domains registered via the Domains API

Use after registering a domain to publish A, CNAME, MX, and TXT records

Complementary

DomainRegistrationProvider API Client

→

Lists the operations exposed by the Microsoft.DomainRegistration provider

Use when the agent needs to enumerate provider operations rather than register a domain

Alternative

Domain Services Resource Provider

→

Manages Azure AD Domain Services rather than domain name registration

Choose when the request concerns managed Active Directory rather than DNS-level domain ownership

FAQs

Specific to using Domains API Client API through Jentic.

Why is there no official OpenAPI spec for Domains API Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Domains API Client 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 Domains API Client use?

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs at least Contributor on the target resource group. Through Jentic the underlying client secret stays in your Jentic One instance and the agent only receives a scoped bearer token.

Can I check domain availability before registering?

Yes. POST /subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/checkDomainAvailability accepts a name in the body and returns availability plus the registration price. Pair this with /listDomainRecommendations to get alternatives when the first choice is taken.

What are the rate limits for the Domains API Client?

Standard Azure Resource Manager subscription-scoped throttling applies (broadly 12,000 reads per hour and 1,200 writes per hour). Domain registration also depends on the upstream registrar and is not instantaneous - Domains_CreateOrUpdate may take several minutes before provisioningState reads Succeeded.

How do I register a domain through Jentic?

Run pip install jentic, search for register a domain on azure, load Domains_CreateOrUpdate, supply domainName, contactAdmin, contactBilling, contactRegistrant, contactTech, consent, and privacy, then execute. Poll Domains_Get until provisioningState is Succeeded.

Does this API manage DNS records on the registered domain?

No. The Domains API only handles registration and lifecycle (purchase, renew, ownership). DNS records on the registered domain are managed through Azure DNS via the separate DnsManagementClient API.

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

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use. Since the subscription and resource group sit in the request path, you can pin the agent to a single subscription and resource group and the domains inside it. You also choose the exact operations it may call, so higher-impact ones like Domains_CreateOrUpdate or deleting a domain are excluded unless you add them, while you allow read-only calls such as Domains_CheckAvailability or Domains_List.

GET STARTED

Start building with Domains API Client API

Explore with Jentic One
View OpenAPI Document