Skip to main content
kRouter
All providers

Pay-per-token

recraft/

Recraft

Recraft — connect via API key.

recraft.ai

Quick setup

  1. Open the kRouter dashboard at http://localhost:20128

  2. Go to Providers → click Recraft

  3. Paste your API key, click Save

  4. Test the connection

Use in your IDE

Point any OpenAI-compatible client at kRouter using your local API key.

ide configbash
# Endpoint
http://localhost:20128/v1

# API key (from Dashboard → API Keys)
sk-krouter-XXXX

# Model
recraft/<model-id>

How Recraft billing works with kRouter

Recraft is pay-per-token. You bring your own API key and kRouter routes to it, so you keep your own rate limits and billing relationship. kRouter authenticates it via apikey. 2 models are routable as recraft/<model>.

Through kRouter, Recraft serves image generation, exposed on /v1/images/generations. Requests reach it through the same local OpenAI-compatible endpoint as every other provider, so switching to or from Recraft is a one-line model change in your client rather than a rewrite.

Recraft models & pricing

These are the model ids kRouter routes to. This provider does not publish per-token rates.

ModelRoute as
Recraft V3recraft/recraftv3
Recraft V2recraft/recraftv2

Recraft FAQ

Is Recraft free through kRouter?

Recraft is pay-per-token: you bring your own API key and are billed by Recraft at their rates. kRouter adds nothing on top and is free and MIT-licensed.

How do I use Recraft with Claude Code or Cursor?

Connect Recraft in the kRouter dashboard, then point your tool at kRouter's local endpoint (http://localhost:20128/v1) with a kRouter API key. Any OpenAI-compatible client works, and models are addressed as recraft/<model>.

Which Recraft models can kRouter route to?

2 models, including Recraft V3, Recraft V2. Every one is addressed as recraft/<model> from any client.

What happens when Recraft is rate limited?

kRouter detects the limit, parks that account until its real reset time, and fails over to your next connected account or provider — so the request still completes instead of erroring.