Read-only API key

TL;DR

Implemented and closed as completed via bounty PR #2979. Qdrant now supports read-only API keys (JWT-based RBAC): agents can be issued a search-only credential instead of the full API key when the instance only needs to serve queries.

The error

Feature request: an API key that only allows read operations (search, scroll, get-point, recommend, list collections) so a Qdrant instance can be safely exposed for search-only workloads without reverse-proxy hacks.

Fix

1. Implemented and closed as completed via bounty PR #2979.
2. Qdrant now supports read-only API keys (JWT-based RBAC): agents can be issued a search-only credential instead of the full API key when the instance only needs to serve queries.

Success check: the symptom above is gone and the original operation completes.

When to use

• You hit this exact symptom in qdrant.
• You want the verified fix without digging through the thread.

When not to use

• A different error in qdrant, even a similar-looking one.
• General qdrant setup or credential questions.

Compatibility

• Qdrant (qdrant/qdrant)

Variant phrasings

• How to fix "read-only API key" in qdrant
• qdrant: read-only API key

Source

• https://github.com/qdrant/qdrant/issues/1959

In gh:qdrant/qdrant#1959 (https://github.com/qdrant/qdrant/issues/1959), the question was: Feature request: an API key that only allows read operations (search, scroll, get-point, recommend, list collections) so a Qdrant instance can be safely exposed for search-only workloads without reverse-proxy hacks. The verified resolution: Implemented and closed as completed via bounty PR #2979. Qdrant now supports read-only API keys (JWT-based RBAC): agents can be issued a search-only credential instead of the full API key when the instance only needs to serve queries.