Let Agents In

Agent readiness, measured from outside

Find out where an AI agent gets stuck on your product, before it quietly picks somebody else.

Type your domain and 15 checks run against it in half a minute, telling you which step an unattended agent dies on: finding you, reading your docs, creating an account, getting a key, or the first API call. When a developer says “add file uploads”, an agent picks the provider and writes the integration. It never files a support ticket to tell you it gave up.

Of 141 vendors we can compare today (we hold 177; the rest are waiting for a rescan), measured under formula 9.30 while the scanner runs 9.31, so a scan you run today can disagree with the row below it, 75 serve a signup form that renders nothing without JavaScript, which an agent reads as a page with no way in. Outright refusals aimed at agents are rarer than the noise around them suggests, and we say so rather than counting every 403 our data centre collects.

Your scan gets a permanent link you can forward. It is never added to the published corpus, and we do not post it anywhere.

Free. No account. Reads only what you publish.

What we found

18 / 180 / 12

Every run shipped an integration. Not one got a credential of its own where the work needed one.

Eighteen runs in isolated copies of a real application, across the four categories we have run agents in. In the three that need an account, every run stopped at the signup form and said so in its own words. In the fourth no account was needed and the barrier still appeared, earlier: a required licence key struck vendors off during dependency research, before their product was opened.

0 / 106 / 6

Whether your documentation gets read depends on the kind of decision, not on the model.

In one study the cheaper model fetched no external source in ten runs and said so: own knowledge only. In another, where the choice turned on a licence, every run fetched sources including all of the cheaper ones. A decision that cannot be answered from memory is what makes your documentation get read.

5 → 0one line of code

A provider that won five of eight greenfield runs won none of twelve against real code.

The app already had a session cookie. Adopting that provider meant running a second identity system just to upload a file, and three separate runs rejected it in almost the same words.

0 / 20considered in 19

Being rejected for the same reason nineteen times is a positioning problem, not a product one.

One provider was never selected, yet was considered and dismissed in nineteen of twenty runs, always because it assumes a framework the project did not use. One documentation chapter fixes it.

Thirty-eight runs across five studies, with the limits of each one stated. Read the method

Scanned so far

138 domains · every result is a live link

Ordered by the share of measurable points each domain earned, which is why a smaller number can sit above a larger one. These are real scans, not examples. Each vendor can open its own scorecard, reproduce every check and tell us where we are wrong. That offer is the whole point of publishing the formula. Scores are out of the points we could measure on each domain, not out of the paper maximum: a site that refuses our requests scores against a smaller denominator, not a worse number.

A score marked * comes from a domain where too much of the card was unreadable to compare it with the rest: usually the site refused us, sometimes we could not reach the pages a check needs, and either way the fault can be ours. Checks that simply do not apply, like an account on a library you install rather than sign up for, are not counted against it. Those rows sit at the bottom of their category whatever the percentage says, so that blocking the scanner cannot be a way to lead it.

  1. 1name.com
    11/15
  2. 2dynadot.com
    8/12
  3. 3dnsimple.com
    9/14
  4. 4porkbun.com
    8/13
  5. 5njal.la
    6/12

6 more in this category, all of them in the data.

  1. 1turso.tech
    13/15
  2. 2neon.com
    12/14
  3. 3planetscale.com
    13/16
  4. 4supabase.com
    13/16
  5. 5mongodb.com
    10/13

3 more in this category, all of them in the data.

  1. 1honeybadger.io
    11/14
  2. 2sentry.io
    11/15
  3. 3betterstack.com
    9/15
  4. 4rollbar.com
    8/14
  5. 5raygun.com
    8/16

2 more in this category, all of them in the data.

  1. 1launchdarkly.com
    12/15
  2. 2flagsmith.com
    11/14
  3. 3statsig.com
    10/13
  4. 4getunleash.io
    11/16
  5. 5growthbook.io
    10/15

2 more in this category, all of them in the data.

Headless CMS

median 50%
  1. 1sanity.io
    11/15
  2. 2storyblok.com
    11/15
  3. 3hygraph.com
    10/15
  4. 4strapi.io
    7/14
  5. 5directus.com
    7/16

2 more in this category, all of them in the data.

  1. 1restate.dev
    9/13
  2. 2inngest.com
    11/16
  3. 3trigger.dev
    11/16
  4. 4temporal.io
    10/15
  5. 5windmill.dev
    10/15

2 more in this category, all of them in the data.

  1. 1fireworks.ai
    14/15
  2. 2openrouter.ai
    14/15
  3. 3baseten.co
    13/14
  4. 4together.ai
    12/13
  5. 5modal.com
    9/15

2 more in this category, all of them in the data.

  1. 1mixpanel.com
    13/14
  2. 2amplitude.com
    10/14
  3. 3posthog.com
    8/13
  4. 4plausible.io
    8/14
  5. 5usefathom.com
    8/14

1 more in this category, all of them in the data.

  1. 1pinecone.io
    13/15
  2. 2trychroma.com
    11/13
  3. 3qdrant.tech
    9/12
  4. 4weaviate.io
    11/15
  5. 5turbopuffer.com
    10/16

1 more in this category, all of them in the data.

  1. 1polar.sh
    11/14
  2. 2stripe.com
    12/16
  3. 3plaid.com
    11/15
  4. 4paddle.com
    9/14
  5. 5chargebee.com
    10/16

1 more in this category, all of them in the data.

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

1 more in this category, all of them in the data.

  1. 1sinch.com
    10/13
  2. 2bird.com
    12/16
  3. 3twilio.com
    12/16
  4. 4plivo.com
    10/15
  5. 5telnyx.com
    11/17

1 more in this category, all of them in the data.

  1. 1agora.io
    11/14
  2. 2daily.co
    10/15
  3. 3mux.com
    10/15
  4. 4api.video
    8/15
  5. 5bitmovin.com
    11/11*

1 more in this category, all of them in the data.

  1. 1zenrows.com
    13/14
  2. 2browserbase.com
    14/16
  3. 3firecrawl.dev
    14/16
  4. 4apify.com
    12/15
  5. 5browserless.io
    12/16

1 more in this category, all of them in the data.

  1. 1knock.app
    12/15
  2. 2novu.co
    12/15
  3. 3onesignal.com
    12/15
  4. 4courier.com
    9/15
  5. 5magicbell.com
    8/14

1 more in this category, all of them in the data.

  1. 1nylas.com
    11/15
  2. 2savvycal.com
    9/13
  3. 3cal.com
    10/15
  4. 4calendly.com
    9/15
  5. 5cronofy.com
    8/16

1 more in this category, all of them in the data.

  1. 1radar.com
    10/14
  2. 2mapbox.com
    10/15
  3. 3maptiler.com
    10/15
  4. 4here.com
    9/14
  5. 5locationiq.com
    8/13

1 more in this category, all of them in the data.

  1. 1honeycomb.io
    13/15
  2. 2axiom.co
    12/16
  3. 3datadoghq.com
    12/16
  4. 4grafana.com
    11/16
  5. 5newrelic.com
    8/12

1 more in this category, all of them in the data.

  1. 1useanvil.com
    10/13
  2. 2docuseal.com
    9/12
  3. 3documenso.com
    9/16
  4. 4pdfmonkey.io
    7/13
  5. 5dropboxsign.com
    6/13

1 more in this category, all of them in the data.

  1. 1bigcommerce.com
    10/15
  2. 2commercetools.com
    8/12
  3. 3saleor.io
    7/13
  4. 4medusajs.com
    7/15
  5. 5swell.is
    6/13

1 more in this category, all of them in the data.

  1. 1deepl.com
    14/16
  2. 2phrase.com
    13/16
  3. 3crowdin.com
    10/15
  4. 4lokalise.com
    10/16
  5. 5tolgee.io
    8/14

1 more in this category, all of them in the data.

The five stages

Most scanners stop at whether you publish a file. The interesting failures happen further down the funnel, where an agent has already chosen you and still cannot finish.

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

What the five stages look like on one real domain

name.com 11 / 15 · current leader in domain registration and dns

  1. ADiscoveryCan an agent find and read you?
  2. BAgent entryIs there a door built for a machine?
  3. CRegistrationCan an agent get an account?
  4. DProvisioningCan it get credentials without a human?
  5. EIntegrationCan it ship working code?

Free scan

What a machine can see

15 deterministic checks across the five stages, 17 points on paper. Published formula, reproducible result, no model involved. Runs in under a minute.

You are scored out of what we could measure on your domain, not out of 17. Across the 141 domains scanned here that averages 14 points, and only 1 could be measured in full.

Your scan gets a permanent link you can forward. It is never added to the published corpus, and we do not post it anywhere.

Monitoring

When it breaks, you hear it from us

An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rerun the checks weekly and write only when a verdict moves, naming what it says now and what it said before.

Once a month a real agent is asked the question your buyers ask, five times over, and you are told how many of the five named you and which provider was picked instead. It answers a question and signs up for nothing, so nothing of yours is touched. That half covers the 26 categories we measure, and if your product is not in one of them we tell you rather than quietly skip it.

Free while we are building it, and we will ask before it ever costs anything. No account, no card, and one link in every email stops it.

Want the agent runs once rather than every month? One report, ten runs, two tools, and you keep the transcripts.

Run by Krystian Gwizdała. The scanner, the formula, the agent runs and every number on this site are mine, and an audit is run by me rather than by a team you never meet. Four audits are published in full so you can see the work before deciding whether it is worth anything to you.