name.com Track · DevNetwork Hackathon 2026

Measure the name before you buy it

The thing discovering your service is increasingly an AI agent, not a human. DomainArena tests whether agents can infer what service sits behind a domain — before you spend money on a name.

Try the Live Demo How it works
You buy a domain on intuition. The machine audience can't find you.
93% of Google searches now end without a click. Agents are making billions of API calls daily. But domain naming is still a human guesswork game.
Human Heuristic
velora.com
"Sounds technical and modern." Agent infers: a fantasy game. Score: 0.1. Result: WRONG
Agent-Tested
jsonrepair.dev
"Transmits meaning without context." Agent infers: JSON repair tool. Score: 0.9. Result: CORRECT
From inventory to verified receipt
Every step has provenance. The agent never sees the product description — only the domain name.
Step 1
name.com
Search available domains + live pricing
Step 2
Blind Test
Llama 3.3 sees only the hostname
Step 3
Score
Independent Mistral evaluator
Step 4
Recommend
Winner by comprehension + economics
Step 5
Approve
Human gates all writes
Step 6
Register
Fresh recheck then buy
Step 7
Verify
DNS readback + SHA-256 receipt
6
name.com API Endpoints
16
Experiments Run
148
Tests Passing
7+
Model Families Tested
Full domain lifecycle through one API
DomainArena uses six name.com capabilities: search, availability, pricing, registration, DNS create, and DNS readback. Every step is verified server-side before money moves.
POST/domains:searchdiscover available candidates
GET/domains/{name}:getPricingverify pricing before purchase
POST/domainsregister domain (approval-gated)
POST/domains/{name}/recordsconfigure DNS
GET/domains/{name}/recordsverify DNS configuration
name.com isn't just discovery. It is the authoritative transaction boundary immediately before money moves. Before registration, DomainArena re-queries availability and price. If anything changed, it fails closed.
Why one-shot domain ratings don't work
16 experiments revealed that agent naming behavior is much stranger than a simple LLM rating suggests.

Position dominates domain choice

In pairwise tests, 87% of agents picked the first option regardless of which domain was shown. TLD effects (.com vs .dev vs .ai) were statistically insignificant. Order matters more than extension.

Models disagree materially

Llama 3.3, Mistral Small, and Qwen3 produced different rankings for the same domains. A domain cannot be called "agent-legible" based on one model. Cross-family replication is essential.

Description seduction is real

Some model families selected broken tools when they had enterprise-sounding descriptions. Agent discovery systems can be manipulated by presentation rather than capability.

Semantic inversion is a cheap proxy

Blind inference is a useful first filter, but execution testing is ground truth. AgentSearchBench (10K agents) confirms description similarity is weaker than execution-grounded performance.

Serverless inference drifts

Identical prompts at temperature zero produced materially different choices across time windows. One-shot domain ratings are scientifically weak. DomainArena replicates across windows.

Generator/judge separation

The tested model never scores itself. Llama generates the inference, independent Mistral evaluates the match. This prevents self-reinforcing bias in comprehension testing.

From discovery to verified infrastructure
1
Search
2
Test
3
Score
4
Approve
5
Recheck
6
Register
7
Verify

The entire decision basis is frozen into a content-addressed SHA-256 receipt. Domain, intent, score, inference, prices, registration status, DNS verification — all hashed together. Proof that the decision was made with verified economic state, not gut feeling.

Measure the name. Buy the evidence-backed winner. Verify the infrastructure.

DomainArena attacks the decision before deployment: which available hostname best communicates the intended service to agents?