Vectara

PASS consensus from 3 PASS.

The docs root failed as JavaScript-rendered, but the direct quickstart gives one complete account-to-citations path. One page carries the whole path, get an API key, POST /v2/corpora, POST /v2/corpora/{corpus_key}/documents, POST /v2/query with generation_preset_name mockingbird-2.0, in three languages, with a sample response showing numbered citations, per-result scores, and a factual_consistency_score. The quickstart lays out four unambiguous steps with links to the REST API reference for each endpoint (POST /v2/corpora, POST /v2/corpora/:corpus_key/upload_file, POST /v2/corpora/:corpus_key/query).

FAIL consensus from 1 PARTIAL, 2 FAIL.

The docs state 10,000 trial credits but omit paid allocations, plan quotas, and general API request limits. The trial credit figure is the only number published: no paid-plan credit allowance, no per-plan storage or query quota, and no request-rate limit appears anywhere in the 552 pages listed in llms.txt, while the linked pricing page gives only annual price floors and a different set of plan names. The trial credit number is stated once and consistently (10,000), but no credit-to-operation conversion rate exists anywhere in the docs. Paid plans list only annual minimums ($100K SaaS) with no per-unit quotas. The FAQs and billing policy mention bundles without defining bundle composition.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The page recommends basic-search degradation, but its example handles only status 400 and returns 429 as a failure. The page names 429 and prescribes "Implement graceful degradation to basic search", but its only fallback code branches on e.status_code == 400 and returns a failure dict for every other status including 429, and no page states a retry interval, a Retry-After header, or whether non-reranked search carries a separate limit. The Python SDK rerankers page explicitly calls out 429 from reranking and directs agents to fall back to a basic search without reranker. The error-handling page shows how to catch ApiError by status_code. Combined, this gives a complete recovery path.

PASS consensus from 2 PASS, 1 PARTIAL.

The guide supplies the connector request, signing secret, webhook path, Slack URL check, subscriptions, and an end test. Every step exists, signing secret, app ID, the connector POST, the returned webhook_path, the Request URL, and a troubleshooting block for "Your URL didn't respond with the challenge parameter", but step 2 tells you to add message.channels, message.groups, message.im, and message.mpim as Bot Token Scopes when those are Slack event types, and the same page's troubleshooting section names the actual scopes channels:history, chat:write, and users:read. Seven-step guide covers Slack app creation, bot permissions, signing-secret retrieval, connector creation via API, webhook registration with Slack, channel invitation, and testing. Troubleshooting section addresses verification failures.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The upload index failed extraction; the quickstart lacks import time, and endpoint prose conflicts with the REST path. pip install vectara plus corpus, upload, and query examples are all present, but the query response field is called search_result in step 5, search_results in the validation script on the same page, results in that page's parameter list, and search_results with a summary field in the REST quickstart, and the page's prerequisites link to /docs/security/authentication/overview returns 404. Complete five-step quickstart with pip install, Vectara client initialization, corpus creation, document indexing, and query execution. Validation script described. SDK method signatures match the REST API endpoints.