Verify your domain
Verification is a single DNS record. The same record is what makes your
vanity MCP URL and AI-traffic landing pages work — one change, two payoffs.
Add the record
In your DNS provider (Cloudflare, Route 53, Namecheap, GoDaddy, etc.):
| Type | Host | Value | TTL |
|---|---|---|---|
CNAME | oasy.<your-domain> | cname.oasy.ai | default (Auto / 1h) |
Some providers want the fully qualified host (oasy.publisher.tld);
others want just the subdomain (oasy) and auto-append your apex.
Both produce the same record.
Verify
In the dashboard, on the MCP page, click
Check DNS on the amber "Finish verifying" banner. We resolve
oasy.<your-domain> server-side and confirm it CNAMEs to cname.oasy.ai.
On success we stamp customDomain on your Publisher row and the banner
disappears.
Why it works
cname.oasy.ai is an alias in our zone that resolves through to Vercel's
edge CDN. The MCP route in our app reads the request's Host header,
looks up the publisher by customDomain, and serves the right tools.
TLS auto-issues on our side.
Troubleshooting
"No CNAME record found yet" — DNS hasn't propagated. Most providers
update within 60 seconds; some take up to an hour. Try again.
"oasy.foo.com points at — the record
exists but targets the wrong value. Double-check the Value / Target
field is exactly cname.oasy.ai (no trailing dot, no https://).
"DNS lookup failed" — your DNS provider is returning SERVFAIL.
Re-save the record; some providers (looking at you, GoDaddy classic)
need a manual zone refresh.
Don't want to wait?
Click "Continue without verifying" on the onboarding screen. Your MCP
still works at the long https://api.oasy.ai/api/mcp/<orgId> URL.
The dashboard will keep reminding you until DNS lands.