Skip to main content

Replicate

Run thousands of image, video, audio and language models hosted on Replicate.

Connect it with: API key. Replicate's own documentation: https://replicate.com/docs/reference/http.

What agents can do​

Connect Replicate so the agents working your tasks can reach it. With it connected, they can:

  • Run any public model on Replicate (image, video, speech, music, language) and fetch its output.
  • Run your own private models and deployments.
  • Check the status of a prediction and cancel one that is no longer needed.
  • Search the model catalog for a model that fits the task.

Before you start​

  • A Replicate account with billing set up; without a payment method the API is limited to a few requests per minute.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Replicate​

Jaah connects to Replicate with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

  • API token: Sign in at replicate.com, open your account menu > API tokens (replicate.com/account/api-tokens), name a new token and select Create token. It starts with r8_.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Replicate card.
  2. Name the secret and choose who can use it.
  3. Fill in API token.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Replicate with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Replicate's API once (GET https://api.replicate.com/v1/account) with the stored values, and shows who it answered as, or which value Replicate refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: api_token.

Tell the agent in your task description which secret to use, for example “use the Replicate secret org/replicate”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Replicate once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Replicate's side too, revoke or delete the key at Replicate.

Limitations​

  • Predictions are billed by Replicate per second of compute or per output; the Test only reads your account.
  • Model outputs are stored by Replicate for a limited time, so agents should save anything they need.
  • Agents can do only what the connected Replicate account allows.

Troubleshooting​

The Test says Replicate rejected the API token (401)

The token was deleted or mistyped. Create a new one under API tokens and select Replace.

Agents get 429 Too Many Requests

The account has no payment method, so it is limited to about 6 requests per minute. Add billing in your Replicate account settings.

Agents get 402 Payment Required

The account's credit is spent. Add credit or a payment method in Replicate's billing settings.

Still stuck? Select Test and read the result: it names the value Replicate refused and the status it answered.

FAQ​

Whose account pays for the predictions?

The account the token belongs to, or the organization if you created the token while working in an organization.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Replicate account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.