Data & AI · wired today

Chroma, wired into your agent workforce

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

Connecting Chroma takes one credential

You provide base URL, API key from your Chroma account; Quox sends it as a bearer token. 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: Chroma's own API documentation ↗ covers creating and scoping the credential.

What agents can run against Chroma

heartbeat

Check that the Chroma server is alive and get its nanosecond heartbeat counter

version

Get the Chroma server version string

pre_flight_checks

Get the Chroma server's client limits, including the maximum batch size it will accept

identity

Get the identity the stored credential resolves to on this Chroma server: user id, tenant and the databases it may reach

list_collections

List the collections in one Chroma tenant and database, with each collection's id, name and vector dimension

count_collections

Count the collections in one Chroma tenant and database without listing them

get_collection

Get one Chroma collection's id, name, vector dimension, metadata and configuration by name or id

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

How proven is this?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Chroma 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.

Chroma integration FAQ

What can Quox agents do with Chroma?

Agents can run 7 read-only tools against Chroma: heartbeat, version, pre flight checks, identity, list collections and more. Every call is receipted in the evidence trail.

What does the Chroma integration need?

You provide base URL, API key from your Chroma account; Quox sends it as a bearer token. 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 Chroma 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 Chroma connector?