Let Agents In

Agent readiness · hover.com

2026-08-12 10:59 UTC · formula v9.2 · 12.4s

There is no door built for a machine anywhere on your domain.

None of the nine known agent entry paths answered, including /agent-signup.md and /.well-known/agent-access.json.

3/ 11
A · Discovery
3/4
B · Agent entry
0/4
C · Registration
0/1
D · Provisioning
0/1
E · Integration
0/1

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

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

Pass it onEmail itLinkedIn

Probably the wrong yardstick

We found no documentation, no SDK and no API description, so this may not be a product developers integrate. The formula measures whether an agent can adopt you as a building block. Judged as anything else, the score below is not meaningful.

Fix this first

+4points, taking 3/11 to 7/11, past inwx.com, namecheap.com, dynadot.com

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

  1. 1
    llms.txt publishedminutes · +1

    Publish /llms.txt: a markdown list linking your quickstart, API reference, pricing and package name. It is the cheapest file on this list.

  2. 2
    Agent entry pointan afternoon · +2

    Publish /agent-signup.md: the path from nothing to a working key, written as steps for a machine rather than a tour for a person. Ours is at /agent-signup.md if you want a worked example, and it says plainly that we have nothing to sign up for.

  3. 3
    Machine-readable API descriptionan afternoon · +1

    Publish an OpenAPI file at /openapi.json, or serve markdown when a client sends Accept: text/markdown. Either one stops agents guessing your API.

Then, when you have room

  • OAuth dynamic client registration a project · +1Publish 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.
  • MCP surface a project · +1Wrap your top three API calls in an MCP server and declare it at /.well-known/mcp.json.
  • Signup reachable without a browser a project · +1Let https://www.hover.com/signup render its form in server HTML and stop refusing non-browser requests to it.
  • 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

8 of the checks an agent depends on, hover.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 hover.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 fullWhat the same run on hover.com costs

Against domain registration and dns

You are 11 of 11 in a category where a developer is trying to register a domain and point it somewhere with nobody at the keyboard.

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

Where competitors pass and hover.com does not

  • llms.txt publishedporkbun.com · dynadot.com · name.com · godaddy.com · inwx.com
  • Signup reachable without a browserporkbun.com · dnsimple.com · netim.com · njal.la
  • Machine-readable API descriptionporkbun.com · name.com · godaddy.com
  • Paths robots.txt points at answerporkbun.com · name.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

A
DiscoveryCan an agent find and read you?
3/4
B
Agent entryIs there a door built for a machine?
0/4
C
RegistrationCan an agent get an account?
0/1
D
ProvisioningCan it get credentials without a human?
0/1
E
IntegrationCan it ship working code?
0/1

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)
  • FAIL
    llms.txt publishedNo llms.txt at any of the 3 locations probedA curated map of your docs is the cheapest way to control what an agent reads first. Worth one point and not more: in eighteen isolated agent runs across four categories, not one cited llms.txt among its sources, and an independent ninety-day measurement published by Otterly in February 2026 found it served 84 requests against 62,100 AI-bot visits.
  • UNMEASURED
    Docs readable without JavaScriptUnmeasurable: no documentation page could be found to readLink your documentation from your home page or list it in llms.txt.
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • N/A
    Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shellA markdown file written for a machine turns a guessing game into a procedure it can follow.
  • 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 surfaceNo MCP surface: nothing answered at mcp.hover.com, mcp.hover.com/mcp, mcp.hover.com/v1/mcp, api.hover.com/mcp, /mcp or /api/mcp, and no file mentions 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: the signup form at https://www.hover.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
  • FAIL
    Signup reachable without a browserhttps://www.hover.com/signup is reachable, but its form needs JavaScriptIf a bare HTTP request gets a 403, the agent never sees the form at all.

D · Provisioning

  • UNMEASURED
    Programmatic key provisioningUnmeasurable: we could not read a single documentation page, so there was nothing to look inLink your API reference from your docs index or from llms.txt and this becomes measurable.
  • FAIL
    Free tier or no-card trial stated in texthttps://hover.com/pricing answers a plain request with no price and no free-tier wording in the 942 characters it servesA 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

  • UNMEASURED
    Typed SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.hover.com, and no markdown negotiationAn OpenAPI file or markdown negotiation lets an agent read your API instead of guessing it.Point at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

What we discovered on the way

Docs
not found
Pricing
https://hover.com/pricing · guessed path
Signup
https://www.hover.com/signup · linked from the site
npm package
not found
GitHub
not found
Package licence
not found
Crawl-delay
none
Content-Signal
ai-train=yes, search=yes, ai-input=yes
Blocked on-demand agents
none