Agent readiness · replicate.com
2026-08-12 10:36 UTC · formula v9.2 · 6.5s
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.
A dashed column is a stage we could not measure, not a stage you failed.
- A · Discovery
- 4/5
- B · Agent entry
- 2/2
- C · Registration
- n/m
- D · Provisioning
- 0/3
- E · Integration
- 2/2
of the 12 points that apply to you and we could measure · 5 of 17 were not scored
You 8 · category median 8 · best openrouter.ai 14 · 15 deterministic HTTP checks, published formula
Fix this first
This is the whole list: everything we could measure and you do not pass. Another 5 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.
- 1llms.txt publishedminutes · +1
Your llms.txt is already there. 1 of the 12 links we sampled are gone, starting with https://replicate.com/docs/topics/billing/index. Fix those and this passes: a map an agent follows into a 404 costs it the budget it came with.
- 2Free tier or no-card trial stated in textminutes · +1
Every mention of free on your pricing page sits inside a button. An agent reads text, not chrome, so state the tier in a sentence or a price cell: what is free, what it is limited to, and whether a card is needed.
- 3Programmatic 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.
Take it with you
4 of the checks an agent depends on, replicate.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 replicate.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.
Against model hosting and gateways
You are 3 of 7 in a category where a developer is trying to call a model you did not train without running the GPUs.
- 1openrouter.ai14/15
- 2fireworks.ai11/15
- 3replicate.comyou8/12
- 4baseten.co9/14
- 5together.ai8/13
- 6modal.com8/15
- 7groq.com7/14
Where competitors pass and replicate.com does not
- llms.txt publishedopenrouter.ai · fireworks.ai · groq.com · modal.com
- Free tier or no-card trial stated in textopenrouter.ai · fireworks.ai · modal.com · baseten.co
- Programmatic key provisioningopenrouter.ai · fireworks.ai
- Paths robots.txt points at answermodal.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
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
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- FAILllms.txt publishedllms.txt present at https://replicate.com/llms.txt and https://replicate.com/docs/llms.txt, but 1 of the 12 links we sampled across the file are gone, starting with https://replicate.com/docs/topics/billing/indexA curated map of your docs is the cheapest way to control what an agent reads first. Worth one point and not more: in eighteen isolated agent runs across four categories, not one cited llms.txt among its sources, and an independent ninety-day measurement published by Otterly in February 2026 found it served 84 requests against 62,100 AI-bot visits.
- PASSDocs readable without JavaScript43,793 characters of text without JS, on https://replicate.com/docs/reference/http rather than on https://replicate.com/docs
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- UNMEASUREDAgent entry pointUnmeasurable: 1 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.
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://mcp.replicate.com/mcp, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://replicate.com/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
- UNMEASUREDSignup reachable without a browserUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://replicate.com/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
- FAILFree tier or no-card trial stated in texthttps://replicate.com/pricing carries a "start for free" style link and nothing else about a free tier, so what we found is a button rather than a stated priceA 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
- PASSTyped SDK on the registryreplicate@1.4.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://replicate.com/docs
What we discovered on the way
- Docs
- https://replicate.com/docs · linked from the site
- Pricing
- https://replicate.com/pricing · linked from the site
- Signup
- not found
- npm package
- replicate (registry guess)
- GitHub
- replicate/replicate-javascript
- Package licence
- Apache-2.0
- Crawl-delay
- none
- Content-Signal
- search=yes, ai-train=no, ai-input=yes
- Blocked on-demand agents
- none