# AX Check: qdrant.tech Checked 2026-10-22. Qdrant's quickstart and pricing are usable straight out of the box. 21 of 23 checklist items passed: install commands, code examples, and pricing tiers are all readable without interaction. Only homepage Markdown support needs attention. ## Onboarding needs a login ## Coding sessions All three independent coding sessions completed and correctly identified pricing: a free tier (0.5 vCPU / 1GB RAM / 4GB disk) plus a paid tier starting around $25 per month, billed on vCPU, memory and storage usage. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/6ac7572e-9d0f-4a83-9d2d-0eba8aa40819) · [Read transcript](https://www.ax-check.com/qdrant.tech/sessions/deepseek.json) Cited the free tier (0.5 vCPU / 1GB RAM / 4GB disk) and Managed Cloud 'from $25', billed hourly on vCPU, memory, storage, backups and tokens. It noted exact rates need the calculator. Figures come from the fetched pricing page. (seq 22, seq 57, seq 59) #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained Qdrant Cloud credentials. It only checked for pre-existing env vars (none relevant found), then explicitly stated it could not create an account because signup is a browser/dashboard flow, and asked the product owner to supply a cluster URL and API key. All actual SDK operations (create_collection, upsert, query_points) ran only against the SDK's local in-process ':memory:' mode, never against a hosted endpoint. Event 8: ```text PI_GATEWAY_API_KEY= ``` Event 31: ```text QDRANT_URL not set -> using in-process ':memory:' mode for validation only Created collection 'demo_docs' (dim=4, cosine) Upserted 4 points ``` Event 59: ```text I could not execute against the **hosted** product because this environment has **no Qdrant Cloud credentials** — no `QDRANT_URL`/`QDRANT_API_KEY`, and I can't create an account (signup is a browser/dashboard flow). ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get Qdrant Cloud credentials**: Signing up for Qdrant Cloud requires a browser-based dashboard flow (login/signup pages), which an autonomous agent cannot complete without human help. This is a normal product login requirement, not a defect — Qdrant Cloud intentionally gates cluster creation behind account signup. The agent correctly identified this and stopped rather than faking success, running every operation against the local in-memory SDK mode instead of the hosted product. Event 40: ```text cloud.qdrant.io/login cloud.qdrant.io/signup ``` Event 59: ```text I could not execute against the **hosted** product because this environment has **no Qdrant Cloud credentials** — no `QDRANT_URL`/`QDRANT_API_KEY`, and I can't create an account (signup is a browser/dashboard flow). ``` #### Suggested Changes - **Publish per-resource pricing rates directly on the pricing page**: The pricing page (qdrant.tech/pricing) shows only a starting price ('from $25') and says billing is based on vCPU/memory/storage/backup/inference usage, but does not list actual per-unit rates — those require visiting the separate calculator at cloud.qdrant.io/calculator. Add a rate table or inline example calculation to the pricing page itself so developers evaluating cost do not need to jump to a calculator tool to get concrete numbers. Verify by checking that per-vCPU/per-GB dollar figures appear in the page text, not just tier names and feature checklists. Event 47: ```text price":"from 25$","priceCurrency":"USD" ``` Event 22: ```text Billing is calculated based on actual resource usage during the billing period. You're charged for compute (vCPU), memory (GB), storage (GB) consumed by your clusters, storage (GB) consumed by backups, and used inference tokens of paid models. ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/611bca9b-c084-4aa0-971a-0f1f652eca67) · [Read transcript](https://www.ax-check.com/qdrant.tech/sessions/kimi.json) Gave a $0 free tier (1 GB RAM) and about $0.014 per GB-RAM per hour paid. Named cost drivers (RAM, vCPU, disk) and region variation. Figures came from memory. (seq 25) #### End-to-end onboarding - **Onboarding needs a login**: The agent could not obtain Qdrant Cloud credentials on its own. No QDRANT_URL or QDRANT_API_KEY existed in the sandbox, and the agent correctly identified that Qdrant Cloud account creation requires interactive signup (email or OAuth) with no programmatic path. It wrote a complete example script against the hosted SDK but the script exits immediately when run because the required environment variables are unset — no authenticated operation against the real product occurred. Event 5: ```text PI_CODING_AGENT=true PI_REASONING_LEVEL=medium PI_SESSION_FILE=/sandbox/.gauge/pi/sessions/2026-10-22T22-45-51-449Z_01a165ca-cad9-74de-95fa-2d18857b0897.jsonl ``` Event 25: ```text Qdrant Cloud account creation requires interactive signup at cloud.qdrant.io (email or GitHub/Google OAuth) — there's no programmatic, credential-free way to provision a cluster or API key, and no Qdrant credentials exist in this environment. ``` Event 23: ```text Set QDRANT_URL and QDRANT_API_KEY first (see docstring). exit=1 ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to obtain Qdrant Cloud credentials**: Qdrant Cloud requires interactive signup (email or OAuth) to get a cluster URL and API key, which the agent cannot do without human involvement. This halted the actual run of the example script against the hosted product — this is a normal authentication requirement of the product, not a product defect or agent error. Event 25: ```text Qdrant Cloud account creation requires interactive signup at cloud.qdrant.io (email or GitHub/Google OAuth) — there's no programmatic, credential-free way to provision a cluster or API key, and no Qdrant credentials exist in this environment. ``` Event 23: ```text Set QDRANT_URL and QDRANT_API_KEY first (see docstring). exit=1 ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/db04dfcb-2a5a-4352-85de-c8622b0e9999) · [Read transcript](https://www.ax-check.com/qdrant.tech/sessions/qwen.json) Pricing was tied to plan assumptions: billing by provisioned node count and size, a free 1-node tier of about 0.5 vCPU and 1 GB, and roughly $25–35/month for one small paid node. The figures were flagged as unverified recollection. (seq 36) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never obtained Qdrant Cloud credentials. It checked the environment for QDRANT env vars, found none, and ran the entire example against the SDK's in-process (:memory:) mode, which is explicitly a local mock with no network calls to a hosted Qdrant instance. No account signup, API key retrieval, or authenticated request to a live Qdrant Cloud cluster occurred. Event 4: ```text env | grep -iE 'qdrant|QDRANT' ``` Event 34: ```text (no QDRANT_URL/QDRANT_API_KEY set — using in-memory mode) ``` Event 36: ```text There are **no Qdrant credentials in this environment**, so I could not connect to a live Qdrant Cloud cluster — account signup requires a human. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Qdrant Cloud credentials available for live testing**: The sandbox environment had no QDRANT_URL or QDRANT_API_KEY set, and Qdrant Cloud account creation requires human signup. This is a missing-credentials limitation of the test environment, not a product defect — the agent correctly fell back to the SDK's in-memory mode rather than attempting a local server stack, per the task's constraints. Event 4: ```text env | grep -iE 'qdrant|QDRANT' ; echo "---" ; ls -la /sandbox/repo ``` Event 36: ```text There are **no Qdrant credentials in this environment**, so I could not connect to a live Qdrant Cloud cluster — account signup requires a human. ``` - **Example script used deprecated/incorrect qdrant-client API on first run**: The initial script called client.query() and client.recreate_collection(), which failed with AttributeError and a deprecation warning under the installed qdrant-client 1.20.0. This was an agent error (writing code against an outdated API) rather than a product issue, and it was self-corrected in the next turn by switching to query_points() and create_collection()/collection_exists(). Event 25: ```text AttributeError: 'QdrantClient' object has no attribute 'query' ``` Event 25: ```text DeprecationWarning: `recreate_collection` method is deprecated and will be removed in the future. ``` #### Suggested Changes - **Surface pinned API usage examples matching the latest qdrant-client version**: The agent's first attempt at a quickstart-style script used client.query() and recreate_collection(), both invalid or deprecated in qdrant-client 1.20.0, causing a runtime crash before self-correcting to query_points(). Check by running a fresh pip install qdrant-client and confirming any first-party quickstart snippet executes without AttributeError or DeprecationWarning on the current default version. Event 25: ```text Traceback (most recent call last): File "/sandbox/repo/qdrant_example.py", line 38, in hits = client.query(collection_name=COLLECTION, query_vector=[0.15, 0.9, 0.1, 0.2], limit=3) ^^^^^^^^^^^^ AttributeError: 'QdrantClient' object has no attribute 'query' ``` ### Task given to each agent Help me build a simple example using Qdrant. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: B · 84/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown request; no Markdown representation offered. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt lists extensive docs, quickstarts, API, MCP, skills and academy links with descriptions. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt organizes content under Documentation, Academy and other headed sections with descriptive entries. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt links API Reference, Qdrant MCP Server, Agent Skills and Cloud CLI pages. ``` - **Pass** — A compact guide representation exists ```text Qdrant publishes standalone .md guides, e.g. the Edge quickstart, served as text/markdown. ``` - **Pass** — A focused guide is directly retrievable ```text Edge and FastEmbed quickstart .md pages fetch directly with concrete install and code steps. ``` - **Pass** — Equivalent instructions fit a token budget ```text Edge quickstart .md is 3186 tokens, well under 8000 and far below its HTML extraction. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text Edge quickstart gives install, config, upsert, query, filter, optimize steps with runnable Python and Rust code. ``` - **Pass** — Install and next-step links resolve ```text Fetched install and next-step links (PyPI, crates.io, docs pages) resolve successfully. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text llms.txt links Local Quickstart, Cloud Quickstart, and Edge/FastEmbed quickstarts with concrete steps. ``` - **Pass** — Installation commands are extractable ```text Install commands extractable: 'pip install fastembed', 'brew install qdrant/tap/qcloud', curl install script. ``` - **Pass** — Code examples are available without interaction ```text Quickstarts show full Python and Rust code examples inline without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text CLI quickstart states create a management API key and note account ID before use. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders tiers, limits and FAQs as static HTML without interaction. ``` - **Pass** — Prices are stated, not gated ```text Free tier, Standard usage-based, Premium minimum spend stated; support prices Free/Included/On Request. ``` - **Pass** — Pricing units and limits are explicit ```text Free tier limits 0.5 vCPU/1GB RAM/4GB disk; billing by vCPU, GB memory, storage, tokens. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Cited the free tier (0.5 vCPU / 1GB RAM / 4GB disk) and Managed Cloud 'from $25', billed hourly on vCPU, memory, storage, backups and tokens. It noted exact rates need the calculator. Figures come from the fetched pricing page. (seq 22, seq 57, seq 59) Kimi K3: Gave a $0 free tier (1 GB RAM) and about $0.014 per GB-RAM per hour paid. Named cost drivers (RAM, vCPU, disk) and region variation. Figures came from memory. (seq 25) Qwen 3.8 Max: Pricing was tied to plan assumptions: billing by provisioned node count and size, a free 1-node tier of about 0.5 vCPU and 1 GB, and roughly $25–35/month for one small paid node. The figures were flagged as unverified recollection. (seq 36) This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text api.qdrant.tech/api-reference.md serves a full REST API reference with endpoints, auth, and SDK examples. ``` - **Pass** — An MCP server is documented and well-formed ```text Official MCP server documented with tools, env vars, uvx/Docker install, and client configs. ``` - **Pass** — A CLI install path is documented ```text qcloud CLI install documented via Homebrew, install script, releases, and source. ``` - **Pass** — SDK packages resolve on their registries ```text Registry lookups for qdrant-client, @qdrant/js-client-rest, and fastembed all returned HTTP 200. ``` - **Pass** — Agent skills are published ```text Agent skills catalog documented with hub skills, npx install, and skills.qdrant.tech hosting. ``` [Full report data](https://www.ax-check.com/qdrant.tech/report.json)