LlamaIndex

PASS consensus from 3 PASS.

The framework landing page gives the API-key variable, pip command, local data folder, indexing call, query engine, and query call in one sequence. One linear path runs from pip install llama-index through export OPENAI_API_KEY=XXXXX, a wget that creates the sample data/ directory, and a complete copy-pasteable starter.py that indexes and queries it. The homepage quickstart section documents a single clear path from install to query in five lines.

PASS consensus from 2 PASS, 1 PARTIAL.

The docs state parsing prices and monthly credits, but the rate table covers only the v1 parse-upload route while the current guide uses v2. The Rate Limits page names the Parse upload route, its numeric limit, and its scope, and the free-tier figure of 20 requests per minute matches the plan table on the Billing page, while Pricing gives parse credit costs per tier against a stated $1.25 per 1,000 credits. Rate limits, credit costs per tier, and plan quotas are documented and consistent across the rate limits, pricing, and billing pages.

PASS consensus from 3 PASS.

The troubleshooting page names 429, directs readers to endpoint limits, prescribes jittered exponential backoff, suggests batching, and includes a status-code reference. A dedicated Troubleshooting & Error Codes page carries a 429 section, per-product error-message tables mapping exact strings to status codes and resolutions, and an HTTP status code reference, and it states the absence of a Retry-After header rather than leaving the reader to discover it. The troubleshooting page provides a dedicated 429 section referencing the rate limits page, plus an error reference table with explicit 429 messages and resolution guidance.

PASS consensus from 3 PASS.

One page documents endpoint configuration, completion events, payload and headers, raw-body HMAC-SHA256, and a Python receiver. The page covers configuration inline and by saved config ID, the full job-completion payload and header list, and runnable Python and TypeScript verifiers that use a constant-time comparison and warn against re-serializing the parsed JSON before hashing. Webhook configuration, payload structure, event types, signature verification code, and a complete FastAPI receiver example are all documented on one page.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The platform quickstart is end to end, but the generated parsing.create() example omits both source alternatives required by its own reference text. The SDK is easy to find and its quickstart runs, but the reference documents only parsing.create while the platform quickstart and every Parse example call client.parsing.parse(...), a method the Python SDK reference never lists, so the example form and the reference form disagree. The SDK reference page provides a minimal working example that matches the client and method form used across the parse getting-started pages and LlamaCloud platform documentation.