AI naming API for agents — with real domain checks

Brandname Maker is built for coding agents, LLM tools, and founders who need naming passes integrated into automated workflows. If you are building product naming into an agent or tool, this API returns structured shortlists with real domain availability checks — not brainstorming lists.

Agents call the API with a brief (what it is, who it's for, rejected names), pay with stablecoins or card, and return shortlists with consultant-style rationales plus domain status on each candidate.

Free browser-based naming tools (like those from Shopify, Wix, and similar services) are built for brainstorming and exploration. They work well for generating lists of ideas.

Brandname Maker is different:

• API, not browser UI — pay-per-call endpoint (GET and POST) for agents and code, not a web form
• Real registry checks — Fastly Domain Research lookups on shortlist candidates for .com, .app, and .ai TLDs
• Machine payment — stablecoins (Solana USDC, Tempo, Base USDC) at $0.25 per run or card/Stripe Link at $1.00 per run, with HTTP 402 payment challenges

The API does not provide trademark clearance or legal advice. Domain checks report registry availability only.

Each naming pass follows a structured process:

1. Sweep approximately 30 candidates — explore naming directions based on the brief
2. Narrow to 10–15 name + tagline table — reasoning for each candidate
3. Final shortlist of 3–6 names with taglines — consultant-style rationale for each: where the name comes from, what a stranger hears first, why it fits this customer, what the tagline does, and the one caveat

The response includes the full naming analysis: feeling table, customer experiences, passerby test, collision notes, and Fastly registry domain status for shortlist TLDs (.com and .app checked for every name, .ai as a strong third option for top names). When bare brand domains are scarce, the API may also check prefix variants (e.g., getsecondreader.com) that keep the brand word intact. Domain checks are capped at approximately 8–12 total per pass to manage lookup costs.

The API speaks MPP (Machine Payments Protocol). An unpaid request returns HTTP 402 with a WWW-Authenticate: Payment challenge listing accepted payment methods. Pick one rail, pay, and retry the same POST with Authorization: Payment.

For card or Link payments without a crypto wallet, agents can use the Link CLI:

npx @stripe/link-cli mpp pay https://brandnamemaker.com/api/v1/name \
  -X POST \
  --data '{"brief": "your brief here"}'

The Link CLI reads the 402 challenge, asks the Link account holder to approve the $1.00 spend on their phone, retries with the credential, and prints the naming pass. Card payments are refunded automatically if the naming pass fails.