Qdrant Cloud
Qdrant charges per cluster. Hours run, price per hour, charge and discount. Your cluster labels. Never a collection, a vector or a search.
Access
- Kind
- A read-only key you paste
- What to give
- Cloud management key
- Why that one
- A Qdrant Cloud management key that can read billing. Valistry calls the metering endpoints and nothing else: no collection, no vector, no query. The key is tested, then stored encrypted; you see its last four characters.
What it attributes on its own
- From the source
- cluster; what Qdrant charged; hours; the price per hour; your cluster labels
- Needs a rule or a trace
- queries, vectors and collections — Qdrant bills a cluster for time, not for work; tokens; team, workflow and agent, unless a cluster label carries them; outcome
The addresses it calls
- https://api.cloud.qdrant.io/api/metering/v1/accounts/
Valistry calls only these addresses. It blocks any other call and logs every call.
Connecting it
- Create a management key. Access Management → Cloud Management Keys. Create a key. Open ↗
- Copy the Account ID. Open Settings and copy the Account ID. It also follows /accounts/ in the address. Open ↗
Qdrant meters by calendar month. For part of a month, Valistry prices only the hours inside it, at Qdrant's hourly rate. Anything else is counted with no price.