Inkeep

PASS consensus from 3 PASS.

The quickstart orders prerequisites, scaffolding, setup, startup, login, and the Activities Planner chat on one page. One page carries the whole path: three named prerequisites with version floors, then five numbered steps from npx @inkeep/create-agents my-agents through pnpm setup-dev, pnpm dev, login, and chatting with the Activities Planner agent, with no branch to choose. The quickstart provides a complete 5-step path from zero to chatting with the Activities Planner agent, with prerequisites, exact commands, and expected outcomes.

PASS consensus from 2 PASS, 1 PARTIAL.

Defaults are 10 transfers, 12 steps, 30-second function tools, 60-second MCP tools, and 10-minute streams; both caps are 1000. Every requested value is inline as a code comment (transfers default 10 / max 1000, generation steps default 12 / max 1000, function tool 30sec, MCP tool 1min, stream lifetime 10min) and Open Source versus Enterprise is a nine-table matrix on /pricing, but the same page prints two different names for the transfer-count variable and then tells the reader the real values live in monorepo TypeScript files it never reproduces. All limits are documented with explicit environment variable names, default values, maximum ceilings, and the configuration hierarchy for agent-specific overrides via stopWhen.

PASS consensus from 2 PASS, 1 PARTIAL.

The docs cover diagnosis and configuration changes, but they omit one complete restart and retry sequence. An "Agent Stopped Unexpectedly" section names both failure modes, gives three diagnosis steps against the Traces timeline and its clickable error cards, gives three fixes including raising the limit, and links to the exact stopWhen syntax and to per-service logs in the pnpm dev terminal. The docs cover trace inspection (SigNoz and Visual Builder), limit adjustment (stopWhen and env vars), and durable execution mode for crash recovery, though the recovery path is spread across multiple pages.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

Definition, pushing, verification, and tracking are documented, but signature formatting is missing and invocation endpoints conflict. Defining the trigger, pushing it, and reading invocation status are all fully specified, but the SDK page's webhook path and its invocations curl both disagree with the generated API reference, and the signature encoding, prefix, and signed byte range are never stated, so a valid test signature cannot be constructed from the docs. The docs cover the full webhook trigger lifecycle: create, configure signing secret, receive POST, validate payload, inspect invocation status. The HMAC verification is handled by Inkeep's framework.

PARTIAL consensus from 3 PARTIAL.

The SDK defines both entities, but a minimal local run requires combining agent, project, and CLI pages. The fact-finder tutorial builds sub-agent, agent, tool, and project registration inside the quickstart's src/projects layout and ends at inkeep push plus the Visual Builder "Try it" button, but Project Management registers the same thing under subAgents on project() while this page uses agents, and the minimal agent() example on Agents & Sub Agents omits both name and defaultSubAgent that every working example includes. The SDK example shows a complete agent and sub-agent definition, but the docs do not explicitly show how to integrate this example into the scaffolded quickstart project, the user must infer the integration path from the fact-finder tutorial and push-pull documentation.