Google Cloud Domains API
Browse all Google APIs✓ Official Vendor SpecCloud InfrastructureNetworkingoauth226 EndpointsREST
For Agents
Search, register, transfer, configure, and renew domain names within a Google Cloud project, with full DNS, contact, and privacy controls.
Use for: Search whether 'mycompany.dev' is available to register, Get the registration price and supported privacy options for a domain, I need to register a new domain with Cloud DNS configured automatically, Transfer an existing domain from GoDaddy into Google Cloud
Not supported: Does not handle DNS record management, SSL certificate issuance, or domain marketplace listings — use for domain registration and registrar-level configuration only.
Google Cloud Domains lets you register, transfer, and manage domain name registrations directly from your Google Cloud project. The API exposes the full registration lifecycle: search for available domains, retrieve register and transfer parameters, configure DNS settings (Cloud DNS or custom name servers), manage WHOIS contact privacy, configure auto-renew, and export or transfer registrations out. Operations are scoped under projects and locations and return long-running operations for asynchronous registration steps.
Install Jentic One Beta
Connect the Cloud Domains API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Domains API, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 instanceJentic 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 Cloud Domains API.
Search availability and price for a candidate domain name and retrieve register parameters before purchase
Register a new domain with contact details, DNS settings, and privacy options as a long-running operation
Initiate a domain transfer in from another registrar using an authorization code and confirm transfer parameters
Configure or update DNS settings to use Cloud DNS, Google Domains DNS, or custom name servers
Update registrant, admin, and technical contacts and toggle WHOIS contact privacy
Export a registration out of Cloud Domains or initiate transfer-out with an authorization code
Use Cases
Patterns agents use Cloud Domains API for, with concrete tasks.
★ Programmatic Domain Registration for Multi-Tenant Apps
SaaS platforms that issue customer-branded subdomains or vanity domains use Cloud Domains to register names on behalf of tenants from within the same Google Cloud project that hosts their app. The API handles availability search, price disclosure, registration as a long-running operation, and automatic Cloud DNS configuration. Registration plus DNS readiness typically completes within minutes for supported TLDs.
Call retrieveRegisterParameters for 'tenant-foo.com', then POST /v1/{+parent}/registrations:register with yearly_price and contact details, and poll the returned operation until DONE.
Domain Portfolio Migration to Google Cloud
Teams consolidating registrations from multiple registrars use the transfer endpoints to move domains into Cloud Domains, where billing rolls into the same Google Cloud invoice. The API verifies transfer eligibility, accepts the authorization code from the losing registrar, and configures DNS during the transfer window. Each transfer takes 5-7 days per registry rules; the API surfaces status throughout.
For each domain in a CSV, call retrieveTransferParameters, then registrations:transfer with the auth code, and report the operation name and current state.
Contact and Privacy Compliance Updates
When organisations restructure or update legal contacts, they patch registration contacts across hundreds of domains in a single workflow. The API supports updating registrant, admin, technical, and billing contacts and toggling WHOIS privacy proxy settings. Bulk contact updates that would take hours per domain in a registrar UI complete in a single scripted run.
PATCH /v1/{+name} with updated registrant contact email and contactPrivacy=PRIVATE_CONTACT_DATA for every registration under the project.
Agent-Driven Domain Operations via Jentic
An AI agent helping a developer launch a new product can search for available domains, present prices, register the chosen name, and wire up Cloud DNS records, all through Jentic. The agent does not need to learn the long-running operation pattern or the contacts schema; Jentic returns the right operation and its input shape on each step.
Search Jentic for 'register a new domain', load the registrations:register schema, execute it with the chosen TLD, and wait on the operation.
Key Endpoints
26 endpoints — google cloud domains lets you register, transfer, and manage domain name registrations directly from your google cloud project.
METHOD
PATH
DESCRIPTION
GET
/v1/{+location}/registrations:searchDomains
Search availability for candidate domains
GET
/v1/{+location}/registrations:retrieveRegisterParameters
Get price and options for registering a specific domain
GET
/v1/{+location}/registrations:retrieveTransferParameters
Get transfer-in eligibility and pricing
PATCH
/v1/{+name}
Update registration contacts, DNS, or privacy settings
DELETE
/v1/{+name}
Delete a registration before it has been completed
GET
/v1/{+name}/locations
List supported registration locations
GET
/v1/{+location}/registrations:searchDomains
Search availability for candidate domains
GET
/v1/{+location}/registrations:retrieveRegisterParameters
Get price and options for registering a specific domain
GET
/v1/{+location}/registrations:retrieveTransferParameters
Get transfer-in eligibility and pricing
PATCH
/v1/{+name}
Update registration contacts, DNS, or privacy settings
DELETE
/v1/{+name}
Delete a registration before it has been completed
GET
/v1/{+name}/locations
List supported registration locations
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Cloud service account keys are encrypted in the Jentic vault. Agents receive scoped OAuth access tokens with the cloud-platform scope; raw keys never enter the agent context, which matters because the domains.admin role can incur real billing.
Intent-based discovery
Agents search by intent (e.g. 'register a domain') and Jentic returns the right operation across the search → register → configure flow with input schemas attached, including the long-running operation envelope.
Time to first call
Direct Cloud Domains integration: 2-4 days for OAuth, registration LRO polling, and contact/DNS schema. Through Jentic: under 1 hour for a one-shot register-and-configure flow.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Domains API through Jentic.
What authentication does the Cloud Domains API use?
Cloud Domains uses Google OAuth 2.0 with the cloud-platform scope. Tokens are typically issued from a service account and passed as a Bearer token. Through Jentic the service account JSON is stored in the credential vault and the agent only ever sees a short-lived access token.
Can I check domain availability without registering?
Yes. Call GET /v1/{+location}/registrations:searchDomains to list candidate matches and availability, then retrieveRegisterParameters for a specific domain to see the yearly_price, supported privacy modes, and notices that must be acknowledged on registration.
What are the rate limits for the Cloud Domains API?
Cloud Domains shares the standard Google Cloud per-project quota (default 60 read requests per minute and 60 write requests per minute, with registration operations also subject to per-TLD registry limits). Quotas can be raised from the Cloud Console.
How do I transfer a domain in through Jentic?
Search Jentic for 'transfer a domain in', load the schema for retrieveTransferParameters and registrations:transfer, then execute both with the authorization code from the losing registrar. Jentic returns the long-running operation name; poll until DONE.
Is the Cloud Domains API free?
The API is free to call but domain registrations and renewals are billed at registry-set per-TLD prices, exposed through retrieveRegisterParameters. There is no markup beyond what Cloud Domains discloses before registration.
How do I update WHOIS contact privacy on a registration?
PATCH /v1/{+name} with contactSettings.privacy set to PRIVATE_CONTACT_DATA, REDACTED_CONTACT_DATA, or PUBLIC_CONTACT_DATA. The change is scoped by registry rules — some TLDs do not support privacy redaction and the API surfaces this via the supportedPrivacy list on retrieveRegisterParameters.
GET STARTED