Agent readiness · Vector databases
weaviate.io
11 of 15 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)
- PASSllms.txt publishedllms.txt present at https://weaviate.io/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript37,885 characters of text without JS, on https://docs.weaviate.io/weaviate/tutorials/tokenization rather than on https://docs.weaviate.io/weaviate
- PASSOn-demand agents not blockedExplicitly allowed: ChatGPT-User
- PASSPaths robots.txt points at answerthe 1 concrete path your robots.txt allows all answer
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- PASSAgent entry pointFound: https://weaviate.io/agents.md
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceMCP mentioned 7x in your own files, but nothing answered at mcp.weaviate.io, mcp.weaviate.io/mcp, mcp.weaviate.io/v1/mcp, api.weaviate.io/mcp, /mcp or /api/mcp
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://weaviate.io/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://weaviate.io/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
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 5 documents we read: "management api"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://weaviate.io/pricing: "No credit card", "free tier", "Free Forever"
E · Integration
- PASSTyped SDK on the registryweaviate-client@3.14.0 ships types
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://docs.weaviate.io/weaviate, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
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 weaviate.io 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.