Media · wired today

Cloudinary, wired into your agent workforce

Creative assets and channels, readable without handing anyone the keys. The Cloudinary connector is one of 222 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.

Connecting Cloudinary takes one credential

You provide cloud name, API key, API secret from your Cloudinary account; Quox sends it as HTTP basic credentials. 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: Cloudinary's own API documentation ↗ covers creating and scoping the credential.

What agents can run against Cloudinary

list_resources

List uploaded Cloudinary image assets, newest first, one page at a time

usage

Get the Cloudinary account's plan and current usage: credits, storage, bandwidth, transformations and object counts

list_folders

List the root-level asset folders in the Cloudinary product environment

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

How proven is this?

This connector was blind shape-proven against the real Cloudinary API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.

Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
Read-only It ships read tools only, so there is nothing to approval-gate.
Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.

Cloudinary integration FAQ

What can Quox agents do with Cloudinary?

Agents can run 3 read-only tools against Cloudinary: list resources, usage, list folders. Every call is receipted in the evidence trail.

What does the Cloudinary integration need?

You provide cloud name, API key, API secret from your Cloudinary account; Quox sends it as HTTP basic credentials. 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 Cloudinary 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 Cloudinary connector?