A recaptcha challenge sits between an agent and an account it was ready to create.

https://cloud.typesense.org/signup loads recaptcha. There is no version of that an agent solves.

9/ 16

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

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

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

Pass it onEmail it LinkedIn

Fix this first

+4points, taking 9/16 to 13/16, past algolia.com, elastic.co

This is the whole list: everything we could measure and you do not pass. Another 1 point sits 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.
2
No CAPTCHA in the signup HTMLan afternoon · +1
Trigger recaptcha on a risk signal instead of on every signup, or open an API path to an account. A CAPTCHA is a hard stop, not a speed bump.
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.
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

7 of the checks an agent depends on, typesense.org 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 typesense.org. 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 typesense.org costs

Against search as a service

You are 4 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.co
10/14
3
meilisearch.com
9/15
4
typesense.orgyou
9/16
5
oramasearch.com
6/13
6
searchkit.co
5/13

Where competitors pass and typesense.org does not

Machine-readable API descriptionalgolia.com · meilisearch.com · elastic.co · oramasearch.com
Free tier or no-card trial stated in textalgolia.com · meilisearch.com · oramasearch.com
OAuth dynamic client registrationalgolia.com · elastic.co
MCP surfacealgolia.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?

5/5

Agent entryIs there a door built for a machine?

0/4

RegistrationCan an agent get an account?

1/2

ProvisioningCan it get credentials without a human?

2/3

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://typesense.org/llms.txt and https://typesense.org/docs/llms.txt, and the 12 links we sampled across the file all answer
PASS
Docs readable without JavaScript17,612 characters of text without JS, on https://typesense.org/docs/30.2/api/api-keys.html rather than on https://typesense.org/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.
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.typesense.org, mcp.typesense.org/mcp, mcp.typesense.org/v1/mcp, api.typesense.org/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

FAIL
No CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTMLA CAPTCHA is a hard stop. Permissions after signup beat a gate before it.
PASS
Signup reachable without a browserForm renders in server HTML at https://cloud.typesense.org/signup

D · Provisioning

PASS
Programmatic key provisioning2 of 7 provisioning phrases across the 6 documents we read: "management api", "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"
FAIL
Free tier or no-card trial stated in textNo free tier or no-card wording at https://cloud.typesense.org/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 registrytypesense@3.0.6 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://typesense.org/docs/, 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://typesense.org/docs/ · linked from the site
Pricing: https://cloud.typesense.org/pricing · linked from the site
Signup: https://cloud.typesense.org/signup · linked from the site
npm package: typesense (registry guess)
GitHub: typesense/typesense-js
Package licence: Apache-2.0
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none