Connect Claude to Replicate

Read the account this token belongs to: `username`, `type` (user or organization), display name and avatar. Free - it runs no model and starts no prediction. Use it to confirm which account is about to be billed before running anything, and note that it returns no balance or spend figure, because Replicate exposes none through the API. This is the connection test for exactly those reasons: it costs nothing, creates nothing and needs no arguments.

Browse Replicate's public models, newest version first by default. Free. The answer is trimmed to the fields worth reading - owner, name, description, visibility, run count and URL - because the untrimmed record for every model carries a full `openapi_schema` and a page of them is tens of thousands of tokens an agent will not read. Call get_model once you have a candidate; that is where the input schema lives. There is no text search here: Replicate serves search as an HTTP `QUERY` request this connector cannot express, so narrow by browsing list_collections instead, or pass an `owner/name` you already know straight to get_model. Paging is Replicate's own: the raw response carries a `next` URL rather than a cursor parameter, and this connector has no way to follow it.

Read one model by owner and name. Free. This is the call worth making before create_prediction: the response carries `latest_version`, and inside it `openapi_schema`, which is the authoritative list of what that model's `input` object accepts and requires. Every model on Replicate declares its own parameters and rejects parameters belonging to another, so guessing from a similar model is how a prediction fails. `default_example` shows a real call that worked. Take `latest_version.id` from here to pin a version, or pass `owner/name` alone to create_prediction to use whatever is newest.

List the published versions of one model, newest first. Free. A version id is a 64-character hash and it is what pins a prediction to code that will not change under it - the model's owner can push a new version at any time, and a prediction that named only `owner/name` runs the new one. Read the ids here, then read one with get_model_version to see the input schema that version declares.

Read one pinned version of a model, including the `openapi_schema` describing exactly what `input` that version accepts. Free. Use it when a prediction has to be reproducible: the schema a model declares changes between versions, so a body built against the newest version can be rejected by an older one and vice versa. Pass the same version id to create_prediction.

List Replicate's curated model collections - "text-to-image", "super-resolution" and the rest - with their slugs and descriptions. Free. This is the practical way to find a model on this connector, because the text search Replicate offers is an HTTP `QUERY` request that cannot be declared here. Pick a slug and read it with get_collection.

Read one curated collection and the models in it. Free. Each entry carries owner, name, description and run count, trimmed the same way list_models is trimmed, so use get_model afterwards for the input schema of whichever one looks right. `run_count` is the most useful signal in here: a model nobody runs is usually a model that no longer works.

Check a prediction started by create_prediction and read its result. Free - polling is not billed; the compute already running is. `status` is starting, processing, succeeded, failed, canceled or aborted, and the last four are terminal. Poll about every two seconds at first and back off towards ten. A succeeded prediction carries `output`, whose shape is the model's own: a string, a URL, a list of URLs, or an object. `metrics.predict_time` is the number the per-second bill is computed from. Output file URLs are deleted an hour after the prediction was created, so download anything worth keeping rather than storing the URL. `logs` carries the model's own stderr, which is where a failure usually explains itself.

List predictions made by this account, newest first. Free. This is how to find a submission whose id was lost - a create_prediction call that timed out ambiguously should be looked for here rather than repeated, because Replicate accepts no idempotency key and a repeat is a second charge. Narrow with created_after and created_before; there is no way to page further, because Replicate returns a `next` URL rather than a cursor parameter and this connector cannot follow it. Every record carries the `input` it was given and the `output` it produced, which is why the payload is kept out of the audit log.