Let Agents In

Agent readiness · bitmovin.com

2026-08-12 10:37 UTC · formula v9.2 · 3.3s

Your edge refuses ordinary HTTP from a data centre, agent or not.

GET https://bitmovin.com/ answered 403 to LetAgentsIn/1.0 and 403 to a Chrome user-agent. Both were refused, so this is your WAF rejecting the network we scan from rather than a rule about agents. Everything below was measured through that wall.

9/ 11

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

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

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

You 9 · category median 8.5 · best bitmovin.com 9 · 15 deterministic HTTP checks, published formula

Pass it onEmail itLinkedIn

A challenge, not a limit

Your edge answered 403 and asked the caller to run JavaScript to prove it is a browser. A person never sees it. No agent can pass it, because an agent is an HTTP client, so this is the one wall on this page that stops the funnel before any of it starts. We score it rather than excusing it as our own traffic: everything below was measured through it and is a floor, not a ceiling.

Fix this first

+1point, taking 9/11 to 10/11

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 · +1

    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.

Then, when you have room

  • Answers an agent user-agent a project · +1Your public pages answer 403 to Chrome and 403 to an agent user-agent. Exempt them from that rule and rate limit instead of refusing.

Take it with you

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

Against video hosting and streaming

You lead the 6 we have scanned in this category.

  1. 1
    bitmovin.comyou
    9/11
  2. 2
    agora.io
    9/14
  3. 3
    mux.com
    9/15
  4. 4
    livekit.com
    6/11
  5. 5
    api.video
    8/15
  6. 6
    daily.co
    8/15

Where competitors pass and bitmovin.com does not

  • Answers an agent user-agentmux.com · api.video · daily.co · livekit.com · agora.io
  • Programmatic key provisioningagora.io

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?
2/3
B
Agent entryIs there a door built for a machine?
4/4
C
RegistrationCan an agent get an account?
not measured
D
ProvisioningCan it get credentials without a human?
1/2
E
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

  • FAIL
    Answers an agent user-agentAnswered 403 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology) with a JavaScript challenge from your edge, so no agent reaches the site at allAn agent sends HTTP with its own user-agent, not a browser fingerprint. A 403 here ends the funnel before any of it starts.
  • PASS
    llms.txt publishedllms.txt present at https://developer.bitmovin.com/llms.txt, and the 12 links we sampled across the file all answer
  • PASS
    Docs readable without JavaScript15,311 characters of text without JS, on https://developer.bitmovin.com/playback/docs/managing-api-keys rather than on https://developer.bitmovin.com
  • UNMEASURED
    On-demand agents not blockedUnmeasurable: your edge answered our request for robots.txt with a refusal rather than the file, so what it permits is not something we measuredServe robots.txt to ordinary HTTP clients. Every crawler you want has to read it too.
  • UNMEASURED
    Paths robots.txt points at answerUnmeasurable: robots.txt was refused rather than absent, so nothing in it could be followedServe robots.txt to ordinary HTTP clients and this becomes measurable.
  • UNMEASURED
    No punishing crawl delayUnmeasurable: robots.txt was refused rather than absent, so any Crawl-delay in it is unreadServe robots.txt to ordinary HTTP clients and this becomes measurable.

B · Agent entry

  • PASS
    Agent entry pointFound: https://bitmovin.com/skill.md
  • PASS
    OAuth dynamic client registrationregistration_endpoint published
  • PASS
    MCP surfaceLive MCP endpoint at https://mcp.bitmovin.com/mcp, answered 401 with an auth challenge

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://bitmovin.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://bitmovin.com/signup answers 403 to an agent and 403 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

  • PART
    Programmatic key provisioning1 of 7 provisioning phrases across the 5 documents we read: "service account"Documented 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 registrybitmovin-player@8.271.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://developer.bitmovin.com/platform/docs/manage-api-keys

What we discovered on the way

Docs
https://developer.bitmovin.com · found on a subdomain
Pricing
not found
Signup
https://bitmovin.com/signup · guessed path
npm package
bitmovin-player (registry guess)
GitHub
not found
Package licence
not found
Crawl-delay
none
Content-Signal
none
Blocked on-demand agents
none