Zep

PASS consensus from 3 PASS.

The quickstart shows installation, authentication, user and thread creation, message insertion, and user_context.context retrieval in one sequence. One linear Quickstart carries a single Python path from pip install zep-cloud through Zep(api_key=API_KEY), client.user.add, client.thread.create, client.thread.add_messages, and client.thread.get_user_context, with a sample Context Block shown at the end. Quickstart provides a single-page end-to-end walkthrough from pip install through client init, user creation, thread creation, message ingestion, and context block retrieval, with working Python code at every step.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The account window is one minute; Flex lists 600 RPM and Flex Plus 1,000, while Free, Flex under load, and Enterprise vary. The window (one minute) and scope (per account) are stated, but no RPM number appears anywhere in the docs; the page defers to the marketing pricing page, which gives 600 RPM for Flex and 1,000 RPM for Flex Plus, leaves Free as "Variable rate limits, depending on service-wide load", and then qualifies that Flex numbers may be lowered. Rate limits are expressed as requests-per-minute per account with exact values for paid plans (Flex 600 RPM, Flex Plus 1000 RPM, Enterprise custom) and window/reset headers documented; Free plan is disclosed as variable.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The page documents Retry-After parsing and sleeping, but leaves the retry loop, backoff schedule, and jitter implementation unspecified. The read-wait-retry loop is fully coded in Python, TypeScript, and Go against the typed 429 error, and the header table names Retry-After as set only on 429 responses, though backoff and jitter are instructed in prose with no base delay, cap, or retry ceiling given. The basic catch-read-wait-retry loop has a code example, but combining Retry-After with exponential backoff and jitter is only mentioned as a recommendation without an implementation code example.

PASS consensus from 3 PASS.

The page covers subscription, payload fields, POST handling, raw-body Svix verification, and a five-minute timestamp check. A single page covers dashboard endpoint creation, the episode.processed field table, a Svix library verification handler, a manual HMAC-SHA256 path with the {svix-id}.{svix-timestamp}.{raw-body} signing string, the five-minute replay rejection window, and svix-id deduplication. Complete documentation covers dashboard webhook creation, endpoint configuration, the full Svix library verification flow in Python with raw body handling, plus manual HMAC-SHA256 verification steps.

PASS consensus from 2 PASS, 1 PARTIAL.

The methods match the live reference, but /sdk-reference/thread/add-messages and /sdk-reference/thread/create returned 404 while operation-ID routes loaded. The Quickstart Python calls match the SDK reference exactly on method names, argument names, and the Message role and content fields; the reference stub imports Zep from the zep_cloud root while the Quickstart imports from zep_cloud.client, and the reference stub omits the API key entirely. Quickstart examples for install, client init, message ingestion, and context retrieval match the SDK reference parameters (threadId path param, messages list, response includes context).