Run nearest-neighbor vector search in Qdrant with the universal Query API (POST /collections/{collection_name}/points/query)
domain: qdrant.tech · 8 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Auth: api-key header (required whenever the instance has a key configured, e.g. Qdrant Cloud).
POST the query vector in the query field: curl -X POST 'http://localhost:6333/collections/{collection_name}/points/query' -H 'api-key: <API_KEY>' -H 'Content-Type: application/json' -d '{"query": [0.2, 0.1, 0.9, 0.7], "limit": 3, "with_payload": true}'
Set limit explicitly if you need more than the default 10 results
Set with_payload: true (or a list of field names) — payload and vector data are missing from results by default
For multi-vector collections, add "using": "<vector_name>" to pick which named vector to search
Do NOT build new integrations against POST /points/search — it is deprecated in favor of /points/query, the unified interface for search/recommend/discover/fusion since v1.10.0
Optionally tune search with "params": {"hnsw_ef": 128, "exact": false} in the same body
Official docs: https://qdrant.tech/documentation/search/search/ ; https://api.qdrant.tech/api-reference/search/query-points
Known gotchas
/points/search, /search/batch, /search/groups, /recommend(+batch/groups), and /discover(+batch) are all deprecated (as of v1.13.3) in favor of the single /points/query endpoint — target /points/query for all new code
limit defaults to 10 if omitted — a surprise when an agent expects all matches
with_payload defaults to false, so a naive query returns id/score but no payload
query is polymorphic — raw dense vector, sparse vector object, a point ID (more-like-this), or nested objects like {"recommend": {...}} / {"fusion": "rrf"} all go through the same endpoint
Give your agent this knowledge — and 17,800+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?