The LaunchCDN API
for Developers and AI Agents

Run your network from code, or hand it to an AI agent. The LaunchCDN REST API returns clean JSON, so your own scripts, SEO tools and LLM-powered agents can deploy domains and look up everything about the sites in your account.

Included on every plan at no extra charge. Log in to your account, open the API section, and copy your User ID and Auth Key.

What the API Does

Five endpoints cover the whole lifecycle of a site, from deployment to day-to-day management. A small surface is easy to learn for developers, and just as easy for a model to use correctly.

How Requests Work

Every call is a POST to https://api.launchcdn.com/v1/<endpoint>/ with your user and auth values as form fields. Every response is JSON with a result of success or error, and errors come with a plain-English message that you (or your agent) can act on.

curl -A "AcmeSEOTool/1.0" \
  -d user=1001 -d auth=YOUR_AUTH_KEY \
  https://api.launchcdn.com/v1/getalldomains/

A trimmed response looks like this, with each site’s login details included alongside:

{
  "result": "success",
  "results": 2,
  "data": [
    {
      "domain": "example.com",
      "hosting_type": "wordpress",
      "serverip": "203.0.113.10",
      "nameservers": ["perry.ns.cloudflare.com", "dew.ns.cloudflare.com"]
    },
    {
      "domain": "example.org",
      "hosting_type": "static",
      "serverhostname": "server1.example-host.net",
      "serverip": "203.0.113.20",
      "nameservers": ["ns1.example-dns.net", "ns2.example-dns.net"]
    }
  ]
}

Deploying a Site

Send the domain, hosting type and CDN, plus a few optional settings:

curl -A "AcmeSEOTool/1.0" \
  -d user=1001 -d auth=YOUR_AUTH_KEY \
  -d domain=example.com -d type=wordpress \
  -d cdnprovider=cloudflare -d protocol=3 \
  -d wpuser=jason -d wppass=A_STRONG_PASSWORD \
  -d "wpsitename=Example Reviews" -d "wpsitedesc=Honest reviews and guides" \
  -d mxoption=forward -d mxuser=jason -d [email protected] \
  https://api.launchcdn.com/v1/deploy/

A few things to know before you deploy:

• Register the domain first. It needs to resolve before we can deploy it. If it isn’t pointed anywhere yet, set it to parking name servers at your registrar.
• Each deploy uses a domain slot. If your plan is full, the API tells you how many slots you’re using.
• Deployment runs in the background. The call returns as soon as the order is created, and the site is ready in under 5 minutes. Poll getsingledomain to pick up its name servers once it’s live.
• Some domains are refused. Domains that look like a trademark or brand name, or contain restricted words, return an error explaining why.

Using the API With LLMs and AI Agents

The API was built for scripts, and that makes it a natural fit for AI agents. Responses are compact JSON, errors are readable, and there are only five things to learn. Give a model access to it and it can run the mechanical side of your network while you decide the strategy.

Give Your Agent Tools

Wrap each endpoint as a tool and keep the Auth Key inside your wrapper, so the model never sees it. These definitions use Claude’s tool format; for OpenAI-style function calling, rename input_schema to parameters. The same shapes work as tools in an MCP server.

[
  {
    "name": "launchcdn_list_sites",
    "description": "List every site in the LaunchCDN account with its hosting type, name servers, origin server and access details.",
    "input_schema": { "type": "object", "properties": {} }
  },
  {
    "name": "launchcdn_get_site",
    "description": "Get the details for one domain in the LaunchCDN account.",
    "input_schema": {
      "type": "object",
      "properties": { "domain": { "type": "string", "description": "e.g. example.com" } },
      "required": ["domain"]
    }
  },
  {
    "name": "launchcdn_deploy_site",
    "description": "Deploy a registered domain to LaunchCDN behind a CDN. Uses one domain slot from the plan. Ask the user to confirm before calling.",
    "input_schema": {
      "type": "object",
      "properties": {
        "domain": { "type": "string" },
        "type": { "type": "string", "enum": ["wordpress", "static"] },
        "cdnprovider": { "type": "string", "enum": ["amazon", "cloudflare", "bunnycdn"] },
        "protocol": { "type": "integer", "enum": [1, 2, 3, 4], "description": "1 http://, 2 http://www., 3 https://, 4 https://www." },
        "wpsitename": { "type": "string", "description": "WordPress sites only" },
        "wpsitedesc": { "type": "string", "description": "WordPress sites only" }
      },
      "required": ["domain", "type", "cdnprovider"]
    }
  },
  {
    "name": "launchcdn_wordpress_login_link",
    "description": "Get a one-time sign-on link to a WordPress site's admin area.",
    "input_schema": {
      "type": "object",
      "properties": { "domain": { "type": "string" } },
      "required": ["domain"]
    }
  }
]

Leave wpuser and wppass out of the tool and have your wrapper generate them, so admin passwords never pass through the model.

Example Prompts

• “Deploy these five domains as WordPress sites on Cloudflare with HTTPS, then list the name servers for each one.”
• “Check every site in my account and tell me which ones still need their name servers set at the registrar.”
• “Give me a WordPress login link for example.com.”
• “Deploy example.org as a static site on Bunny.net, then publish the homepage from this HTML file.”

Workflows That Work Well

• Launch a batch. The agent deploys each domain, waits for it to go live, then sets the name servers through your registrar’s API or MCP server.
• Publish and refresh content. Using the origin server and access details from the API, the agent writes posts through the WordPress REST API, or uploads pages to HTML/PHP sites, and keeps prices and round-ups current on a schedule.
• Audit the network. A scheduled agent lists every site and compares the name servers we return with what’s set at the registrar, flagging anything that doesn’t match.
• Hand off to a human. When something needs a person, the agent fetches a one-time WordPress login link instead of sharing a password.

Guardrails

• Confirm before deploying. Deploys use plan slots, so have the agent ask before it calls deploy. The API can’t delete domains, which limits what a misbehaving agent can do.
• Keep credentials out of the model. Responses include site logins. Strip them in your wrapper unless a step needs them, and never paste your Auth Key into a prompt.
• Edit sites at the origin. Send content edits to the site’s origin server from the API rather than through the CDN, so changes apply immediately.
• Identify your tool. Send a descriptive user agent that names your tool, not an HTTP library’s default.

API Questions We Get Asked

Can I use the LaunchCDN API with ChatGPT, Claude or other LLMs?

Yes. The API is plain HTTPS with JSON responses, so any model that supports tool use or function calling can drive it through a small wrapper. Define the endpoints as tools, keep your Auth Key in the wrapper, and the model can deploy domains, look up sites and fetch WordPress login links.

Can I connect the API through MCP?

Yes. Each endpoint maps cleanly to an MCP tool, so you can wrap the API in a small MCP server and use it from any MCP-compatible client or agent framework. The tool definitions on this page are a good starting point.

Does API access cost extra?

No. The API is included on every LaunchCDN plan at no extra charge. Deployed domains use slots from your plan in the usual way.

Can an AI agent delete my sites through the API?

No. The API can deploy domains and read details about them, but it cannot delete domains. Removing a site is done from your dashboard.

Can my agent edit site content?

Yes. The API returns each site’s origin server and access details, so an agent can publish and update content directly: through the WordPress REST API for WordPress sites, or through DirectAdmin and FTP for HTML/PHP sites.

Where is the full API documentation?

Full documentation with request examples and a Postman collection is at api.launchcdn.com.

Documentation and Partnerships

Full documentation with request examples and a Postman collection lives at api.launchcdn.com.

Building a commercial integration? Email us. We’re happy to discuss affiliate partnerships and co-marketing with tools that make sense for PBN operators.