You publish files for machines to read, but nothing that tells one how to become a customer.

None of the nine known agent entry paths answered, including /agent-signup.md and /.well-known/agent-access.json. Reading is solved on your site; joining is not.

10/ 13

A dashed column is a stage we could not measure, not a stage you failed.

A · Discovery: 6/6
B · Agent entry: 0/2
C · Registration: n/m
D · Provisioning: 2/3
E · Integration: 2/2

of the 13 points that apply to you and we could measure · 4 of 17 were not scored

You 10 · category median 5 · best name.com 10 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+1point, taking 10/13 to 11/13

This is the whole list: everything we could measure and you do not pass. Another 4 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

1
OAuth dynamic client registrationa project · +1
Publish OAuth authorization server metadata with an RFC 7591 registration_endpoint in it. It is the only standard way an agent registers itself without a human.

Then, when you have room

MCP surface a project · +1You already talk about MCP, and nothing answered at the addresses named above. If your server is at another path, declare it at /.well-known/mcp.json: that file is what an agent reads first, and it is what makes the path stop mattering.
Free tier or no-card trial stated in text a project · +1If you have a free tier or a no-card trial, say so in text on the pricing page rather than in an image or a button. If you are usage-priced with no free tier, this check is one an agent will read as a cost, not a defect.

Take it with you

3 of the checks an agent depends on, name.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on name.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Read the audits in full What the same run on name.com costs

Against domain registration and dns

You lead the 11 we have scanned in this category.

1
name.comyou
10/13
2
inwx.com
6/11
3
porkbun.com
8/15
4
dnsimple.com
8/16
5
namecheap.com
4/8
6
dynadot.com
6/13
7
netim.com
5/11
8
gandi.net
5/13
9
njal.la
5/13
10
godaddy.com
3/8
11
hover.com
3/11

Where competitors pass and name.com does not

OAuth dynamic client registrationnamecheap.com · dynadot.com
MCP surfacenamecheap.com · dynadot.com
Free tier or no-card trial stated in textdnsimple.com

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

DiscoveryCan an agent find and read you?

6/6

Agent entryIs there a door built for a machine?

0/2

RegistrationCan an agent get an account?

not measured

ProvisioningCan it get credentials without a human?

2/3

IntegrationCan it ship working code?

2/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

A · Discovery

PASS
Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology) across three tries (200, 200, 429)
PASS
llms.txt publishedllms.txt and llms-full.txt present at https://www.name.com/llms.txt and https://www.name.com/llms-full.txt and https://docs.name.com/llms.txt and https://docs.name.com/llms-full.txt, and the 12 links we sampled across both files all answer
PASS
Docs readable without JavaScript7,876 characters of text without JS, on https://docs.name.com/api/v1/reference/account-info/check-account-balance rather than on https://docs.name.com
PASS
On-demand agents not blockedNo on-demand agent is blocked
PASS
Paths robots.txt points at answernone of the 2 concrete paths your robots.txt allows is gone, though /account/login answered us 429
PASS
No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

UNMEASURED
Agent entry pointUnmeasurable: 9 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
FAIL
OAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomainsRFC 7591 is the only standard path by which an agent can register itself without a human.
FAIL
MCP surfaceMCP mentioned 36x in your own files, but nothing answered at mcp.name.com, mcp.name.com/mcp, mcp.name.com/v1/mcp, api.name.com/mcp, /mcp or /api/mcpAn MCP server turns your API from something an agent reads about into something it can call.

C · Registration

UNMEASURED
No CAPTCHA in the signup HTMLUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://www.name.com/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
UNMEASURED
Signup reachable without a browserUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://www.name.com/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.

D · Provisioning

PASS
Programmatic key provisioning2 of 7 provisioning phrases across the 8 documents we read: "management api", "account api"
FAIL
Free tier or no-card trial stated in textNo free tier or no-card wording at https://www.name.com/pricingA free tier is what lets an agent finish the job in the same session it started. Usage-priced products with self-serve signup can fail this honestly, which is why it is one point and not a verdict.

E · Integration

PASS
Typed SDK on the registry@namecom/core-api@1.33.0 ships types, matched from the registry by who publishes it rather than by a link on your site
PASS
Machine-readable API descriptionDocs serve markdown to machines, at https://docs.name.com

What we discovered on the way

Docs: https://docs.name.com · found on a subdomain
Pricing: https://www.name.com/pricing · linked from the site
Signup: not found
npm package: @namecom/core-api (registry guess)
GitHub: not found
Package licence: MIT
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none