MotherDuck

PASS consensus from 3 PASS.

The tutorial links account signup, offers direct in-page execution, and supplies a complete query against the auto-attached sample_data database. Part 1 states prerequisites, names the auto-attached sample_data database, gives the exact SQL for the NYC 311 and taxi queries, and tells a DuckDB client user to run ATTACH 'md:'; first, so no step requires guessing; the only wart is the opening line "Before playing with the dataset we just downloaded", which refers to a download that never happens on the page. The tutorial page provides the exact SQL query against the auto-attached sample_data database and gives clear connection instructions for all clients.

PASS consensus from 3 PASS.

One plan table gives compute, storage, user, and service-account quotas, while its Flight values agree with the detailed Flights table. Every limit class is stated numerically and the four pages that repeat them agree: Lite is 10 CU hours and 10 GB per month, 3 active users, 2 service accounts, Pulse only, and Flights capped at 30 minutes of compute per day with one concurrent run and a 1-hour per-run maximum, while Business is $250 per month, pay-as-you-go compute and storage, 10 active users, unlimited service accounts, all five Duckling sizes, and Flights with unlimited concurrent runs and an 8-hour per-run maximum. All plan limits are in a single comparison table with consistent categories and expand into detailed sub-sections for compute, storage, and flights.

PASS consensus from 3 PASS.

The error page identifies same-path connections with different configurations as the cause and links to exact TTL syntax for recovery. The page reproduces the error string verbatim, names the cause as MotherDuck's longer-lived database instance cache, and gives three concrete corrections (unify the configuration, set the instance TTL to zero and close prior connections, or add a session_name suffix for overlapping connections), each linked to working syntax on the connecting page; in the markdown mirror two of those three links point at /documentation/... and 404, though the rendered HTML resolves them correctly. The docs identify the error text, explain the cause (database instance cache with different config), and give three complete recovery paths with cross-references to the TTL and session_name documentation.

PASS consensus from 2 PASS, 1 PARTIAL.

The authentication and Python guides cover token creation, environment storage, database connection, and SHOW DATABASES verification. The whole path exists (create a token in the UI, export it, connect with duckdb "md:my_db", and confirm with SHOW DATABASES), but two pages must be reconciled: the authentication page says the environment variable is motherduck_token while the service accounts page says to "set MOTHERDUCK_TOKEN in your environment" with neither page stating that the name is case-insensitive, and the UI route to the token screen is given as Settings then "+ Create token" on the authentication page but as Settings > Integrations > Access Token in the tutorial. The full path is covered across two linked pages: create token in UI settings, store as environment variable or connection string parameter, then connect and confirm with a SHOW DATABASES query.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The Python landing page extraction failed, while direct guides supplied the SDK path but disagreed on whether a database name is required. The Python path itself is correct and agrees with the rest of the interface guidance (duckdb.connect('md:') or 'md:?motherduck_token=<your_access_token>', then con.sql("SHOW DATABASES").show() to verify, on a client version range that matches cloud-regions and duckdb-versions.json), but the install command an agent needs is an unrendered MDX template literal in the markdown mirror and in the getting-started llms-full.txt bundle, so only the rendered HTML page actually shows pip install duckdb==1.5.5. The Python SDK page gives the install command (pip install duckdb==1.5.5), both browser and token auth patterns, and a verification query that agrees with the general connection guidance elsewhere.