Provider · AI

Replicate — Ashlr Stack Provider

Replicate: Open-source model inference with per-second billing. API token stored in Phantom. Wire it into your project with one command via Ashlr Stack.

AI · PAT KEY-ONLY · v0.2 adds provisioning

Replicate — Open-source model inference with per-second billing. API token stored in Phantom.

Dashboard ↗

One command

Add Replicate to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add replicate

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "LLM provider for a coding assistant"

Auth flow

Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom.

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

Secret slots

stack add replicate writes these 1 secret slot into your Phantom vault:

REPLICATE_API_TOKEN

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

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?

Yes — Stack provisions Replicate on your behalf, but it authenticates as you. Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://replicate.com and paste it once.

Where does Stack store my Replicate credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (REPLICATE_API_TOKEN) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove replicate` to pull the Replicate service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Replicate credentials in their dashboard — https://replicate.com — and Stack's next `doctor --fix` will pick up the new values.