Skip to main content
Explore the Krea API
Plans, capabilities, and what you can build with the API.

Creating API Keys

There are two kinds of API tokens:
  • Personal API tokens act as you: requests run under your own Krea account, with your workspace role and access to your styles. Any workspace member can create one, and a personal token stops working if you leave the workspace.
  • Service API tokens act as a separate service user in your workspace, not as the person who created them. Only workspace owners and admins can create them. Service tokens keep working if their creator leaves the workspace. Workspace owners and admins can see every token in the workspace, with 30-day spend tracked per service token.
To create an API key:
  1. Go to krea.ai/app/api/tokens
  2. Click Create Personal Token or Create Service Token
  3. Give your key a descriptive name
  4. Save the token securely — you’ll only see it once!
Personal API tokens operate as your own Krea account, so styles you’ve trained in the app are available to them directly. Service API tokens operate as a separate user identity within your workspace: styles trained in the app won’t be accessible via a service token, and styles trained via a service token won’t appear in the app, unless they are shared with the workspace. See Train a Custom Style for details.
Security Guidelines
  • Store tokens in environment variables, never in code
  • Use different tokens for development and production
  • Revoke tokens immediately if compromised
  • Never commit tokens to version control
  • Never share tokens publicly

Using API Keys

Include your token in the Authorization header of all requests:

Pricing

For per-model prices, see krea.ai/app/api/pricing ↗. Every model has a fixed per-generation price determined by your request parameters (resolution, quality, audio, duration, style references, etc.).

How API Billing Works

Direct API calls and MCP connections that use an API token draw from your workspace’s API balance — separate from the workspace’s compute unit balance used by the Krea web app. MCP connections that use OAuth are billed to the signed-in Krea account using compute units. API access must be enabled on your workspace before you can use API keys; if it isn’t, contact support@krea.ai ↗.
The Agent API and Agent tools are an exception: Agent turns use the workspace’s compute unit balance, including when authenticated with an API key. They do not use the API balance.
Failed and cancelled jobs are not billed. You only pay for completed jobs.

When your balance runs out

In-flight jobs finish normally. New API requests are rejected with HTTP 402 Payment Required:
Top up at krea.ai/app/api/ to resume. There is no public endpoint for checking your balance programmatically — monitor it in-app. That body is the API-balance 402. Zero Data Retention and other 402 responses are listed in Errors and debugging.

Adding API Balance

Add funds at krea.ai/app/api/. Only workspace owners can add API balance.
  • Preset amounts: $10, $25, $50, $100
  • Custom amount: $5 minimum, $10,000 maximum
  • Paid via Stripe Checkout; balance applies immediately on success

Tracking Usage

See the API Usage page at krea.ai/app/api/usage for completed API jobs and estimated costs over a selectable date range. Workspace managers see usage for the whole workspace; other members see usage from their own tokens. The API balance card at krea.ai/app/api/ also shows the estimated API cost for the last 7 days.

Enterprise

Higher-volume customers can be invoiced monthly on Net 30 terms instead of prepaying. Contact sales@krea.ai ↗ to discuss enterprise billing.

Next Steps

Interactive Playground

Make your first API request

Model APIs

Explore all available endpoints

Job Lifecycle

Understand job states and polling

Rate Limits

Understand API limits by plan tier