Put a custom domain on your API with TLS

How do I put my brand on my API?

Your customers should see your domain, not ours. Add one DNS record and APIblaze serves your API there, with HTTPS set up for you.

Works for your API, its MCP server, its developer portal and its login pages, and it is the address Claude’s and ChatGPT’s connector directories ask for.

Put APIblaze in front of your API

$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yaml

Paste it in a terminal. No servers to run. The link is a sample restaurant API; swap in your own. Then add your domain, as shown below.

Watch it

Same API, your name on it

Everyone who calls your API sees your domain, with a valid certificate.

Before
Nino’s Pizza API
https://ninopizzas.abz.run/restaurants

Your API on an APIblaze address

Address
ninopizzas.abz.run
Whose name callers see
APIblaze’s
Certificate
Issued to APIblaze’s domain
Protocol
HTTPS, TLS 1.2 or newer
After
Nino’s Pizza API
https://api.ninopizzas.com/restaurants

Connection is secure, on your own domain

Address
api.ninopizzas.com
Whose name callers see
Yours
Certificate
Issued to api.ninopizzas.com, renewed for you
Protocol
HTTPS, TLS 1.2 or newer
How it works

One record, a certificate you never touch

Tell APIblaze your domain, and it gives you one DNS record to add wherever you manage that domain. Once the record is in, your certificate is issued and renewed for you.

api.ninopizzas.comActive

Calls to your domain reach your API over HTTPS, with all your rules.

The one record you add

At your DNS provider, the same place your website’s records live.

TypeCNAME
Nameapi
Targetproxy.abz.run

DNS on Cloudflare? Set the record to DNS only (the gray cloud), not proxied.

Claude and ChatGPT connectors

Your API, ready for Claude’s and ChatGPT’s directories

Both connector directories want your MCP server on your own domain, and it is one of the first things they check. APIblaze sets up the domain and the rest of what they ask for, then hands you the submission packet to send in.

Claude’s directory policy

“The MCP server domain should match your service.”

ChatGPT’s app review

Checks a verification file on your domain.

APIblaze serves it there for you.

1. Your domain

TypeCNAME
Namemcp
Targetproxy.abz.run
mcp.ninopizzas.comActive

The address both directories expect to see.

2. Directory-ready

Readiness report

  • MCP server on your own domain
  • Sign-in Claude and ChatGPT can use
  • ChatGPT’s domain check, served on your domain
  • Listing: name, tagline, privacy page, support
  • Reviewer test account
Claude: ready ChatGPT: ready

Submission packet written. You send it in.

3. In your users’ AI assistant

Nino’s Pizzamcp.ninopizzas.comConnected

Book a table for 2 at Nino’s tomorrow at 8 pm.

createReservation

Done. A table for 2 at Nino’s, tomorrow at 8 pm.

From your terminal

  1. Put your MCP server on your own domain

    $ npx apiblaze@latest domain add myapi --domain mcp.ninopizzas.com --kind mcp
  2. Check everything, apply the safe fixes, fill in what’s missing and write the submission packet

    $ npx apiblaze@latest connector myapi
  3. See the readiness report any time, without changing anything

    $ npx apiblaze@latest check --directory-ready myapi

Or in the dashboard

Switch on Directory-ready in your project’s Directory section. Its Readiness report lists every blocker with its fix, and Apply safe fixes handles the ones APIblaze can.

Set it up

Your name on every address

Your API is one of four places people see an APIblaze address. Each one can carry your domain. Replace myapi and ninopizzas with your project and tenant.

Your API

https://api.ninopizzas.com

$ npx apiblaze@latest domain add myapi --domain api.ninopizzas.com

Its MCP server

https://mcp.ninopizzas.com

Claude’s and ChatGPT’s connector directories expect this one on your own domain.

$ npx apiblaze@latest domain add myapi --domain mcp.ninopizzas.com --kind mcp

Its developer portal

https://developers.ninopizzas.com

$ npx apiblaze@latest domain add --tenant ninopizzas --kind portal --domain developers.ninopizzas.com

Its login pages

https://login.ninopizzas.com

$ npx apiblaze@latest domain add --tenant ninopizzas --kind auth --domain login.ninopizzas.com

Prefer the dashboard? The API and MCP domains are under the project’s Custom Domains; the portal and login pages under Tenants → Custom domains.

Common questions

  1. Do I need to buy or upload a certificate?

    No. APIblaze has a certificate issued for your exact hostname, and Cloudflare, which serves it, keeps it renewed.

  2. Which HTTPS (TLS) versions are allowed?

    TLS 1.2 and newer.

  3. How do I know when it is live?

    The domain moves from Pending DNS to Verifying SSL to Active. The dashboard shows it, and npx apiblaze@latest domain status prints any DNS record still missing.

  4. My DNS is on Cloudflare. Anything special?

    Set the record to DNS only (the gray cloud), not proxied.

  5. Can I use my root domain, like ninopizzas.com?

    Use a subdomain such as api.ninopizzas.com.

  6. Do I need my own domain for a Claude connector?

    To be listed in Claude’s or ChatGPT’s connector directory, yes: both expect the MCP server on your own domain. Add it with domain add --kind mcp, then npx apiblaze@latest connector checks the rest and writes the submission packet.

  7. Can each customer have their own domain?

    Yes. Add --tenant to pin a domain to one of your customers, so their calls arrive on their own name.

  8. What does it cost, and how do I stop?

    Each domain is billed monthly; prices are on the pricing page. If a monthly charge can’t be paid, the domain is suspended until you add credit. npx apiblaze@latest domain rm removes it and billing stops.

Prices are on the pricing page.

Put your brand on your API

No servers, no certificates to manage. One DNS record, and your name on every call.

$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yaml
Using an AI coding assistant? Paste this into Claude Code or Codex:Put my API on my own domain using npx apiblaze@latest skills