ClouDNS DNS API
49
AI ReadinessFoundational (D+)49/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingapiKey13 EndpointsREST
For Agents
Manage authoritative DNS zones and records on ClouDNS - register zones, add and modify A/AAAA/MX/CNAME/TXT records, and check propagation status across nameservers.
Use for: I need to add an A record pointing my apex domain at a new server IP, Register a new DNS zone for a customer domain, Check whether my latest DNS change has propagated across all ClouDNS nameservers, List all DNS zones currently hosted in this ClouDNS account
Not supported: Does not handle domain registration, TLS certificate issuance, or web hosting - use for authoritative DNS zone and record management only.
The ClouDNS DNS API provides programmatic management of authoritative DNS zones and records hosted on the ClouDNS global Anycast network. It exposes operations to register and delete zones, list zone records, add, modify, and delete A, AAAA, MX, CNAME, TXT and other record types, and check zone propagation status across the ClouDNS nameservers. Authentication uses an auth-id and auth-password pair passed as query parameters, and responses are available in both JSON and XML formats.
Install Jentic One Beta
Connect the ClouDNS DNS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClouDNS DNS 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcloudns.net%2Fcloudns" | sh2
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%2Fcloudns.net%2Fcloudns" | 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 ClouDNS DNS API.
Register and delete DNS zones on the ClouDNS Anycast network
Add, modify, and delete individual DNS records inside a zone
List zones with pagination and retrieve aggregate zone statistics
Activate or deactivate DNS zones without deleting their records
Check whether a zone has fully propagated across all ClouDNS nameservers
Verify auth-id and auth-password credentials before running other operations
Use Cases
Patterns agents use ClouDNS DNS API for, with concrete tasks.
★ Automated DNS Provisioning for New Customer Domains
Hosting providers and SaaS platforms that issue subdomains or full domains to customers can use the ClouDNS API to register a new zone and seed it with the required A, CNAME, and MX records in a single workflow. The /dns/register.json and /dns/add-record.json endpoints handle zone creation and record population, and is-updated.json confirms global propagation before the customer-facing service is announced as ready. Typical end-to-end provisioning takes under a minute including propagation checks.
Register the zone example-customer.com, add an A record for the apex pointing to 203.0.113.10, add a CNAME for www pointing to the apex, and poll is-updated.json until propagation completes
Bulk DNS Record Updates During Migrations
When migrating between hosting providers, mail providers, or CDN edges, infrastructure teams need to update many records consistently. The ClouDNS API exposes mod-record.json for in-place edits and delete-record.json plus add-record.json for full replacements, while list-zones.json and records.json provide the inventory needed to plan the change. Updates apply to the Anycast network within seconds and propagation can be tracked via update-status.json.
List all records in zone acme.com, identify every A record pointing to the legacy IP 198.51.100.5, and modify each one to point to 203.0.113.42
Scheduled Zone Propagation Monitoring
Operations teams running production DNS changes need confirmation that updates have replicated across every authoritative nameserver before declaring a change complete. The update-status.json and is-updated.json endpoints return per-nameserver propagation state and a single is-fully-updated boolean. Polling these endpoints from a CI job or monitoring system replaces manual dig checks against each ClouDNS nameserver.
After modifying a TXT record on zone acme.com, poll is-updated.json every 10 seconds for up to 2 minutes and report when the zone is fully synchronised
Agent-Driven DNS Operations via Jentic
AI agents that manage cloud infrastructure can call the ClouDNS API through Jentic to add, change, or remove DNS records as part of larger workflows such as TLS certificate validation, mail server setup, or domain handover. Jentic resolves the intent, supplies the auth-id and auth-password from its credential vault, and returns structured results so the agent can verify the change without parsing raw responses. Setup is search-load-execute rather than reading the ClouDNS HTTP API wiki.
Through Jentic, search for 'add a DNS record', load the ClouDNS add-record.json operation, and execute it to create a TXT record for ACME DNS-01 challenge validation
Key Endpoints
13 endpoints — the cloudns dns api provides programmatic management of authoritative dns zones and records hosted on the cloudns global anycast network.
METHOD
PATH
DESCRIPTION
POST
/dns/register.json
Register a new DNS zone
GET
/dns/list-zones.json
List DNS zones
GET
/dns/records.json
List DNS records for a zone
POST
/dns/add-record.json
Add a DNS record to a zone
POST
/dns/mod-record.json
Modify an existing DNS record
POST
/dns/delete-record.json
Delete a DNS record
GET
/dns/is-updated.json
Check whether a zone is fully propagated
POST
/dns/register.json
Register a new DNS zone
GET
/dns/list-zones.json
List DNS zones
GET
/dns/records.json
List DNS records for a zone
POST
/dns/add-record.json
Add a DNS record to a zone
POST
/dns/mod-record.json
Modify an existing DNS record
POST
/dns/delete-record.json
Delete a DNS record
GET
/dns/is-updated.json
Check whether a zone is fully propagated
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.
C
ClouDNS DNS API
- Foundational (D+)49/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
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.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
57%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
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.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ClouDNS DNS API by hand means passing your auth-id and auth-password as query parameters on every request and posting the zone and record calls to api.cloudns.net yourself. Through Jentic you install once, import the ClouDNS DNS API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
ClouDNS names the zone and record in the request parameters rather than pinning one id in the URL path, so scope the agent by the operations it needs, such as listing zones, reading records, or adding a record. You choose that set, so operations like modifying or deleting a record are only in reach if you include them.
Credential isolation
Your ClouDNS auth-id and auth-password are stored once, encrypted, by your own Jentic One instance and injected as query parameters at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a DNS record' or 'check DNS propagation', and Jentic returns the matching ClouDNS operation with its input schema so the agent calls the right endpoint without reading the ClouDNS HTTP API wiki.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ClouDNS DNS API through Jentic.
What authentication does the ClouDNS DNS API use?
The ClouDNS DNS API uses an apiKey scheme: every request must include auth-id and auth-password as query parameters. Through Jentic these credentials are stored in your Jentic One instance and injected at execution time, so they never appear in the agent context or in logs.
Can I add and modify individual DNS records with the ClouDNS DNS API?
Yes. /dns/add-record.json creates a record, /dns/mod-record.json updates an existing one in place, and /dns/delete-record.json removes it. The endpoints accept the standard ClouDNS record types (A, AAAA, MX, CNAME, TXT and others) plus the zone name and record body.
How can I tell when a DNS change has propagated across all ClouDNS nameservers?
Call /dns/is-updated.json with the zone name to get a single boolean indicating full propagation, or /dns/update-status.json for per-nameserver state. Polling is-updated.json every few seconds is the standard pattern for confirming a change before downstream services start using it.
What are the rate limits for the ClouDNS DNS API?
The OpenAPI specification does not declare explicit rate limit headers or a 429 response. ClouDNS publishes account-tier limits in its wiki and applies throttling at the account level, so very high volume callers should batch updates and back off if requests start to fail. For agent workloads through Jentic, retries are handled by the SDK.
How do I add a DNS record with the ClouDNS DNS API through Jentic?
Install the SDK with pip install jentic, search for 'add a DNS record', load the cloudns.net add-record.json operation, and execute it with the zone name, record type, host, and record value. Jentic supplies the auth-id and auth-password automatically and returns the structured response from /dns/add-record.json.
Does the ClouDNS DNS API support both JSON and XML responses?
Yes. The same endpoints are available with .json or .xml suffixes. The Jentic-published spec covers the .json variants since structured JSON is what agents and SDKs consume directly.
Can I limit what my agent is allowed to do with the ClouDNS DNS API?
Yes. Because you run Jentic One yourself, you decide which ClouDNS operations your agent may call, and your own rules govern access. ClouDNS names the zone and record in the request parameters rather than pinning one id in the URL path, so you scope the agent by the operations it needs, such as listing zones with /dns/list-zones.json, reading records with /dns/records.json, or adding a record with /dns/add-record.json. Higher-impact operations like /dns/mod-record.json and /dns/delete-record.json are only in reach if you include them in that set.
GET STARTED