Skip to content
stack
Get started
Provider · AI

Replicate — Ashlr Stack Provider

Replicate: Open-source model inference with per-second billing. API token stored in Phantom. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

AI · PAT KEY-ONLY · supplied credential attachment
Replicate — Open-source model inference with per-second billing. API token stored in Phantom.
Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results. 

stack add replicate

Or retrieve catalog matches for what you're building via stack recommend: 

stack recommend "LLM provider for a coding assistant"

Auth flow

Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource.

How-to: Create a token at https://replicate.com/account/api-tokens.

Secret slots

stack add replicate has these 1 catalog secret slot; verify which values its adapter actually materializes through Phantom:

  • REPLICATE_API_TOKEN

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

  • OpenAI — GPT, Realtime, embeddings. Key verified against /v1/models on paste.
  • Anthropic — Claude models + MCP. Key verified against the Messages API on paste.
  • xAI — Grok + tool use. Key verified on paste.
  • DeepSeek — Open-weight models. Key verified on paste.
  • Braintrust — LLM evals + observability + prompt playground. Verified against /v1/organization on paste.

FAQ

Do I need a Replicate account to use it with Stack?

Use an existing Replicate account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource. If you don't have a credential yet, create one at https://replicate.com and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Replicate credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (REPLICATE_API_TOKEN); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove replicate` for local Replicate configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Replicate credentials through https://replicate.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.

Outbound