Data & AI · wired today

Replicate, wired into your agent workforce

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

Connecting Replicate takes one credential

You provide API token from your Replicate 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: Replicate's own API documentation ↗ covers creating and scoping the credential.

What agents can run against Replicate

get_account

Get the Replicate account that owns this API token: username and account type. The cheap balance-free identity read and the spec's auth-proving call

list_collections

List Replicate's curated model collections (e.g. text-to-image, language-models), each with a name and slug

get_model

Get a specific public model by owner and name: description, latest version id, and total run count

list_models

List public models on Replicate, most recent first (browse the catalogue): owner, name, description, run count and latest version id

get_prediction

Poll a prediction by id for its current status and, once finished, its output and run metrics. This is the ASYNC POLL half of the submit-then-poll pattern: create_prediction (write:true) starts a job and returns an id, this tool is the zero-spend authed read that checks on it

list_predictions

List this account's recent predictions with their id, status and model, most recent first

create_prediction

Start a new prediction (run a model version against an input). This is the ASYNC SUBMIT half of the submit-then-poll pattern: it is a billable generation, so it is HITL-gated and never fired by the shape-proof harness. Poll the returned id with get_prediction once approved and started

How proven is this?

Replicate answers every unauthenticated request identically, so its endpoint paths rest on Replicate's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.

Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
Approvable Its write tools execute only after a human approves them in the inbox.
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.

Replicate integration FAQ

What can Quox agents do with Replicate?

Agents can run 7 tools against Replicate: get account, list collections, get model, list models, get prediction and more. Every call is receipted in the evidence trail.

What does the Replicate integration need?

You provide API token from your Replicate 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 Replicate 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 Replicate connector?