Can an AI agent use Qdrant?
Qdrant is a vector database that stores and searches data by meaning.
Rank among the 246 products we drove
- Steps on its own
- tied #3
- 4/ 5
- Find to Leave, no person
- Core work done
- tied #1
- 100%
- 7 of 7 core tasks
- Time to get in
- tied #42
- 4minutes
- Getting in on its own
Yes. Our agent signed up for Qdrant on its own in a browser with a code sent to its inbox, got an API key and used its API, MCP server and CLI.
The record
Level confirmed
Not yet
Level from one drive; a second must agree.
- Got in by
- Sign-up in a browser4 minutes
- Got as far as
- Pay: reaches the checkoutA card form for $26.10 a month
Connects by
MCP, API, CLI, SDK
Agent payments
None found
On its own · 366 doc pages read
Docs it can act on: llms.txt, an OpenAPI and an MCP server.
On its own · 4 minutes
Sign-up in a browser.
On its own · 7 of 7 core tasks
Did: create a free cluster and more access keys through the API; create, fill, search, filter and delete collections and points.
Partly
Reaches the checkout. A card form for $26.10 a month.
On its own
Nothing to cancel. It deletes its account.
- On its own
- Partly
To reach L5: Pay without a person.
See how it ranks among vector databases for agents.
Own Qdrant? 9 things to fix. Get your findings, free
Checked 18 Nov 2026: MCP server answers, 5 tools, MCP tool list changed since the check before, llms.txt unchanged since the check before.
Find
How an agent connects
MCP, API, OpenAPI, CLI, SDK and llms.txt found.
MCP server
All testedOfficial server. Local server, 2 tools.
2 tools mapped in our drive
API
149 of 209 testedREST database API plus Cloud management REST/gRPC API.
209 operations mapped in our drive
OpenAPI
Yes13 unlabelled 3.1.0 files behind an HTML index.
CLI
46 of 95 testedqcloud 0.33.0, management key only.
95 commands mapped in our drive
SDK
All testedPython, TypeScript, Rust, Go, Java, .NET.
- PyPIqdrant-client
- npm@qdrant/js-client-rest
- PyPIfastembed
12 methods mapped in our drive
llms.txt
YesAgent payments
None foundReached the card form and stopped: Dedicated cluster, 1 node, 2 GiB RAM, 0.5 vCPU, 8 GiB disk (, $26.10 a month. It checks out through Stripe Checkout. An invisible bot check loaded at checkout.
Docs
Some gapsCovers getting started, auth and code examples.
Errors only mentioned in passing.
Describes each operation only in part: completeness 64 of 100.
9 of 10 documented ways to do the core work worked.
366 of 368 pages read
Changed since it was driven
Checked daily
- MCP: 1 tool added
- llms.txt: 4 links added and 9 removed
Get in
Getting in
Our agent tried 2 of 6 ways in; 1 worked without a person.
The way that worked
Sign-up in a browser4 minutes
- An inboxNeeded
- A browserNeeded
- A personNot needed
- Agent on a serverAPI, MCP, CLINoStops at sign-up: it works only in a browser.
- Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does all of the core work. Payment: reaches the checkout, a card form for $26.10 a month.
- Signed agentKnown to CloudflareYesThe sign-up page opens.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Sign-up in a browser | Worked | |
| Runs locally, no account | Not counted here | The self-hosted edition has its own level |
| Continue with GitHub | Not tried | Not part of this drive |
| Continue with Google | Not tried | Not part of this drive |
| Company single sign-on | Not tried | Needs a person's account |
| Marketplace install | Not tried | Not part of this drive |
Use
What an agent can do with Qdrant
All 7 core tasks done, and 13 of 16 others.
Core tasks
- done there
- offered, not tried
| Task | Result | Through |
|---|---|---|
| Create a collection | Done | API: done thereCLI: offered, not tried |
| Upsert points with vectors and payload | Done | API: done thereMCP: done there |
| Delete points | Done | API: done there |
| Run a vector similarity search | Done | API: done thereMCP: done there |
| Filter search results by payload conditions | Done | API: done there |
| Run hybrid, multi-stage and recommendation queries (Query API) | Done | API: done there |
| Generate vector embeddings via Inference API | Done | API: done there |
Surface audit: 325 documented operations: 214 run, 87 blocked by sandbox or plan limits and 24 left out because they spend money or reach real people. Of the 214 run, 204 passed and 10 didn't; 3 behaved differently from the docs. By surface, 149 on the API, 46 in the CLI, 12 in the SDK, 2 on the MCP server and 5 elsewhere, such as sign-in and webhooks.
Holds up
88of 100
- Reliability90
- Handles mistakes85
The mean of the two, 87.5, with a half rounded to the even number.
Docs match
88of 100
- Docs accuracy99
- Docs completeness64
Docs accuracy counts 70%, completeness 30%.
Surface tested
68of 100
204 of 301 passed: the 325 documented operations less the 24 that spend money or reach real people
What it can't do, and why
- Get the first API key without a browser The first management key is only made in the web console.
- Scale or replicate a cluster Needs a paid cluster, which needs a card.
- Pay without a card Only a Stripe card form or a cloud marketplace is offered.
- Delete the account through the API Account deletion is refused for keys; the agent did it in the console.
- Reach the hosted MCP endpoint Its host's robots.txt answered with a server error.
13 of 16 other tasks done
- Run full-text (BM25) searchDone
- List collections and read their schemaDone
- Delete a collectionDone
- Create a payload index on a fieldDone
- Create a collection snapshot for backupDone
- Restore a collection from a snapshotDone
- Set per-collection read/write access with granular JWT keysDone
- Create an API key for a clusterDone
- Migrate data from another vector database or Qdrant instanceDone
- Run raw REST calls from the Web UI consoleDone
- Monitor cluster metrics via Prometheus/GrafanaDone
- Invite a teammate to the accountDone
- Restrict cluster access by IP allowlistDone
- Configure collection shardingPartly
- Add replicas for high availabilityPaid plan
- Scale cluster compute vertically or horizontallyPaid plan
- Configure SAML SSO for the accountPaid plan
- Read the account audit logPaid plan
- Change the account's subscription tierPaid plan
- Provision clusters as infrastructure as codeNot tried
The plans they need
- Add replicaspaid (dedicated) cluster
- Scale clusterpaid (dedicated) cluster
- SAML SSOPremium
- Audit logpaid cluster
- Change tierpaid
The drive used the free plan.
Self-hosted edition
Qdrant also ships an edition you run yourself. Our agent installed it on its own server in about 0.6 minutes and drove it the same way, doing 100% of the core work.
Tips for agent builders
- Sign up at cloud.qdrant.io with an email code, then make one Cloud Management Key in Access Management; do everything else over https://api.cloud.qdrant.io with Authorization: apikey <key>.
- Find the free package with GET /api/booking/v1/accounts/{account}/packages?cloud_provider_id=aws&cloud_provider_region_id=us-east-1 (type free), then CreateCluster; one free cluster per account.
- Cloud API REST paths and bodies are in the proto google.api.http annotations at github.com/qdrant/qdrant-cloud-public-api; DeleteDatabaseApiKey needs ?cluster_id=.
- On Cloud clusters create a payload index (PUT /collections/{name}/index) before filtering or deleting by a field: strict mode refuses unindexed filters.
- Use {"text":…,"model":"sentence-transformers/all-minilm-l6-v2"} in place of a vector for free server-side embeddings; qdrant/bm25 gives sparse vectors.
- Pass --force to qcloud delete commands; without it they wait on a prompt.
Pay
Paying
Ways to pay checked 2 Nov 2026.
- ResultPartly. Reaches the checkout. A card form for $26.10 a month.
- CheckoutReached the card form and stopped: Dedicated cluster, 1 node, 2 GiB RAM, 0.5 vCPU, 8 GiB disk (, $26.10 a month. It checks out through Stripe Checkout. An invisible bot check loaded at checkout.
- TrialIt has a free plan.
Leave
Leaving
- ResultOn its own. Nothing to cancel. It deletes its account.
- Its accountYes, in a browser, without a human. The account and the user went: Settings > Delete Account, then Preferences > Delete User, in the console; the management key then got 404 on the account. DeleteAccount over the API with the management key -> 403 (user-only, interactive).
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
No sign-up page on the newest check; 17 of 17 days
llms.txt,
Found on the newest check; 17 of 17 days
MCP server (5 tools),
Answers on the newest check; 3 of 17 days
OpenAPI (Its drive found one elsewhere),
Not on its site on the newest check; 17 of 17 days
Compare
How Qdrant compares
In Vector databases
None of the 7 products we drove in Vector databases is higher; 3 others share L4. As of 2 Nov 2026.
| Product | Level | Find to leave |
|---|---|---|
| LanceDB | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Stopped, Leave: On its own. |
| Chroma | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| Pinecone | L1 | Find: On its own, Get in: Partly, Use: Not measured, Pay: Not reached, Leave: Not reached. |
| turbopuffer | L1 | Find: On its own, Get in: Stopped, Use: Not tried, Pay: Partly, Leave: Partly. |
| Qdrant (this page) | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
| Zilliz | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
| Weaviate | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
For the team behind Qdrant
Agents get stuck at Pay
9 things to fix for agents: 5 small, 3 medium and 1 large
Not every fix clears a blocker: some make a step that works easier for agents.
Agent blockers: 2 foundAgent surfaces: 5 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at qdrant.tech.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UseClear
- PayBlocks agents
- LeaveClear
Or claim Qdrant to see where each issue is and ask for a free drive after a fix.
Want Qdrant driven every month? See Watch
On our standard
Best or ahead on 3 of 22 criteria, behind on 7. Each against the products we measured on it.
- Every way in works for an agentAhead of 4 of 6 others (vector databases products), 2 the same.
- The best way in is built for agentsAhead of 4 of 6 others (vector databases products), 2 the same.
- A way in with no personTied for the best result 3 of 6 others (vector databases products) the same, 3 lower.
- Delete by API, checkedIn the middle 46 of 97 others (every product) lower, 43 the same, 8 higher.
- A request id on every answerBehind 4 of 6 others (vector databases products), 2 the same.
- Export before leavingBehind 4 of 6 others (vector databases products), 2 the same.
- Prices an agent can readBehind 5 of 6 others (vector databases products), 1 the same.
- Errors say what to do nextBehind 5 of 6 others (vector databases products), 1 the same.
All 22 criteria
- No person in the buy pathLevel with 5 of 6 others (vector databases products), 1 lower.
- Agents may read docs, API and sign-upThe same as all 4 others (vector databases products).
- A path written for agentsLevel with 4 of 6 others (vector databases products), 1 lower, 1 higher.
- Terms allow an agent's accountThe same as all 6 others (vector databases products).
- Real status codesThe same as all 6 others (vector databases products).
- An agent payment rail on the coreThe same as all 6 others (vector databases products).
- A plan an agent can buy by APIThe same as all 5 others (vector databases products).
- WebMCP tools on the web appThe same as all 6 others (vector databases products).
- Pages fit one fetchLevel with 5 of 6 others (vector databases products), 1 higher.
- llms.txt that worksLevel with 4 of 6 others (vector databases products), 2 higher.
- All validation problems at onceLevel with 33 of 57 others (every product), 24 higher.
- Errors a program can readTied for the lowest result 3 of 6 others (vector databases products) the same, 3 higher.
- Sign-in for agents acting for a personBehind 84 of 158 others (every product), 74 the same.
- Docs an agent can navigateBehind 4 of 6 others (vector databases products), 2 the same.
Where Qdrant fits
- Category
- Tasks
- Topics
- MCP serversFind step
- Docs and llms.txtFind step
- MCP sign-inGet in step
- Sign-upGet in step
- Card checkoutPay step
- Delete the accountLeave step
History
Level by drive
One drive so far, on 2 Nov 2026.
One drive so far.
Read more on this step
Pay is where our agent stopped at Qdrant.
- Finding · 18 Nov 2026How far does an AI agent get in a card checkout?Our agent reached the checkout at 88 of the 190 products it set out to buy from, and the card form at 68.Read
- Guide · 18 Nov 2026Let AI agents pay you per call: x402 and MPPx402 or MPP on a paid endpoint, your prices where agents read them, and plans an agent can buy by API or MCP.Read
- Guide · 9 Nov 2026Agent experience (AX): what it is, measured at 246 productsAs of 9 Nov 2026: Agent experience (AX) is whether an AI agent can find, get into, use and pay for a product on its own. We drove 246 products to measure it.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
Found an error? Tell us on this page or read how corrections work.
Questions people ask about Qdrant
- Can an AI agent create a Qdrant account on its own?
- Yes, in a browser, without a person. Cloud.qdrant.io/signup (Auth0): email, then a 6-digit code; no password, no CAPTCHA. Onboarding asked first and last name, account name and company name: our agent answered; the role/use-case step was skipped.
- Does Qdrant have an MCP server, and can an agent connect to it?
- Yes. Qdrant has an official MCP server. The server runs on the agent's own machine and lists 2 tools. A new agent can get in on its own: in the drive of 2 Nov 2026, our agent signed up, verified and got its key without a person. Through the MCP server, our agent tried 2 tasks and did 2.
- How does an AI agent get a Qdrant API key?
- In the drive of 2 Nov 2026, our agent got its Qdrant API key in a browser, without a person. The first Cloud Management Key is made in the console (Access Management > Cloud Management Keys > Create), as the docs say. After that, cluster keys and more management keys come from the API and CLI without a browser.
- Can an AI agent delete its Qdrant account?
- Yes, in a browser, without a human. The account and the user went: Settings > Delete Account, then Preferences > Delete User, in the console; the management key then got 404 on the account. DeleteAccount over the API with the management key -> 403 (user-only, interactive).
- Can an AI agent pay for Qdrant?
- Partly. Our agent reached a card form for $26.10 a month. It has a free plan.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “Qdrant: AI agent test drive”, 2 November 2026, https://agentdrives.com/tools/qdrant. CC BY 4.0.
AgentDrives. (2026, November 2). Qdrant: AI agent test drive. https://agentdrives.com/tools/qdrant
@misc{agentdrives_qdrant_2026,
author = {{AgentDrives}},
title = {Qdrant: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/qdrant},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
We check it against the drive and correct the page, with the date.