Qdrant Cloud: 2 reads and 4 writes, one client

Open-source vector database with rich payload filtering. Free cloud cluster, no card. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Qdrant Cloud can do here

The integration exposes 2 reads and 4 writes, each with a declared input and output schema rather than a page of documentation you would have to translate. Open-source vector database with rich payload filtering. Free cloud cluster, no card.

How it authenticates

Qdrant Cloud authenticates with a apiKey, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey and clusterUrl when we broker the call for you.

Capabilities it fulfils

Qdrant Cloud answers vector.query and vector.upsert in the vendor-neutral form, which means code asking for any of those can be pointed at Qdrant Cloud without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.

• listCollections — read: Collections in this cluster. The connection test.
• getCollection — read: One collection: its size, vector configuration and indexing state.
• upsertPoints — write: Write points. Qdrant calls a vector plus its payload a POINT.
• searchPoints — write: Find the nearest points to a query vector.
• retrievePoints — write: Fetch points by id, without a search.
• deletePoints — write: Delete points by id or by filter. IRREVERSIBLE.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.