names.dev · private beta

The right name
isn’t found.
It’s weighed.

names.dev turns a product brief into ranked, evidence-backed identity options across domains, handles, app stores, package namespaces, risk, and acquisition paths.

Compare what is claimable now, what needs a trusted partner path, and what should be watched or scouted before you build around it.

Acquisition budget

Type or paste an idea

Run a name decision →See the model Start a sprint

try

Scanning · 248 candidates

#01Lumerralumerra.ai

Domainpartner path · $18k-$32k

Handlesmostly available

GitHub orgclear

npm packageclear

Trademark risklow

94NameScore

#02Fluxframefluxframe.com

Domainaftermarket · $18k–$32k

Handlesmixed

GitHub orgavailable

npm packageavailable

Trademark risklow

91NameScore

#03Kairos Studiokairos.studio

Domainseller-verified · $3,900

Handlesmixed

GitHub orgavailable

Bundle IDno conflicts

Trademark risklow

88NameScore

#04Spectraspectra.ai

Domainparked since 2018

Handlesmostly taken

GitHub orgtaken

Acquisitionscoutable

Trademark riskmedium

87NameScore

+ 245 more · scored in 1.4sView all →

Identity surfaces

Decision signals

Source states

Partner

Routed fulfillment

100%

Human approval

What we are building

The decision layer before the transaction.

Registrars and marketplaces are strongest once a buyer knows what to buy. names.dev starts earlier: intent, fit, confidence, risk, and the right fulfillment path.

Understand intent

Parse product category, audience, tone, budget, platform needs, and words to avoid before generating names.

Weigh identity

Score each name across domains, handles, namespaces, app identity, risk, source freshness, and acquisition difficulty.

Route fulfillment

Send qualified demand to the right path: available registration, partner inventory, aftermarket offer, watchlist, or sprint.

Private beta

The public curtain is temporary. Behind it, names.dev is being tuned around better decisions, source confidence, and partner-routed fulfillment.

Start a sprint →View sample results

The product flow

From prompt to identity-launched.

names.dev turns a product idea into a scored identity decision, then routes the next step through the safest available path.

Describe project

Paste in what you are building, who it is for, the budget, and the constraints.

Generate territories

Brandable naming territories tuned to the category, tone, and audience.

Search surfaces

Domains, handles, GitHub orgs, package names, app identifiers, and aftermarket.

Score candidates

Twelve dimensions including trademark risk and acquisition difficulty.

Route next path

Available registration, partner purchase, offer, scout, watch, lease, or sprint. Whatever fits the name.

Human approval

Every cash buy, transfer, outreach, or paid action requires a one-shot signed token.

Configure identity

DNS, handles, GitHub org, package name, app identifier, trademark notes.

Launch identity

Landing direction, brand voice, launch copy. Ready to ship to Studio or Launch.

§ 01 / Why now

Code is becoming abundant. Names are still scarce.

AI agents can generate apps, landing pages, stores, and tools faster than ever. But every serious product still needs an identity people can remember, trust, search, type, and share. names.dev helps builders choose that scarce asset before the rest of the launch hardens around it.

Projects are multiplying

One founder can now launch ten experiments at once. Every one of them needs a name.

Good names do not scale

Short, memorable, category-defining domains remain scarce. The supply curve hasn't moved in a decade.

Agents need identity rails

Every AI-built project needs a way to find, score, route, and approve a real identity. Without rails, agents can't ship responsibly.

For the founder

“I'm naming a new company.”

From prompt to scored identity, with a claim path for domains, handles, namespaces, and launch surfaces.

For the operator

“I'm naming the next thing my agent ships.”

MCP-native. Fourteen tools. Writes gate behind one approval. Loop it into your build pipeline.

For the domain holder

“I have inventory I want builders to find.”

List once. We surface your names against semantically matching prompts and route qualified demand back through your preferred path.

§ 02 / Identity surfaces

A name is more than a domain.

Every serious product needs an identity across domains, handles, developer namespaces, app stores, and search. names.dev checks the whole surface area before you commit.

Domains

Registration, partner inventory, aftermarket, and watch/scout paths across every relevant TLD.

.com.ai.dev.app.iopremiumaftermarketscoutable

Handles

Availability and confidence signals across the platforms that matter for launch, distribution, hiring, and recall.

XInstagramTikTokYouTubeGitHubLinkedIn

Developer namespaces

Whether the package name, repo name, or container tag is yours to take without conflict.

GitHub orgsnpmPyPIcrates.ioDocker Hubcontainer tags

App identity

Whether your name can ship as a native app without naming collisions or bundle conflicts.

iOS bundle IDAndroid packageApp Store namePlay Store name

Trademark and risk

Basic conflict and confusing-similarity signals before you spend real money on a launch.

USPTOEUIPOcategory overlapcommon-word riskhomograph risk

Brand system

Voice, palette, type direction, and a logo prompt designers can hand straight to Claude Design.

voicepalettetypelogo prompttaglinelanding direction

Every surface checked in parallel.

§ 03 / How it works

One prompt. Every identity surface in play.

Understand

What are you building?

Parse product, category, audience, tone, budget, and constraints from a plain-English prompt. The interpretation is shown and one-click correctable.

Search

Every identity surface at once.

Domains, handles, GitHub orgs, package names, app identifiers, aftermarket inventory, seller-claimed listings, and scoutable assets.

Score

Twelve dimensions, 1.4 seconds.

Brandability, memorability, pronunciation, spelling risk, domain strength, handle availability, namespace availability, category fit, trademark risk, acquisition difficulty, price sanity, resale potential.

Route

Show the right next path.

Available registration, trusted partner inventory, aftermarket offer, broker path, watchlist, sprint, or launch kit. Every write gates behind a one-shot signed approval token.

§ 04 / The score

Every name is weighed across twelve dimensions.

A name is not just available or unavailable. It carries brand value, namespace risk, acquisition difficulty, resale potential, and timing. NameScore combines twelve subscores into one 0–100 decision model for product identity.

Candidate · ranked 01 of 248scored 1.4s

Lumerra

Primary domain: lumerra.ai

Domainaftermarket · partner path

Handlesmostly available

GitHub orgclear

Package risklow

Trademark risklow

SCORE

strong fit

Verdict

Strong brand fit with a partner-routed aftermarket path. Good choice if the budget supports acquisition; otherwise compare nearby available variants before committing.

Twelve dimensions

Brandability96

Distinct in category

Memorability94

Spelled right after one hearing

Pronunciation92

Two syllables, vowel-friendly

Spelling risk89

No ambiguous letters

Domain strength88

Strong .ai aftermarket path

Handle availability78

@lumerra free on 4 of 6

Namespace availability90

GitHub org + npm clear

Category fit95

Pattern-matches AI tooling

Trademark risk91

No conflicts found

Acquisition difficulty72

Partner-routed purchase

Price sanity86

Below comp median ($31k)

Resale potential87

12 comps in band

§ 05 / Built for agents

Not another name generator.
An agent-native identity layer.

Agents should not browse registrars, marketplaces, handle checkers, and trademark tools one by one. They query intent. names.dev turns a project description into scored, actionable identity options. Fourteen tools expose search, scoring, and prepared actions. Writes gate behind a one-shot signed human approval.

agent → names.devtools/call · find_names

{
  "tool": "find_names",
  "intent": "AI video editor for creators",
  "style": ["short", "premium", "brandable"],
  "budget": 15000,
  "surfaces": ["domain", "handles", "github", "npm", "app_store"]
}

names.dev → agentresponse · top candidate

{
  "name": "Lumerra",
  "score": 94,
  "domain": "lumerra.ai",
  "domain_status": "aftermarket_partner_path",
  "handles": "mostly_available",
  "namespace_risk": "low",
  "trademark_risk": "low",
  "recommended_action": "compare_partner_path",
  "approval_required": true
}

$ names mcp connect

Names MCP · private beta

Fourteen Names MCP tools

01find_names

02score_name

03check_domains

04check_handles

05check_namespaces

06search_inventory

07estimate_value

08prepare_offer

09register_domain

10watch_name

11verify_inventory

12create_names_manifest

13setup_dns

14launch_identity

Ships across eight surfaces

ClaudeCodexCursorWindsurfChatGPTReplitVercelAxint StudioSwarm

View MCP docs See the protocol

§ 06 / Demand graph

The ecosystem sees sales.
names.dev sees intent.

Every prompt, search, shortlist, watchlist, and MCP call adds a demand signal. Sellers learn what agents are looking for before a transaction happens.

Sales data tells you what already happened. Intent data tells you what builders are about to name, buy, and launch.

BUYER INTENT · DEMO DATAexample intent graphproduction graph starts with beta usage

categoryagent searchesavg budgetsupply gaphot surfacesurgency

AI video2,419$12khigh.ai.comnow

Agent devtools1,204$9khigh.dev.ai.comnow

Health OS811$18kmedium.health.ai.comsoon

AI wellness1,082$10khigh.ai.co.studionow

Local service automation934$7kmedium.co.com.bizsoon

Creator commerce672$6klow.co.com.studiolater

§ 07 / Comparison

How names.dev complements what exists.

provider ecosystemnames.dev layer

Transactional searchProject-intent search

Human-first UXAgent-readable interface

Supply surfacesDemand signal layer

Inventory by sourceAvailable, aftermarket, premium, seller-verified, partner, and scoutable

Listings and checkoutIdentity intelligence before checkout

Buy or bidRoute registration, partner purchase, offer, scout, lease, or sprint

§ 08 / Acquisition

Four ways to take a name home.

Some names can be claimed in minutes. Others need an offer, scout path, lease, or brokered acquisition.

Register

For available names.

Route to the selected registrar with final live check and approval.

Buy

For fixed-price aftermarket.

Escrow and transfer through the trusted provider path.

Offer

For negotiable listings.

Anchor-based offer band keeps both sides honest.

Scout

For names not yet for sale.

Owner research, contact strategy, max-bid memo.

Advanced acquisition paths

Lease-to-own

Pay monthly toward ownership under a clear partner or seller agreement.

Revenue share

Pay nothing upfront. Share % of revenue against a cap.

Advanced structure

Qualified private-beta paths only, with counsel and human approval.

§ 09 / NameScout

For names that are not for sale yet.

names.dev maps names that are unused, parked, underdeveloped, or not publicly listed, then prepares a human-approved acquisition plan. Owner research, contact strategy, offer band, escrow plan, and your maximum approved offer. All outreach requires human approval before send.

01Owner discovery from registry, social, and corporate records
02Warm-intro pathfinding through your network
03Anchor-based offer band, never anchored to seller’s ego
04Compliant outreach drafted for your review — never autonomous

Scoutable identity

Kairos Studiokairos.studio

StatusNot publicly listed

UsageParked since 2018

Acquisition difficultyMedium

Estimated fair range$8,000 to $18,000

Recommended actionPrepare offer

Next stepHuman-approved outreach

NameScout proposes a path. The first message goes nowhere without a one-shot human approval. No automated cold spam.

§ 10 / Sellers

Make your names discoverable to AI buyers.

Connect your registrar, upload a CSV, add a DNS TXT record, or publish a names.json file. names.dev turns your portfolio into agent-readable inventory that surfaces against matching buyer prompts — including the ones still being typed.

Connect registrar

Sync domains from Spaceship, GoDaddy, Namecheap, Cloudflare Registrar, or other providers.

~ 30 seconds · automatic sync

Upload CSV

Bulk import portfolios with pricing, minimum offers, lease options, and category tags.

~ 1 minute · 10,000 row limit

Verify with DNS

Add one TXT record to prove ownership and activate agent-readable listings.

manual · zero registrar lock-in

Publish names.json

Expose sale status, pricing, offer rules, and escrow settings in a machine-readable format.

self-hosted · the protocol path

What sellers get

Verified ownership

DNS TXT, registrar OAuth, or .well-known file.

Buyer-intent alerts

Notifications when prompts match your inventory.

Agent-readable listings

Manifest spec + machine-readable JSON.

Offer routing

Accept cash, lease, or qualified advanced structures.

Minimum offer rules

Filter low-ball offers automatically.

Portfolio analytics

Demand match rate, views, offer flow.

List your portfolio For brokers

SELLER · DEMO PORTFOLIOillustrative sample

248

total

217

verified

intent matches

$3.6k

avg offer

high demand

namescoreaskintereststatus

spectra.aihot87$28k12 promptslive

lumera.aihot94$24,50031 promptslive

kairos.studio88$3,9007 promptslive

halia.so86$1,2004 promptsdraft

draft.fm81$2,4009 promptslive

atlas.run76$5401 promptsneeds verify

· 3 OFFERS PENDING REVIEWReview →

§ 11 / Protocol

A machine-readable identity file for every name.

names.dev publishes an open spec — /.well-known/names.json — that any owner can host. Agents, partner marketplaces, and internal tools can read sale status, handles, categories, asking price, minimum offer, and allowed actions in one structured fetch.

/.well-known/names.jsonopen spec · v1.0 draft

{
  "spec": "https://names.dev/schema/v1/names.schema.json",
  "version": "1.0",
  "name": "Lumerra",
  "domains": [
    {
      "domain": "lumerra.ai",
      "status": "for_sale",
      "asking_price": 12000,
      "minimum_offer": 7500,
      "currency": "USD"
    }
  ],
  "handles": {
    "x": "@lumerra",
    "github": "lumerra"
  },
  "owner": { "type": "individual", "verified": true },
  "categories": ["ai", "video", "creator-tools"],
  "agent_offers_enabled": true,
  "human_approval_required": true,
  "escrow_supported": true,
  "lease_to_own": true,
  "agent_endpoint": "https://names.dev/api/mcp",
  "offer_endpoint": "https://names.dev/api/offers/lumerra",
  "settlement": "escrow.com"
}

For sellers

Publish one JSON file to expose pricing, offer rules, and escrow options to every agent buyer at once.

For agents

One fetch returns sale status, asking price, minimum offer, and the right write endpoint to call.

For registrars

Surface portfolio inventory to agent-driven demand without ceding the customer relationship.

For partners

Adopt the spec to expose your listings to agent buyers without rebuilding your stack or ceding the customer relationship.

§ 12 / Sources

The graph we read.

Eight signal streams, deduplicated, scored, and ranked together in one feed. No source is treated as authoritative on its own.

Registrars

Cloudflare, Spaceship, OpenSRS, Namecheap availability + pricing

Aftermarket

Sedo, Atom, Dan, Afternic listings + comps

RDAP / WHOIS

Owner, registrar, expiration, nameservers

DNS

MX, TXT, CNAME, nameserver patterns

Public web

Parked pages, for-sale notices, landing intent

Seller uploads

Verified portfolios with manifest

Buyer prompts

Anonymized intent signals from agent queries

MCP calls

Tool-call telemetry per category

§ 13 / Approval

Agents recommend. Humans approve.

names.dev can search, score, compare, prepare offers, and configure workflows. Purchases, transfers, paid actions, and outreach require explicit human approval.

Human approval for purchases

Every cash buy, lease commitment, offer, DNS write, and seller listing requires a one-shot HMAC-signed approval token bound to the exact action.

Verified seller ownership

Domains only surface as agent-readable inventory after DNS TXT verification, registrar OAuth, or a published manifest.

Transparent pricing and offer paths

Score-anchored asks. Side-by-side fee disclosure. No hidden markups. Both buyer and seller see the same number.

No hidden background crawling

No unauthorized marketplace scraping. No silent outreach. Every external request is rate-limited, attributed, and logged.

01 · Agent

prepares action

prepare_offer('lumerra.ai')

02 · names.dev

issues one-shot token

HMAC · scoped · 60s ttl

03 · Human

approves in console

names.dev/approve/7f3e2c

04 · Provider

executes approved path

provider action · confirmed

Every write tool — register, offer, list, DNS, or advanced bid — passes through this gate. Tokens are one-shot, scoped to the exact action, and expire in 60 seconds. The agent never holds keys.

§ 14 / Network effect

Every install makes the graph smarter.

More agents create more intent. More intent attracts more sellers. More seller data improves every recommendation. The graph compounds.

01
Agent searches
Every MCP call adds a demand signal.
02
Buyer intent
Aggregated into a private graph by category, budget, TLD.
03
Better scoring
Score model trains on which candidates buyers actually accept.
04
Seller claims
Holders see matching demand and list inventory against it.
05
Verified supply
DNS TXT + manifest = trusted inventory layer.
06
Better results
Scored matches rank higher than blind keyword search.
07
More agent adoption
Loop accelerates with every new install.

More verified inventory

Turn scattered portfolios into verified agent-readable supply without locking sellers into names.dev.

More nodes

Local tools, MCP servers, browser extensions, and registrar connections keep the graph fresh.

MOAT 01

Cross-surface identity intelligence

A name is more than one domain.

names.dev scores domains, handles, app identity, developer namespaces, risk, and acquisition paths together. The source and confidence state belong on every result card.

scoring dimensions

MOAT 02

Buyer intent graph

We learn what builders want before they buy.

Private-beta searches, watchlists, saved candidates, and MCP calls can become aggregated demand signals. Private prompts stay private; graph contribution is opt-in where it matters.

Beta

aggregated demand signals

MOAT 03

Verified inventory layer

Sellers keep control while agents can understand supply.

Registrar sync, DNS verification, seller uploads, and names.json make inventory machine-readable without forcing sellers into a closed marketplace.

names.json

open inventory manifest

§ 15 / Launch identity

Do not just choose the name. Launch the identity.

Once a name is approved, names.dev prepares the next actions: DNS, landing direction, handles, GitHub and package namespaces, and the launch kit a designer or agent needs to ship the v1 site this week.

Route the domain path

Available registration, partner inventory, or aftermarket path through whichever provider you trust. Approval-gated.

02OPEN →

Configure DNS

Email-safe SPF, DKIM, DMARC, A and CNAME defaults, and the names.json claim record.

Reserve handles

Preferred handle stem with prioritized fallbacks across the six brand-launch platforms.

Suggest GitHub org

Clean org name and a starter repo path. Checked against existing namespaces before commit.

Suggest package name

npm, PyPI, and crates.io names that don't squat someone or shadow a popular package.

06OPEN →

Generate tagline

One sharp line of positioning per voice direction, ready for the homepage hero.

07OPEN →

Generate logo direction

Wordmark concept, paired with a drop-in image prompt you can hand to a designer or to Claude Design.

08OPEN →

Create landing direction

Hero headline, sub, three value-prop bullets, primary and secondary CTA, all in the chosen voice.

09OPEN →

Ship to a Ship

Hand off to Studio for creative, Axint for Apple-native runtime, Launch for deploy and control.

Find a name →View a brand kit See a Ship

§ 16 / Capital

Flexible acquisition for serious names.

For premium names where a simple purchase does not close: lease-to-own, revenue share, or qualified non-cash structures. Every advanced path is private beta, counsel-reviewed by the parties, and routed through explicit human approval.

This is not legal, tax, financial, or securities advice. Standard cash, lease, and partner offer flows handle the normal path; advanced structures stay gated.

View advanced paths Post a project

PRICING ANCHORadvanced path · demo

private beta

spectra.aiSPCTR.AI · listing #2841

score87strong

pathlease-to-ownpartner route

range$8k-$18kfair range

sellerverifiedDNS / registrar

counselrequiredadvanced terms

statusprivate betaqualified parties

approvalrequiredone-shot token

RATIONALE · Score 87 supports a structured acquisition path. Comparable .ai names in category suggest a fair range of $8k-$18k before any custom terms. Counsel review: required.

§ 17 / Use cases

Use it from the website, from your agent,
or from your portfolio.

Free

Find and score identities from one prompt.

Join early access →

Pro

Deep reports, watchlists, acquisition plans, and premium scoring.

Join early access →

Seller

Portfolio upload, buyer-intent alerts, agent-readable listings, and verified ownership.

Join early access →

API / MCP

Programmatic identity intelligence for agents, builders, and platforms.

Join early access →

See the full pricing page for transaction-fee schedule and concierge tiers.

§ 18 / Endgame

From one prompt to a launched company.

Name.

lumerra.ai · score 94

Route.

partner path · approved

III

Configure.

DNS · MX · TXT · CAA

Deploy.

lumerra.ai/ · landing v0.1 live

Provision.

founders@lumerra.ai · sending

From one prompt to a fully identity-launched company, with one human approval.median end-to-end · 8m 40s

Find the name before someone else does.

names.dev helps agents and builders discover the scarce identity asset behind every new project.

Find a name →List your portfolio Install MCP

The right nameisn’t found.It’s weighed.

The decision layer before the transaction.

Understand intent

Weigh identity

Route fulfillment

From prompt to identity-launched.

Describe project

Generate territories

Search surfaces

Score candidates

Route next path

Human approval

Configure identity

Launch identity

Code is becoming abundant. Names are still scarce.

Projects are multiplying

Good names do not scale

Agents need identity rails

A name is more than a domain.

Domains

Handles

Developer namespaces

App identity

Trademark and risk

Brand system

One prompt. Every identity surface in play.

Understand

Search

Score

Route

Every name is weighed across twelve dimensions.

Not another name generator.An agent-native identity layer.

The ecosystem sees sales.names.dev sees intent.

How names.dev complements what exists.

Four ways to take a name home.

Register

Buy

Offer

Scout

Lease-to-own

Revenue share

Advanced structure

For names that are not for sale yet.

Make your names discoverable to AI buyers.

Connect registrar

Upload CSV

Verify with DNS

Publish names.json

Verified ownership

Buyer-intent alerts

Agent-readable listings

Offer routing

Minimum offer rules

Portfolio analytics

A machine-readable identity file for every name.

For sellers

For agents

For registrars

For partners

The graph we read.

Registrars

Aftermarket

RDAP / WHOIS

DNS

Public web

Seller uploads

Buyer prompts

MCP calls

Agents recommend. Humans approve.

Human approval for purchases

Verified seller ownership

Transparent pricing and offer paths

No hidden background crawling

Every install makes the graph smarter.

Agent searches

Buyer intent

Better scoring

Seller claims

Verified supply

Better results

The right name
isn’t found.
It’s weighed.

Not another name generator.
An agent-native identity layer.

The ecosystem sees sales.
names.dev sees intent.

Use it from the website, from your agent,
or from your portfolio.