Test your Replicate API key.

What this key does

Replicate runs open-source models behind a uniform HTTP API. Auth is Bearer with an r8_... token. Models are referenced as owner/name; predictions are async by default with a callback / polling pattern.

How to get a Replicate API key

1. Sign in at replicate.com.
2. Open Account → API Tokens.
3. Generate a token starting with r8_.
4. Paste it here.

Common errors and fixes

• 401 Unauthorized: Key is invalid, revoked, or pasted with extra whitespace. Generate a new key from the provider console and try again.
• 403 Forbidden: Key is valid but lacks permission for this resource. Check project / org / workspace scope, or that billing is set up for this key.
• 429 Too Many Requests: You hit the per-minute or per-day rate limit. Wait a moment and retry, or upgrade your tier.
• 404 Not Found: The endpoint or model id changed. Check the provider docs for the current path and model identifier.
• 5xx: The provider is having issues. Check their status page before assuming the bug is yours.

Security best practices

• Store keys in an env var or secret manager — never commit them to a repo, even a private one.
• Restrict scope: prefer per-project or per-deployment keys over a single root key shared across services.
• Rotate on a schedule (90 days is a sane default) and immediately on suspected leak.
• Audit usage in the provider console after rotation to confirm the old key has zero traffic.
• Set per-key spend limits where the provider supports them, so a leaked key has a bounded blast radius.

Pricing at a glance

Replicate bills per second of GPU time. Different models run on different hardware tiers (T4, A40, A100, H100) with different per-second rates.