Agent readiness · Model hosting and gateways
replicate.com
8 of 14 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
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/index
- 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
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- 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 read
- 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 price
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
Tell me when this changes
The failures here are the kind nobody notices. 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 rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for replicate.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.