Skip to main content

Chutes API key setup

Decentralized serverless AI compute platform on the Bittensor network offering LLM inference at highly competitive rates.

Get your key

  1. Open the Chutes API keys page: chutes.ai/app/settings/api-keys
  2. Create an account and generate an API key.
  3. Paste it into the Dracon BYOK provider keys, stored encrypted (AES-256-GCM), used browser-direct, works in every Dracon tool.

Use your key in every tab

Two free extensions take the key you just set up. Both read the page you are on and use your own provider key: free, no account, nothing stored on a server we run.

SamAI

Summarize or ask about any page with your own provider key.

Add to Chrome Add to Firefox

AI Auto Form Filler

Complete a web form from a short description, using a model you bring yourself.

Add to Chrome Add to Firefox

All extensions · last checked 2026-10-22.

Get the key and test it

  1. Open the Chutes API keys page: chutes.ai/app/settings/api-keys Create a key and copy the secret straight away.
  2. Point your client at this provider's base URL: https://llm.chutes.ai/v1 It speaks the OpenAI-compatible shape, so an OpenAI SDK client works against it with no adapter: only the base URL and the key change.
  3. Prove the endpoint answers before you trust it. Send one call with no Authorization header: a live endpoint answers 401 Unauthorized, because it is waiting for a bearer key. The wording of that error differs by provider (some say invalid_api_key, others incorrect_api_key or Token is invalid), so read the 401 as the signal, not the error text.
  4. Paste the key into the Dracon BYOK provider keys ; stored encrypted, used browser-direct, no relay.
  5. Compare other provider plans when this subscription does not match your usage or budget.

Test the key

Both examples read the key from the CHUTES_API_KEY environment variable, so the key stays out of the command line.

export CHUTES_API_KEY="<YOUR_API_KEY>"

curl https://llm.chutes.ai/v1/chat/completions \
  -H "Authorization: Bearer $CHUTES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"deepseek-ai/DeepSeek-V3-0324","messages":[{"role":"user","content":"hi"}]}'
import os
from openai import OpenAI

# export CHUTES_API_KEY="<YOUR_API_KEY>" first
client = OpenAI(
    api_key=os.environ["CHUTES_API_KEY"],
    base_url="https://llm.chutes.ai/v1",
)
resp = client.chat.completions.create(
    model="deepseek-ai/DeepSeek-V3-0324",
    messages=[{"role": "user", "content": "hi"}],
)
print(resp.choices[0].message.content)

Free tier

No recurring free tier advertised as of the last check (2026-10-26). Usage is billed per the provider's listed pricing. You pay them directly, no Dracon markup.

Rate limits: Varies by model

Paid plans compared

Every tier Chutes publishes, with the price and the limit as the vendor states them, last checked 2026-10-27. Confirm with the provider before you buy. You pay them directly, no Dracon markup.

Chutes subscription plans: price, usage limit and what each tier includes.
PlanPriceUsage limitWhat you get
Pay-as-you-gono monthly feePay per token on public inference; No subscription required
  • Serverless GPU compute
  • Decentralized inference
  • Open-source models

Official plan source: chutes.ai/pricing

Connection details

Base URL
https://llm.chutes.ai/v1
API shape
OpenAI-compatible
Env var
CHUTES_API_KEY
Models
deepseek-ai/DeepSeek-V3-0324
Model lineup
Llama 3.3, Llama 4, DeepSeek V3, Qwen 2.5, Mixtral 8x7B

Our verdicts on this kind of provider

Independent comparisons we keep current as pricing and free tiers shift. A guide is setup; a verdict is whether it's worth setting up.

Add your Chutes key Add this provider to a fallback list Compare provider plans