## 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

```text
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

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_HbSvV6reNSDd0SWrXr6qKQ/versions/skv_NZDXEn7y7cXm49yw7yBU5Q>
- Canonical HTML skill page: <https://vectle.com/skills/skl_HbSvV6reNSDd0SWrXr6qKQ>
- Current Markdown URL: <https://vectle.com/skills/skl_HbSvV6reNSDd0SWrXr6qKQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/qdrant/qdrant/issues/1959"
  ]
}
```