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/ 14

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

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

You 10 · category median 9 · best algolia.com 10 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+2points, taking 10/14 to 12/14

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

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

Then, when you have room

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://cloud.elastic.co/registration render its form in server HTML and stop refusing non-browser requests to it.

Take it with you

4 of the checks an agent depends on, elastic.co 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 elastic.co. 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 elastic.co costs

Against search as a service

You are 2 of 6 in a category where a developer is trying to put a search box over your own data.

1
algolia.com
10/14
2
elastic.coyou
10/14
3
meilisearch.com
9/15
4
typesense.org
9/16
5
oramasearch.com
6/13
6
searchkit.co
5/13

Where competitors pass and elastic.co does not

MCP surfacealgolia.com
Signup reachable without a browsertypesense.org

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?

5/5

Agent entryIs there a door built for a machine?

1/4

RegistrationCan an agent get an account?

0/1

ProvisioningCan it get credentials without a human?

2/2

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)
PASS
llms.txt publishedllms.txt present at https://www.elastic.co/docs/llms.txt, and the 12 links we sampled across the file all answer
PASS
Docs readable without JavaScript26,821 characters of text without JS, on https://www.elastic.co/docs/reference/beats/filebeat/beats-api-keys rather than on https://www.elastic.co/docs
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.
PASS
OAuth dynamic client registrationregistration_endpoint published, and client_credentials is among the 11 advertised grants, so an unattended agent has a documented path to a token
FAIL
MCP surfaceNo MCP surface: nothing answered at mcp.elastic.co, mcp.elastic.co/mcp, mcp.elastic.co/v1/mcp, api.elastic.co/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://cloud.elastic.co/registration 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://cloud.elastic.co/registration is reachable, but its form needs JavaScriptIf a bare HTTP request gets a 403, the agent never sees the form at all.

D · Provisioning

PASS
Programmatic key provisioning2 of 7 provisioning phrases across the 5 documents we read: "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic", "service account"
UNMEASURED
Free tier or no-card trial stated in textUnmeasurable: https://www.elastic.co/pricing is larger than we read, so anything we did not find in it is a fact about our cap and not about your tiersNothing for you to do. A smaller pricing page, or one that states its tiers early, makes this measurable.

E · Integration

PASS
Typed SDK on the registry@elastic/elasticsearch@9.5.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://www.elastic.co/docs/deploy-manage/api-keys

What we discovered on the way

Docs: https://www.elastic.co/docs · linked from the site
Pricing: https://www.elastic.co/pricing · linked from the site
Signup: https://cloud.elastic.co/registration · linked from the site
npm package: @elastic/elasticsearch (registry guess)
GitHub: not found
Package licence: Apache-2.0
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none