Your AI agent can now buy you a domain

For the last two years, every AI naming workflow has hit the same wall.

You ask ChatGPT for app names. It hallucinates a list. You copy each one into Namecheap. Half are taken. You go back to the chat. Conversation dies.

The bottleneck was never the LLM — Claude, GPT-4o, and friends are excellent at brandable name generation. The bottleneck was that no AI agent could check availability, quote a real price, or close a purchase.

Today we're shipping the missing layer.

What's launching

namemy.app now exposes a no-auth domain-availability API and a one-click buy URL through every interface AI agents already speak:

• MCP for Claude Desktop, Claude Code, Cursor, Windsurf, Continue.dev — npx @namemyapp/mcp
• OpenAPI Actions for ChatGPT Custom GPTs and Perplexity Pro Spaces — paste https://namemy.app/api/public/openapi.json
• REST for everything else (your own bot, a Cloudflare Worker, a shell script)
• CLI with nma link <domain> for the always-available no-key primitive
• A bundled Claude Code plugin — /plugin install namemyapp — that wires a SKILL, three slash commands, and the MCP server in one step

Every response includes a buyUrl. Click it, you land in namemy.app's checkout with the domain pre-selected, sign up + pay in one flow, and your AI agent stays in the conversation. No card details ever touch the AI session.

Why no-auth public mode

The public surface (/api/public/*) is genuinely no-auth, IP-rate-limited (100 GET/hr, 200 POST/hr per IP), and CORS-open. That means a Custom GPT or Perplexity Space installs in 2 minutes — paste a URL, set auth = None, done. You don't have to provision keys for every end user; they don't even need a namemy.app account to use the agent. They only sign up when they decide to buy.

The authed surface (/api/v1/*) is still there for power users — AI name generation, server-to-server purchase, owned-domain DNS — and gates higher-cost operations behind a Bearer key.

Hybrid checkout

Agent-referred users land in checkout with no namemy.app account. We collect WHOIS contact (legally required by registries anyway — name, address, phone, email), auto-provision a User row from that data, and email a one-click "claim your account" link via Cloudflare Email Sending. They get the domain, then a magic link to manage DNS and renewals from the dashboard.

Net result: zero-friction conversion for agent users, zero orphaned domains.

Attribution

Every API call accepts a ?source= parameter. We record it on every Purchase row and push events to PostHog. So if you build a Custom GPT or an MCP plugin, namemy.app knows your agent referred the conversion. A revenue-share dashboard for top referrers ships next.

Try it now

The fastest path:

1. Open ChatGPT → GPT editor → Create
2. Add an action with auth = None
3. Paste https://namemy.app/api/public/openapi.json as the Schema
4. Ask: "Help me name an AI productivity app — check codeflow.ai, codeflow.dev, codeflow.io"

Or one of the deeper-integration paths:

• Claude Desktop / Code
• Claude Code (bundled plugin)
• Cursor
• Perplexity
• Direct from any agent (REST + CLI)

Full install matrix: namemy.app/agents.

What's next

• Outbound webhooks so agents can listen for purchase completion (no polling).
• Streamable HTTP transport for the MCP server (web-friendly clients).
• Per-agent referral dashboard at /app/agents with conversion + revenue attribution.
• Bulk-with-proposal flow for high-volume agent products that want short shareable URLs.

If you're building an AI product that touches naming or branding and would benefit from any of this, ping us — support@namemy.app or @namemyapp on X.