Let Agents In

Agent readiness · inwx.com

2026-08-12 10:23 UTC · formula v9.2 · 6.0s

Your signup page answers 500 to anything that is not a browser.

https://inwx.com/signup returned 500 across three tries. An agent that got this far still cannot open an account.

6/ 11

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

A · Discovery
5/5
B · Agent entry
0/2
C · Registration
n/m
D · Provisioning
0/2
E · Integration
1/2

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

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

Pass it onEmail itLinkedIn

Fix this first

+3points, taking 6/11 to 9/11, past porkbun.com, dnsimple.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
    Programmatic key provisioningan afternoon · +2

    Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.

  2. 2
    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.

Take it with you

5 of the checks an agent depends on, inwx.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 inwx.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 inwx.com costs

Against domain registration and dns

You are 2 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.comyou
    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.com
    3/11

Where competitors pass and inwx.com does not

  • Machine-readable API descriptionporkbun.com · name.com · godaddy.com
  • Paths robots.txt points at answerporkbun.com · name.com
  • OAuth dynamic client registrationnamecheap.com · dynadot.com
  • MCP surfacenamecheap.com · dynadot.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?
5/5
B
Agent entryIs there a door built for a machine?
0/2
C
RegistrationCan an agent get an account?
not measured
D
ProvisioningCan it get credentials without a human?
0/2
E
IntegrationCan it ship working code?
1/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)
  • PASS
    llms.txt publishedllms.txt present at https://www.inwx.com/llms.txt, and the 12 links we sampled across the file all answer
  • PASS
    Docs readable without JavaScript5,298 characters of text without JS
  • 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

  • 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 9 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.inwx.com, mcp.inwx.com/mcp, mcp.inwx.com/v1/mcp, api.inwx.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://inwx.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.
  • UNMEASURED
    Signup reachable without a browserUnmeasurable: https://inwx.com/signup answers 500 to an agent and 500 to a Chrome user-agent, so nothing gets in from here and the difference we test for cannot be seenNothing for you to do here. It becomes measurable from a network your edge admits.

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 2 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
  • UNMEASURED
    Free tier or no-card trial stated in textUnmeasurable: no pricing page could be fetchedLink a pricing page from your home page, or list one in llms.txt.

E · Integration

  • PASS
    Typed SDK on the registrydomrobot-client@3.3.0 ships types, matched from the registry by who publishes it rather than by a link on your site
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://account.inwx.com/en/help/apidoc, 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
https://account.inwx.com/en/help/apidoc · from your llms.txt
Pricing
not found
Signup
https://inwx.com/signup · guessed path
npm package
domrobot-client (registry guess)
GitHub
not found
Package licence
not found
Crawl-delay
none
Content-Signal
none
Blocked on-demand agents
none