The Domains page shows all API hostnames available to your account. Every account gets a default regional endpoint. Enterprise accounts can additionally bind one custom domain.
Permissions
| Action | primary-owner | owner | member |
|---|
| View domains | ✓ | ✓ | ✓ |
| Add custom domain | ✓ | ✓ | — |
| Verify domain | ✓ | ✓ | — |
| Remove domain | ✓ | ✓ | — |
Default endpoint
You must use the regional endpoint assigned to your account. API keys are region-specific and cannot authenticate against a different region.
| Region | Endpoint |
|---|
| US | https://api.us.babysea.ai/v1 |
| EU | https://api.eu.babysea.ai/v1 |
| APAC | https://api.jp.babysea.ai/v1 |
The default endpoint is always active, cannot be removed, and continues to work even when a custom domain is active.
Custom domains
Enterprise accounts can bind one custom domain, giving you a branded API base URL:
https://api.yourcompany.com/v1
BabySea manages the edge connection and TLS. You manage the DNS record at your DNS provider.
Requirements: Enterprise plan · owner or primary-owner role · DNS admin access to publish a CNAME record.
Domain statuses
| Status | Badge | Meaning |
|---|
pending | Amber | Registered but DNS not yet verified |
active | Green | DNS verified, TLS provisioned, serving traffic |
removing | Amber | De-provisioning in progress |
Normal flow is pending → active. Removal briefly shows removing before the row disappears.
Setup
Open Domains
Navigate to Domains in the sidebar.
Add a custom domain
Click Custom domain in the top right. Enter the hostname you want to bind (4–253 characters, lowercase):Click Add. BabySea provisions the required CNAME target and adds the row with pending status. Configure DNS
Open the row actions menu and click Setup and verify. The dialog shows the DNS record to publish:| Field | Value |
|---|
| Type | CNAME |
| Name | Your domain (e.g. api.yourcompany.com) |
| Value | The target shown in the dialog |
Create this CNAME record at your DNS provider. Each field has a copy button.Use a CNAME record only — not A or AAAA. BabySea requires CNAME resolution to route edge traffic and provision TLS certificates.
Verify DNS
After publishing the CNAME, click Verify DNS in the dialog. BabySea checks DNS resolution and TLS readiness, then returns one of these results:| Result | What to do |
|---|
Domain is active | Nothing — your domain is ready |
DNS not configured | Create or correct the CNAME record in your zone |
Generating SSL Certificate… | DNS is resolving — wait a few minutes and verify again |
Domain verification in progress | Edge is settling — retry after a short wait |
Failed to check domain status | Transient failure — retry verification |
After verification
The row status changes from pending to active. Use your custom domain immediately:
curl -X POST https://api.yourcompany.com/v1/generate/image/bfl/flux-schnell \
-H "Authorization: Bearer bye_your_api_key" \
-H "Content-Type: application/json" \
-d '{"generation_prompt": "A baby seal plays in Arctic"}'
Both the custom domain and the default endpoint remain active. Existing integrations using the default endpoint are unaffected.
DNS and TLS details
Propagation
Global DNS changes are subject to TTL propagation delays. If verification reports DNS not configured, allow propagation time and retry.
TLS certificates
Certificates are auto-provisioned via automated Certificate Authority once DNS is routing correctly. Once issued, they renew automatically — no manual management needed.
Troubleshooting DNS
| Problem | Cause | Fix |
|---|
DNS not configured | CNAME not created | Create the record at your DNS provider |
DNS not configured | CNAME points to wrong target | Update the value to match the dialog |
DNS not configured | DNS hasn’t propagated | Wait and retry |
DNS not configured | Using A record instead of CNAME | Delete the A record, create CNAME |
DNS not configured | Conflicting records on the same name | Remove existing A, AAAA, or CNAME records first |
| SSL still generating after repeated checks | — | Verify the CNAME with a DNS lookup tool, retry, or remove and re-add the domain |
This domain is already in use by another account | Domain registered elsewhere | Contact support if you own it |
Removing a custom domain
Open Domains
Navigate to Domains in the sidebar.
Open the row menu
Click the actions menu on the custom domain row and select Remove.
Confirm
The confirmation dialog warns that API requests will stop immediately. Click Remove to confirm.
On removal: API traffic to the custom domain stops immediately · the row transitions to removing then disappears · the default endpoint is unaffected · you can provision a new custom domain again if eligible.
Removal is permanent and immediate. Update all integrations to use the default endpoint or a new custom domain before removing.
Plan changes
Custom domains are an Enterprise-only feature. If your plan changes:
| Scenario | Effect on custom domain |
|---|
| Downgrade from Enterprise | Domain is automatically removed — enters removing, stops serving traffic, and is purged from the registry. Removal is logged in Activity. |
| Subscription canceled or expired | Same automatic cleanup as a downgrade. Grace-period states do not trigger removal immediately. |
| Upgrade to Enterprise | Provision a custom domain immediately from the console. |
After any removal (manual or automatic), you can re-add the same domain or a different one as long as your account is on an active Enterprise plan. The new domain goes through the full setup and verification process.