WaveSpeed AI API Guide: Pricing, Models & Alternatives (2026)

WaveSpeed AI is a fast platform that runs AI models on demand, hosting a large catalog of third-party image, video, and audio models — Nano Banana, Wan, Seedance, and hundreds more — behind a single API. If you've used Replicate before, the shape of it will feel familiar: one account, one key, and a huge list of models you can call without setting up a separate integration for each provider.

This guide covers what's actually available through the API, real pricing, a working code example, and when a unified API like WaveSpeed AI (or an alternative to it) makes more sense than integrating providers directly.

What Is WaveSpeed AI

WaveSpeed AI positions itself as a fast hosting layer over more than a thousand AI models spanning image, video, audio, and 3D generation. Rather than building its own original AI models, it hosts models from providers like Google, Alibaba, ByteDance, and Recraft, and exposes them all through one consistent request format. You pay WaveSpeed AI directly, and it handles routing the request to whichever underlying model you asked for.

The appeal is straightforward: instead of juggling five different API keys, five different authentication schemes, and five different response formats to use five different models, you integrate once.

What Models Are Available Through the WaveSpeed AI API

Image models

The catalog includes Google's Nano Banana family (including Nano Banana 2 and Nano Banana Pro), Recraft, Flux 2, Seedream, and a long list of open-weight (publicly available model weights) and closed-source image models.

Video models

Wan 2.7 and the newer Wan 3.0 reference-to-video model, Seedance 2.0 and its faster variants, and other video generation models sit alongside the image catalog under the same API.

Utility endpoints (upscaling, face swap, background removal)

Beyond generation, WaveSpeed AI also hosts utility models for common post-processing tasks: upscaling, background removal, face swap, and similar operations, so a full pipeline doesn't require leaving the platform.

Every model gets its own model ID in the form vendor/model or vendor/model/variant, for example wavespeed-ai/z-image/turbo, and that ID is what you pass in the request URL.

WaveSpeed AI API Pricing in 2026

WaveSpeed AI uses usage-based pricing: no subscription, you top up credits and pay per generation. Each model has its own price, and the final cost for a given request depends on factors like output resolution, duration (for video), and batch size. The exact cost is shown before you submit a generation, either on the model page or by calling WaveSpeed AI's price-check endpoint programmatically.

For open-source models, WaveSpeed AI says pricing matches what the original provider charges, so you're not paying a markup for using the hosting layer. For closed-source models, pricing is set at or below the broader market average. New accounts get $1 in free trial credit to test the platform (some premium models aren't available on trial credit), and credits never expire once purchased. Bigger top-ups also raise your account's rate limits: a single top-up under $1,000 moves you from the default Bronze tier to Silver, $1,000 to $4,999 gets you Gold, and $5,000 or more gets you Ultra, each tier unlocking higher requests-per-minute throughput and limits on how many requests can run at the same time.

Because pricing is per-model rather than a flat rate, the honest comparison isn't "WaveSpeed AI vs. X" in the abstract, it's whatever specific model you're calling, priced against calling that same model somewhere else.

Authentication and Getting Started

Create a WaveSpeed AI account, generate an API key from your dashboard, and include it as a Bearer token (a type of authentication token) in every request:

Authorization: Bearer $WAVESPEED_API_KEY

All requests also need a Content-Type: application/json header. From there, submitting a task is a POST request to https://api.wavespeed.ai/api/v3/{model_id}, with a request body that varies depending on which model you're calling.

Working Code Example

Generation on WaveSpeed AI runs in the background by default: you submit a task, get a task ID back, and poll (check back for the result) until it completes. Here's a minimal example generating an image and polling until it's done.

import os
import requests
import time

api_key = os.environ["WAVESPEED_API_KEY"]
headers = {"Authorization": f"Bearer {api_key}", "Content-Type": "application/json"}

# 1. Submit the task
response = requests.post(
    "https://api.wavespeed.ai/api/v3/wavespeed-ai/z-image/turbo",
    headers=headers,
    json={
        "prompt": "a red circle centered on a white background",
        "size": "1024*1024",
    },
    timeout=(10, 60),
)
response.raise_for_status()
task = response.json()["data"]
task_id = task["id"]
print(f"Task submitted: {task_id}")

# 2. Poll for the result
result_url = f"https://api.wavespeed.ai/api/v3/predictions/{task_id}/result"
poll_interval = 2

while True:
    poll = requests.get(result_url, headers=headers, timeout=(10, 30)).json()
    data = poll["data"]
    if data["status"] == "completed":
        print("Output:", data["outputs"][0])
        break
    if data["status"] in {"failed", "cancelled", "timeout"}:
        raise RuntimeError(data.get("error") or f"Task ended with {data['status']}")
    time.sleep(poll_interval)
    poll_interval = min(10, poll_interval + 1)

Swap the model ID in the submit request for any other model on the platform, and adjust the request body to match that model's parameters (the fields differ between an image model and a video model). WaveSpeed AI also supports webhooks (a notification sent automatically to your server when the job finishes) if you'd rather not poll, and recommends waiting at least 2 seconds between checks to avoid rate limiting on the result endpoint.

WaveSpeed AI Alternatives: When to Use a Unified API Instead

WaveSpeed AI and platforms like it (Replicate is the other obvious comparison) solve a real problem: without one, you'd be maintaining separate credentials, error handling, and billing relationships for every model provider you use. But once you're already committed to that pattern, the question becomes which unified API fits your stack best.

Apiframe covers a lot of the same ground, including several models that overlap directly with WaveSpeed AI's catalog: the full Nano Banana family, Wan Image and Wan video models, and Seedance, all behind a single X-API-Key header and the same POST /v2/images/generate or /v2/videos/generate endpoint regardless of which underlying model you're calling. If you're already comparing WaveSpeed AI against alternatives, the things worth weighing are model breadth (how many of the specific models you need does each platform host), billing structure (credit-based prepaid balances on both, but check the per-model math for the specific models you'll actually use), and how webhook and polling patterns are implemented, since that affects how much integration work you'll do either way.

Neither platform is strictly better across the board. The right call usually comes down to which specific models you need and whether you're already using other services from one provider that would simplify billing.