ClickHouse

PASS consensus from 3 PASS.

The quick start covers signup, API-key login, service creation, readiness polling, HTTP querying, and a row-returning client query in one flow. One page carries signup, service creation, provisioning poll, a first query with its JSON output, and the native-client alternative, with copyable commands at every step. One page with GUI and CLI tabs, each giving a complete signup-to-query path; the CLI tab's first clickhousectl cloud service query --query SHOW databases returns rows immediately after provisioning.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The pages consistently state 1,000 concurrent queries per replica, 50 replicas per warehouse, 20 services per organization, and 10 API requests per key per 10 seconds. Service, warehouse, organization, and API rate limits are all stated with exact numbers, but a knowledge-base page gives 100000 parts per service where the usage-limits and cloud-compatibility pages both give 10k. Service, warehouse, and organization limits are documented with specific numbers, and Cloud API rate limits (100 keys/org, 10 req/10s per key) appear on a separate page. However, the cloud-tiers page states Unlimited services for every tier, contradicting the 20-soft-limit on the usage-limits page.

PASS consensus from 3 PASS.

One page identifies both triggering settings, gives diagnostic queries, provides corrective paths, warns against raising limits, and defines recovery verification. The page names both triggering settings, supplies diagnostic SQL against system.parts, gives four ordered fixes, warns against raising the limits as the primary fix, and closes with a verification step. The KB article identifies the root cause (parts_to_throw_insert / max_parts_in_total), provides diagnostic queries, gives three concrete recovery strategies (batch inserts, async inserts, partitioning key review), warns against increasing limits, and closes with a verify-recovery step.

PASS consensus from 3 PASS.

The key guide covers role-based permissions, optional IP scope, one-time credential capture, Basic authentication, and an authorized organizations request. Numbered steps run from opening the API Keys page through role scoping, IP allowlisting, and a working curl call against https://api.clickhouse.cloud/v1/organizations using HTTP Basic auth. Seven-step flow from opening the API Keys page to an authenticated curl request, including key scoping via permissions and predefined roles (developer vs admin).

PASS consensus from 3 PASS.

The Python introduction gives the full port-8443 query path and matches the HTTP docs; the guessed /get-started/quickstarts/use-clickhouse-connect route returned 404. The client page and the Cloud knowledge-base example use the same API surface, get_client(host, port=8443, username, password), command, insert, query, result_rows, so the two agree despite the knowledge-base page pinning a much older driver version. The official client is identified (pip install clickhouse-connect), and code examples show Cloud connection on port 8443 with get_client, command, insert, and query methods. Port 8443 and HTTPS match the HTTP interface docs and Cloud quick start endpoints.