Get started

Data & AI · wired today

What can agents actually do with Qdrant?

Models and datasets are infrastructure now, and agents need eyes on them. The Qdrant connector is one of 205 executable connectors and gives agents 6 read-only tools, with the credential held in the vault and every call receipted.

The Qdrant tool list, exactly as agents see it

  • service_info — Get the Qdrant instance title, version and build commit from the service root endpoint
  • list_collections — List the names of every collection on the Qdrant instance
  • get_collection — Get one Qdrant collection's status, point counts and vector configuration by name
  • list_aliases — List every collection alias on the Qdrant instance with the collection each one points at
  • cluster_info — Get Qdrant cluster status: whether distributed mode is enabled, this peer's id, its peers and its raft state
  • telemetry — Get Qdrant instance telemetry: app name and version, collection count and cluster mode

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

What the Qdrant connector needs

You provide host, API key from your Qdrant account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: Qdrant's own API documentation ↗ covers creating and scoping the credential.

How proven is this?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Qdrant instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.

Qdrant integration FAQ

What can Quox agents do with Qdrant?

Agents can run 6 read-only tools against Qdrant: service info, list collections, get collection, list aliases, cluster info and more. Every call is receipted in the evidence trail.

What does the Qdrant integration need?

You provide host, API key from your Qdrant account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my Qdrant credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the Qdrant connector?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Qdrant instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.