Google Cloud Domains API

Name: Cloud Domains API
Brand: Cloud Domains API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth226 EndpointsREST

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.

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 | sh

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 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 Cloud Domains API.

Search availability and price for a candidate domain name and retrieve register parameters before purchase

Initiate a domain transfer in from another registrar using an authorization code and confirm transfer parameters

GET STARTED

Start building with Cloud Domains API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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

Credential isolation

Your Google OAuth credential for Cloud Domains is stored 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 'search for an available domain' or 'retrieve register parameters', and Jentic returns the matching Cloud Domains operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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.

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

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Cloud Domains operations and which OAuth credential the agent may use. Since the API carries the resource name in the URL path, such as /v1/{+location}/registrations and /v1/{+name}, a rule can pin the agent to a single location or registration and allow only safe operations like searchDomains and retrieveRegisterParameters. Destructive calls such as deleting a registration are excluded unless you explicitly add them.

Google Cloud Domains API

Connect the Cloud Domains API to your agent

Capabilities

Start building with Cloud Domains API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs