DEV Community: useapi.net

MiniMax H3 vs Seedance 2.0: 2K with native audio, head to head on the same omni references

useapi.net — Fri, 31 Jul 2026 05:04:22 +0000

MiniMax's newest video model, H3, is live on POST videos/create as model: "Hailuo-3.0". Two things separate it from everything else in the MiniMax lineup: every generation ships with native stereo audio — no separate voice or music pass — and it renders 2K at 24 fps by default, with the short edge at 1440 pixels (2560×1440 at 16:9, 1440×2560 at 9:16).

H3 is a general-purpose multimodal model rather than a set of task-specific modes. The same endpoint takes a prompt alone, a start frame, or a tray of image, video, and audio references, and the request shape is the one Seedance 2.0 already uses — set model, resolution, and duration directly.

The three clips below are the actual output of a single 4-second run at each mode, unedited. Turn the sound on — the audio in all three is generated by the model.

The last of the three is a direct comparison: it reuses the exact image, video, and audio references and the exact prompt from our Seedance 2.0 omni post, so H3 and the three Seedance 2.0 tiers can be judged on identical input rather than on separate demos.

Text to video

No references at all, just a prompt. aspectRatio is explicit here, though H3 defaults to 16:9 when no reference is supplied.

Aerial push over jagged sea cliffs at dawn. Waves crash white against black rock far below as mist burns off in the first gold light. A lone seabird crosses frame. Cinematic wide-angle, natural color grade. Crashing surf, wind, and distant gull calls.

Your browser does not support the video element.

The surf, wind, and gulls are all model-generated — nothing was added to the audio track.

A start frame, with speech

Supply one image as the first frame and let the prompt drive what happens next. The portrait below is the same reference used in our Seedance 2.0 omni post, so the two models can be compared on identical input.

fileID — the start frame. Upload it with POST /files first.

She looks into the camera, smiles, and says warmly: "You made it — I was starting to think you'd stood me up." Warm bar lights bokeh behind her, subtle handheld drift on the camera. Low jazz and crowd murmur sit under her voice.

Your browser does not support the video element.

Spell the spoken line out in the prompt. H3 renders the delivery from the text, so quoting the line and saying it is spoken is what puts a voice on the track.

Omni references — image, video, and audio together

The same three references from the Seedance 2.0 omni post, and the same prompt, run through H3 for a direct comparison. H3 accepts up to 9 images, 3 videos, and 3 audio clips, capped at 12 files in total, each addressed by an @-tag in the prompt.

Your browser does not support the video element.

@video1 — the scene, rope, and motion to keep. Its face is blurred on purpose: a clear real face in a video reference is rejected by the content filter, and the identity comes from @image1 anyway.

🎧 Play on useapi.net

@audio1 — the speech to drive, about 2 seconds. Together with the portrait above as @image1, that is the full tray.

Replace the woman in @video1 with @image1, keeping the same outdoor scene, rope, and jumping movements. She speaks out loud, clearly saying "Count me jumping" in the voice from @audio1, audible throughout the clip.

Your browser does not support the video element.

No aspectRatio was sent here. With references attached H3 defaults to Auto and matched the 9:16 shape of the inputs on its own.

What it costs

H3 bills 12 credits per second of output at 2K. A video reference is charged on its own length, at the same rate, on top of the generated clip — image and audio references add nothing per second.

Request	Credits
4-second clip, no references	48
4-second clip, image reference	48
4-second clip, 10-second video reference	168
15-second clip, no references	180

That surcharge is worth planning around: trim a video reference to the shortest clip that carries the motion you need, since its full length is billed whatever the output duration.

Where H3 fits

Seedance 2.0 still reaches 4K and runs cheaper per second at 480p and 720p, so it remains the better pick for volume iteration and for the highest resolution. H3 is the one to choose when you want 2K with sound in a single call — the native audio track removes an entire step from the pipeline, and 24 fps at 1440 is a materially different starting point for finishing work.

See the POST videos/create reference for every parameter, the reference-media limits, and a live Try-It console.

How to Generate AI Music with the Mureka API (Suno / Udio Alternative)

useapi.net — Mon, 27 Jul 2026 00:39:22 +0000

Introduction

Mureka AI turns a single text prompt into a complete, produced song — a direct Suno and Udio alternative — and the useapi.net Mureka API drives your own Mureka account over plain REST, with its latest V9 default and flagship O2 models, at your normal consumer subscription price. Mureka is the music generator from Chinese tech company Kunlun Tech, built on its proprietary Mureka models (mureka-9, mureka-o2). One generation returns two complete songs — vocals, melody, and arrangement — and from there you can write your own lyrics, force an instrumental, seed a track from a reference song or melody, extend a song, or clone a voice for text-to-speech. useapi.net runs all of it from one API token.

Pricing

You keep your normal Mureka web subscription for the underlying credits, plus a single flat $15/month to useapi.net that covers API access to every supported service — there is no per-song surcharge from us. Mureka's own subscription plans:

Plan	Price	Songs / month	Cost per song
Pro	$9/month	up to 500	~1.8¢
Premier	$27/month	up to 2,000	~1.35¢

Song and speech allowances are shared (songs or speech minutes), lyrics generation is free, and downloading instrumentals and stems is free. The newer V9 and O2 models consume more Gold per song, so real counts run lower — roughly 250–400 songs on V9/O2. Pro/Premier members can buy additional Gold packs (price shown at checkout).

This is the consumer-account route. Mureka also runs an official developer API, but it works differently — it is sold as prepaid top-ups with 12-month validity, consumed per call rather than billed monthly, and the ladder runs from $30 (1 concurrent request) up to $30,000 (150 concurrent), with the $1,000 tier giving 5 concurrent. Generation there runs ~$0.045/song on V8/V9/O2 (~$0.03 on the older V7.6), plus extra charges for lyrics generation and stem export. useapi.net instead automates the consumer plan you already pay for, so a $27 Premier plan plus the flat $15 covers far more generation than the official API's entry tier. For other music options under the same subscription, see the Flow Music API tutorial (Google's Lyria 3 Pro) and the TemPolor API.

Supported models

Pick a model per request with the model field on POST /music/create. Omit it and the API applies its default, V9.

Model	Engine	What it's for
`V9` (default)	`mureka-9`	Latest generation, used when `model` is omitted — advanced prompt control and studio-grade sound.
`O2`	`mureka-o2`	Flagship high-end model — best audio quality and musical coherence, with strong multilingual vocals.
`V8`	`mureka-8.0.1`	Prior-generation general-purpose model.
`V7.6`	`mureka-7.6`	Earlier model kept for compatibility — it was the default before V9.

Older aliases (V7.5, V7, O1, V6) are still accepted but redirect to current engines, so prefer the four models above. Every model returns finished MP3 audio — there is no MIDI or sheet-music output. The same account and token also drive Mureka's text-to-speech and voice cloning, covered below.

Generate a song in two API calls

You need a useapi.net API token and a connected Mureka account — export the token so the curl examples below run as-is:

export USEAPI_TOKEN="user:1234-..."

The most reliable workflow is asynchronous: the create call returns a jobid immediately, then you poll until both songs are ready.

1. Submit the job — POST https://api.useapi.net/v1/mureka/music/create:

curl -X POST "https://api.useapi.net/v1/mureka/music/create" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "account": "12345678901234",
    "prompt": "upbeat synthwave with bright female vocals about chasing a sunrise, 110 bpm",
    "model": "V9",
    "async": true
  }'

The account is your Mureka account id, and it is optional when you have a single account configured (the API auto-selects it). In async mode the response returns immediately with 201 Created, a jobid, and status: "created":

{
  "jobid": "j0622184042017475905m-u1234-a12345678901234-bot:mureka",
  "verb": "music/create",
  "jobType": "music",
  "status": "created",
  "created": "2026-06-22T18:40:42.412Z",
  "request": {
    "account": "12345678901234",
    "prompt": "upbeat synthwave with bright female vocals about chasing a sunrise, 110 bpm",
    "model": "V9",
    "async": true
  }
}

2. Poll for the result — GET https://api.useapi.net/v1/mureka/jobs/{jobid} (the jobid ends in bot:mureka, so URL-encode it in the path — it contains a :):

curl "https://api.useapi.net/v1/mureka/jobs/JOBID" \
  -H "Authorization: Bearer $USEAPI_TOKEN"

When status is completed, the finished audio lives in response.songs[]. Each generation returns two songs (an A/B pair, version "1" and "2"), and each carries an mp3_url plus cover art:

{
  "jobid": "j0622184042017475905m-u1234-a12345678901234-bot:mureka",
  "status": "completed",
  "response": {
    "feed_id": 11223344,
    "state": 3,
    "songs": [
      {
        "song_id": "user:1234-mureka:123456789-song:33445566",
        "title": "Chasing the Sunrise",
        "version": "1",
        "duration_milliseconds": 173040,
        "mp3_url": "https://static-cos.mureka.ai/cos-prod/...1.mp3",
        "cover": "https://static-cos.mureka.ai/cos-prod/...1.png"
      },
      {
        "song_id": "user:1234-mureka:123456789-song:33445567",
        "title": "Chasing the Sunrise",
        "version": "2",
        "duration_milliseconds": 178910,
        "mp3_url": "https://static-cos.mureka.ai/cos-prod/...2.mp3",
        "cover": "https://static-cos.mureka.ai/cos-prod/...2.png"
      }
    ]
  }
}

A song typically finishes in 30–90 seconds (about 45 on average), and an account supports up to 10 parallel generations. Songs can run up to about 5 minutes depending on the lyrics. Jobs are retained for 7 days, so you can re-fetch a finished result any time in that window. Prefer not to poll? Pass a replyUrl in the create body to receive a webhook callback when the job completes (the payload matches the poll response). A job can come back status: "failed" (e.g. a content-policy rejection), and the create call may return 402 (useapi.net subscription expired) / 412 (out of Mureka credits), 429 (rate limit, or all 10 generation slots busy), or 596 (account session error) — see the endpoint docs for the full list.

Write your own lyrics, or force an instrumental

The plain prompt on POST /music/create lets the model write the lyrics for you. To supply your own words, switch to POST /music/create-advanced — lyrics is required there (use [Verse] / [Chorus] tags, 50–5,000 chars), and desc steers the style with a comma-separated list of genres, moods, and vocal direction. vocal_gender forces male or female:

# Your own lyrics → forces a vocal render of those exact words
curl -X POST "https://api.useapi.net/v1/mureka/music/create-advanced" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "lyrics": "[Verse 1]\nCity lights blur in the rain\n[Chorus]\nAnd I will wait for the morning sun",
    "desc": "soulful R&B, lush keys, 90 bpm",
    "vocal_gender": "female",
    "model": "V9",
    "async": true
  }'

For a purely instrumental track, use POST /music/create-instrumental — just a prompt describing the music, no lyrics:

curl -X POST "https://api.useapi.net/v1/mureka/music/create-instrumental" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "prompt": "ethereal post-rock, cascading delay guitars, orchestral swells building to a cinematic crescendo", "model": "O2", "async": true }'

All three endpoints return the same jobid you poll on, and any resulting song_id can be lengthened with POST /music/extend (pass the song_id plus new lyrics) or reworked with POST /music/regenerate.

Reference tracks, melody seeding, and custom vocals

POST /music/create-advanced can seed a song from your own audio instead of a text description, using three reference inputs (each mutually exclusive with desc):

Parameter	Seed from	Set it up with
`ref_id`	A reference track whose style inspires the song	POST /files (upload), GET /music/refs (browse)
`motif_id`	A melody idea that kickstarts the song	POST /files/motif
`vocal_id`	A specific singing voice, including your own uploaded vocal	POST /files/vocal, GET /music/vocals

This is how you make Mureka sing your custom lyrics in a voice you supply — upload an MP3 vocal sample, take the returned id, and pass it as vocal_id alongside your lyrics. The same Pro-tier reference features (custom soundtracks and melodies) that the Mureka website offers are all reachable from the API.

Clone a voice and generate multi-speaker speech

The same account also drives Mureka's text-to-speech. POST /speech turns text into audio with either a preset or a cloned voice, and unlike music generation it has no concurrency (generation-slot) limit. Clone a voice first from an MP3 sample with POST /speech/voice, then pass the returned id as the voice_id parameter with your text:

curl -X POST "https://api.useapi.net/v1/mureka/speech" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "text": "Hello, this is a cloned voice speaking.", "voice_id": 12345, "async": true }'

For a back-and-forth dialogue, drop text/voice_id and send a conversation array instead — each turn names its own voice_id, so two or more cloned voices can talk to each other in one render:

curl -X POST "https://api.useapi.net/v1/mureka/speech" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "conversation": "[{\"voice_id\": 12345, \"text\": \"Is there anything I can help you with?\"}, {\"voice_id\": 67890, \"text\": \"Yes — read me back the weather.\"}]",
    "async": true
  }'

Speech jobs poll the same way, with the finished MP3 in response.mp3_url. See GET /speech/voices for the available voices, including the ones you have cloned.

Batch-generate with a script

Finding the right track takes many attempts, and running them by hand is tedious. The Node.js script reads a list of prompts from prompts.json, submits each one to POST /music/create in async mode, polls every job until it is done, then downloads both MP3s from each generation — so you can queue a batch and come back to a folder of finished songs.

You need Node.js v21 or newer. Put prompts.json and mureka.mjs in the same folder and run node ./mureka.mjs API_TOKEN, where API_TOKEN is your useapi.net API token. With more than one Mureka account configured, pass the account id (or its Google email) as a second argument — with a single account it is auto-selected. Each entry's prompt is required, and the optional model maps straight to the create endpoint.

Examples

These are real songs and speech generated through the Mureka API, straight from our blog walkthroughs — each from the request shapes shown above. Full prompts and curl for each are in the linked posts.

Astro Gardener — `V9`, female-vocal indie pop with custom lyrics (`create-advanced`)

🎧 Play on useapi.net

— from Mureka: V9 Now the Default Music Model

Cascading Sunrise — `V9` instrumental (`create-instrumental`)

🎧 Play on useapi.net

— from Mureka: V9 Now the Default Music Model

Galactic Odyssey — flagship `O2` instrumental (`create-instrumental`)

🎧 Play on useapi.net

— from Mureka: O2 and V7.6 Music Models

Pirate Programmer — `V7.6`, male-vocal sea-shanty-meets-electronic (`create-advanced`)

🎧 Play on useapi.net

— from Mureka: O2 and V7.6 Music Models

Custom vocal clone — an uploaded voice singing custom lyrics over a reference track (`create-advanced` with `vocal_id` + `ref_id`)

— from Mureka: Custom Vocals

Multi-speaker speech — two cloned voices in one conversation (`POST /speech`)

🎧 Play on useapi.net

— from Mureka: Speech Generation and Voice Cloning

Frequently asked questions

Is the Mureka API a Suno or Udio alternative? Yes. Like Suno and Udio, Mureka generates full songs with vocals from a single text prompt — and the useapi.net Mureka API drives your own Mureka account over plain REST, with the latest V9 default and flagship O2 models, all under one flat $15/month useapi.net subscription. See Supported models above.

Is there an official Mureka API? Yes. Mureka runs an official developer API, sold as prepaid top-ups (12-month validity) consumed per call — from $30 (1 concurrent request) up to $30,000 (150), with the $1,000 tier giving 5 concurrent. Generation runs ~$0.045/song on V8/V9/O2 (~$0.03 on V7.6), plus charges for lyrics and stems. useapi.net is the consumer-account route, automating the $9–$27/month Mureka web plan you already pay for. See Pricing above.

Which models can I use? V9 (default), the flagship O2, V8, and V7.6. Omit the model field and the API uses V9. Older aliases (V7.5, V7, O1, V6) still work but redirect to current engines. See Supported models above.

Can I write my own lyrics or generate an instrumental? Yes. Use POST /music/create-advanced with [Verse]/[Chorus]-tagged lyrics to force a vocal render of your exact words, or POST /music/create-instrumental for a lyrics-free track. See Write your own lyrics, or force an instrumental above.

Can I clone a voice or generate speech? Yes. POST /speech/voice clones a voice from an MP3 sample, then POST /speech renders text — including multi-speaker conversation dialogues — with no concurrency (generation-slot) limit. See Clone a voice and generate multi-speaker speech above.

What do I get back, and in what format? Every music generation returns two complete songs (an A/B pair), each as an mp3_url with cover art, up to about 5 minutes long. The output is finished MP3 audio — there is no MIDI or sheet-music export. See Generate a song in two API calls above.

How much does it cost? You keep your normal Mureka web plan for credits (~1.35–1.8¢ per song), plus a flat $15/month to useapi.net for API access to all services, with no per-song surcharge. See Pricing above.

How is this different from the official Mureka API? The official Mureka API is sold as prepaid top-ups (12-month validity) consumed per call, from $30 up to $30,000, charging ~$0.045/song on V8/V9/O2 (~$0.03 on V7.6) plus lyric and stem fees. useapi.net instead automates your own consumer Mureka account, so you generate at the Mureka website subscription price plus a flat $15/month — and the same one subscription covers other AI services too, including the Flow Music and TemPolor music APIs.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

The full runnable example is in the mureka-api GitHub repo.

Seedance 2.0 API Pricing: The Cheapest Ways to Run It, Compared

useapi.net — Tue, 21 Jul 2026 20:08:55 +0000

Introduction

Seedance 2.0 is the video model everyone is asking for right now, and the cheapest verified way to run its 1080p API is through useapi.net at about $1.20 a clip — below ByteDance's own official rate of $1.87 and below every third-party reseller we could verify. We pulled live pricing on July 21, 2026 from ByteDance's official channels, sixteen third-party vendors, and our own four routes, then normalized everything to one honest unit: the dollar cost of a 5-second, 1080p, text-to-video Seedance 2.0 clip.

It is worth being upfront about where we sit before the numbers. useapi.net is a bring-your-own-account layer, not an official ByteDance reseller. We drive your own PixVerse, Runway, Dreamina, or MiniMax account over a single REST API, so you spend those platforms' consumer credits instead of the metered developer-API rate. That is exactly why the numbers come out lower — and we will show the math rather than ask you to trust it. Prices move fast in this market, so every figure below carries its date, and you should re-check the source before committing spend.

What a Seedance 2.0 clip costs at the source

ByteDance sells Seedance 2.0 through two official channels — BytePlus ModelArk internationally and Volcano Engine in China. Both bill per million tokens, where a clip's token count is width × height × 24fps × seconds ÷ 1024. A 1080p second is 48,600 tokens, so a 5-second clip is 243,000 tokens at 1080p's published rate of $7.7 per million — $1.87. The per-million rate itself changes with resolution — lower at 720p, and lower still at 4K — which is why a 4K clip is not simply four times a 1080p one. Normalized, per official BytePlus rates (July 2026):

Resolution	5-second clip	10-second clip
480p	$0.35	$0.70
720p	$0.76	$1.51
1080p	$1.87	$3.74
4K	$3.89	$7.78

Seedance 2.0 Fast and Mini are cheaper but cap at 720p — there is no official 1080p or 4K on those tiers. Audio generation is included at no extra cost on the 2.0 family. Volcano runs roughly 8–13% cheaper than BytePlus at current exchange rates, but it requires Chinese real-name and face verification, so it is effectively China-only.

The sticker price is not the whole cost. Activating Seedance 2.0 on BytePlus requires a prepaid resource pack — minimum $30.10, non-refundable, expiring after 90 days — and there is no free trial for the 2.0 models. Individual accounts are throttled to 3 concurrent tasks (180 requests/minute), and 4K is capped at a single concurrent task for everyone. None of that makes the official API a bad deal. It sets the bar every alternative should be measured against.

Four ways to run Seedance 2.0 through useapi.net

One useapi.net token drives Seedance 2.0 on four different platforms, each with a different strength. All four sit under the same flat $15/month that covers every service we support, on top of the underlying account plan.

Route	Seedance models	5s 1080p	Stands out for
PixVerse	2.0, Fast, Mini	$1.20	cheapest 1080p, 4K, and real human faces
Dreamina	2.0, Fast, Mini, 1.5 Pro, 1.0 family	~$1.57 (Canada accounts)	widest model range, the only route with Seedance 1.x
MiniMax	2.0, Fast, Mini	~$1.90	4K plus a rich reference-image workflow
Runway	seedance-2, seedance-2-fast	metered	real faces with lighter moderation, plus a legacy unlimited mode

The PixVerse route is the price leader. Its cost calculator prices a 1080p Seedance 2.0 second at 60 credits, so a 5-second clip is 300 credits — $1.20 on the $60/month Premium plan at $0.004 per credit. That is the generation cost per clip. Counter-intuitively, the Premium plan beats the pricier Ultra plan for single clips, because Ultra's 40%-off third-party discount is outweighed by its worse per-credit rate. PixVerse also reaches 2160p (4K) on Seedance 2.0, at about $2.40 for a 5-second clip — below both MiniMax's 4K and the official rate. It handles real human faces too, one of the reference workflows the official API restricts (more on that below).

The Runway route earns its place on real faces, not price. It generates Seedance 2.0 at up to 1080p on metered credits, with notably lighter moderation of real people than the other routes. It also carries a legacy unlimited mode — on older Runway Unlimited plan accounts that already have Explore mode enabled, exploreMode runs Seedance at 480p and 720p without spending credits. Runway no longer enables Explore mode on new accounts, though, and where it does run it is slow — one clip at a time, roughly 10 to 15 minutes each. Treat it as a perk if you already have it, not a reason to pick Runway.

The trade-offs are real and worth naming. Our routes automate consumer accounts, so concurrency is account-bound (typically 5–10 parallel jobs, versus the official API's per-key limits), Dreamina's 1080p and 4K are locked to Canada-region accounts, and Runway's unlimited Explore mode is a legacy perk that new accounts can no longer enable. What you get in return is a materially lower per-clip cost and one token across all four platforms.

The real-faces gap

Price is not the only place the official API is restrictive. Seedance 2.0 rejects reference images and videos that contain real human faces, unless the face comes from the model's own recent output, a preset digital character, or a verified real-person asset. Doing real-person reference work at any scale means ByteDance's enterprise "Advanced Creation Rights" — $14,000 a year for a million assets, $42,000 for five million, corporate verification required.

Three of our routes soften this. The PixVerse route accepts real human faces, the Runway route documents real-face support with notably lighter content moderation, and the MiniMax route accepts real faces in image references (video references with recognizable faces are still moderated). For advertising, UGC, and creator workflows that revolve around a real person, that difference matters more than a few cents per clip — and it does not require the official API's enterprise contract.

The wider market, priced honestly

Most third-party Seedance vendors are reselling ByteDance's own API with a margin on top, and the honest ones cluster at 20–60% above official. A few reference points, priced live in July 2026 for a 5-second 1080p clip:

Vendor	5s 1080p	Notes
useapi.net (PixVerse route)	$1.20	consumer-account credits
Segmind	$1.70	the only reseller we verified below official
Official BytePlus	$1.87	the yardstick
Replicate	$2.25	"Official" model badge, transparent per-second pricing
fal.ai	$3.41	the market's default, and the most expensive standard 2.0 we found

That last row is worth sitting with. fal.ai is where a lot of developers reach for Seedance first, and at $14 per million tokens it charges more than 1.8× ByteDance's own $7.7 — an ~82% premium for the same model.

You will also see sticker prices that look far lower than official. Every one we chased down decomposed into something other than a cheaper Seedance 2.0. A few patterns to watch for when a price looks too good:

Flat per-second rates that hide a cross-subsidy — a single "$0.11/second at any resolution" number is cheap at 1080p but quietly more expensive than official at 480p, and it usually leans on venture subsidy that will not last.
"Turbo" or "accelerated" variants that are not the standard model — one vendor advertises a 1080p clip at $0.75 under a model name ByteDance does not publish, while its actual standard Seedance 2.0 costs four times that on the same site.
Prices quoted at 720p when you wanted 1080p — several "cheapest Seedance" pages have no 1080p tier at all, so the low number is a 720p rate, and a homepage claim of "30–70% cheaper" turns into roughly 9% more than official once you match resolutions.
"Unlimited" plans capped below 1080p — an unlimited tier that only reaches 720p, runs on a slow queue, and expires in a fixed window is a different product than an unlimited 1080p API.
Credits with no published dollar value — if a page prices generations in credits but never tells you what a credit costs, you cannot compare it, and that is usually the point.

None of this means those vendors are dishonest — it means resolution, model variant, and fine print have to match before a comparison means anything. When they do, the verified market has no one meaningfully below official except Segmind at a thin margin, and our PixVerse route beneath that.

Show me the API call

Every price above is one REST call away. Generate a 1080p Seedance 2.0 clip through the PixVerse route:

curl --location 'https://api.useapi.net/v2/pixverse/videos/create' \
--header 'Authorization: Bearer user:12345-…' \
--form 'model="seedance-2.0"' \
--form 'prompt="A lone lighthouse on a storm-battered cliff at dusk, waves exploding against the rocks, beam sweeping through the rain, cinematic wide shot."' \
--form 'quality="1080p"' \
--form 'duration="5"' \
--form 'aspect_ratio="16:9"'

Or, if your Runway account already has Explore mode enabled — Runway no longer offers it on new accounts — the same shape runs unlimited at 720p by adding exploreMode, one slow clip at a time:

curl --location 'https://api.useapi.net/v1/runwayml/videos/create' \
--header 'Authorization: Bearer user:12345-…' \
--form 'model="seedance-2"' \
--form 'text_prompt="A lone lighthouse on a storm-battered cliff at dusk, waves exploding against the rocks, beam sweeping through the rain, cinematic wide shot."' \
--form 'resolution="720p"' \
--form 'duration="5"' \
--form 'exploreMode="true"'

Both return a job id to poll (or a replyUrl webhook when the clip is ready). The full parameter set — reference images, first and last frames, aspect ratios, and audio — lives on each endpoint page linked in the table above.

Which route should you use for Seedance 2.0?

Cheapest 1080p, or you need 2160p — the PixVerse route, at $1.20 for a 5-second 1080p clip.
Real human faces — the PixVerse, MiniMax, or Runway route, which avoid the official API's enterprise-gated face restriction.
Widest model choice, or you specifically want Seedance 1.5 Pro / 1.0 — the Dreamina route, the only one carrying the 1.x family.
4K with a deep reference-image workflow — the MiniMax route, or PixVerse for 4K at the lower price.

Examples

Real Seedance 2.0 output from each route, reused from our blog posts — the same model, run on different platforms. Three of these lean on real human faces, the workflow the official API gates behind an enterprise contract.

PixVerse · Seedance 2.0 (Standard), 1080p — a real face from a photo dropped into reference footage and given speech from a reference audio clip, all in one omni request. From PixVerse Seedance 2.0: Mini vs Fast vs Standard.

Your browser does not support the video element.

MiniMax · Seedance 2.0 (Standard), 1080p — the same real-face omni workflow on the MiniMax route. From MiniMax Seedance 2.0: Standard vs Fast vs Mini.

Your browser does not support the video element.

Runway · Seedance 2.0, 15 seconds, 9:16 — a real face animated on the Runway route, which applies lighter moderation on real people. From Seedance 2.0: Using Real Faces.

Your browser does not support the video element.

Dreamina · Seedance 2.0, text-to-video with lip-sync from a prompt alone. From Dreamina: Seedance 2.0 Video Generation.

Your browser does not support the video element.

FAQ

Is useapi.net an official Seedance API? No. useapi.net is a REST layer that automates your own PixVerse, Runway, Dreamina, or MiniMax account, each of which runs Seedance 2.0. You spend those platforms' consumer credits rather than ByteDance's metered developer-API rate, which is why the per-clip cost comes out lower.

What is the cheapest way to run Seedance 2.0 at 1080p? Of everything we verified in July 2026, the PixVerse route at about $1.20 per 5-second clip, below ByteDance's official $1.87 and below every third-party reseller. See the pricing table.

Can I generate Seedance 2.0 videos with real human faces? The official API restricts real-face reference inputs to verified assets or an enterprise contract starting at $14,000 a year. The PixVerse and MiniMax routes accept real faces (MiniMax in image references), and the Runway route documents real-face support with notably lighter moderation.

How does useapi.net charge less than ByteDance's own API? The official developer API meters by token for scale customers. Consumer plans on PixVerse, Runway, Dreamina, and MiniMax price the same generation lower because they are sold to creators. useapi.net automates one of those consumer accounts over REST, so you get the consumer rate through an API, plus a flat $15/month across every service.

Are the sub-dollar Seedance prices I see elsewhere real? Usually not for a standard 1080p Seedance 2.0 clip. They tend to be 720p rates, subsidized flat-rate plans, distilled "turbo" variants, or credits with no published dollar value — see the wider market section.

Ready to try it? Pick a route — PixVerse for the cheapest 1080p and real faces, MiniMax for 4K with a reference workflow — connect the account, and a useapi.net subscription drives all four with one token. Prices in this article were current on July 21, 2026, and this market moves quickly, so confirm the live rate before you scale.

AI Music APIs Compared: Mureka vs MiniMax vs ElevenLabs vs Lyria 3 Pro

useapi.net — Fri, 17 Jul 2026 03:10:32 +0000

Introduction

We gave the same briefs to five AI music models — Mureka O2, Mureka V9, MiniMax music-2.6, ElevenLabs music-v1, and Google's Lyria 3 Pro — through useapi.net, and published every result: 30 full tracks below, with real prices, generation times, and the quirks we hit along the way. Three test formats, two rounds each: pure instrumentals, vocals where the model writes its own lyrics, and vocals singing lyrics we wrote. Every model in a round gets the identical brief, so what you hear is the model, not the prompt.

The five models arrive through three services — Mureka directly (the strongest Suno and Udio alternative in the group), MiniMax and ElevenLabs through PixVerse, and Lyria 3 Pro through Flow Music. One useapi.net token drives all three. If you want the copy-paste quick starts instead of a listening test, see the Mureka tutorial and the Flow Music tutorial.

Short on time? The whole test is also a 15-minute YouTube video — a skimmable cut with every track's best 30 seconds back to back, loudness-matched, with the prompt, model, cost, and generation time on screen. The full-length tracks and the exact API call behind each one live on this page.

The lineup and what a track costs

Model	useapi.net API	Cost per track	Official API
Mureka O2	Mureka API	$0.0135	Official Mureka API starts at $1,000/month at 3¢/song
Mureka V9	Mureka API	$0.0135	same as above
MiniMax music-2.6	PixVerse API	$0.16	~$0.15/track up to 5 min
ElevenLabs music-v1	PixVerse API	$0.60	$0.15/min, about $0.75 for 5 min
Lyria 3 Pro	Flow Music API	~$0.008–0.013	$0.08/song on Google's official API

Per-track figures are what the underlying account plan works out to — Mureka Premier at $27/month for 2,000 songs, PixVerse credits at $0.004 each on the $60/month Premium plan, Flow Music paid plans. On top of the account you pay useapi.net's flat $15/month for API access to every supported service, with no per-generation surcharge. The standouts are at the extremes: Lyria through Flow Music runs six to ten times cheaper than Google's own API for the same model, and Mureka through useapi.net is about half the official per-song rate with no $1,000/month floor. For ElevenLabs the PixVerse route is about running everything through one account rather than price — at the one-minute tracks it likes to produce, the official API is cheaper.

One playback note before you listen: Flow Music offers a lossless WAV alongside its m4a, so the Lyria players below are WAVs — the rest are the mp3s their APIs return.

How we tested

Every prompt asked for "around 60 seconds" (spoiler: only one model listened — see what we learned). Generation times are wall-clock through the API, polled at 15-second intervals, so treat them as ballpark. Where a model titles its own output we kept the title. Tracks are complete and unedited.

Part 1 — Instrumentals

Round 1: big-band noir

A retro secret-agent groove — walking bass, stabbing brass, surf-twang guitar. Rhythm feel and section writing are hard to fake:

Big-band noir action theme, around 60 seconds. Walking upright-bass and
baritone-sax groove, snapping rimshot snare, stabbing trumpet-section hits,
vibraphone glints, surf-twang guitar riff over a chromatic minor progression,
roaring full-brass climax with crash cymbals. Retro secret-agent swagger,
punchy analog-style production.

Mureka O2 — “The Dead Drop” · 3:19 · generated in 119 s

🎧 Play on useapi.net

Mureka V9 — “Dead End Alley” · 3:28 · generated in 85 s

🎧 Play on useapi.net

MiniMax music-2.6 · 2:11 · generated in 99 s

🎧 Play on useapi.net

ElevenLabs music-v1 · 1:00 · generated in 16 s

🎧 Play on useapi.net

Lyria 3 Pro — “The Shadow Trail” · 2:59 · generated in 34 s

🎧 Play on useapi.net

Note the lengths: same brief, same "around 60 seconds" request — ElevenLabs delivered exactly 1:00, everyone else played on.

Round 2: liquid drum and bass

Maximum contrast with round 1 — a steady 174 BPM groove exposes rhythm programming and texture instead of dynamics:

Liquid drum and bass instrumental, around 60 seconds. Fast rolling breakbeats
at 174 BPM, deep warm sub-bass, lush atmospheric pads, delicate piano motif,
airy wordless vocal-chop textures, smooth builds into a euphoric flowing drop.
Silky, melodic, late-night energy, pristine modern production.

Mureka O2 — “Silver Lining” · 3:19 · generated in 86 s

🎧 Play on useapi.net

Mureka V9 — “Silken Motif” · 2:31 · generated in 67 s

🎧 Play on useapi.net

MiniMax music-2.6 · 2:22 · generated in 119 s

🎧 Play on useapi.net

ElevenLabs music-v1 · 1:00 · generated in 16 s

🎧 Play on useapi.net

Lyria 3 Pro — “Silky Liquid Flow” · 2:54 · generated in 50 s

🎧 Play on useapi.net

Part 2 — Vocals, model writes the lyrics

Round 3: pop duet

One sentence of direction, and a deliberate capability probe — a duet only works if the model can stage two voices. That is the thing to listen for in this round, and it is the clearest differentiator of the six.

A playful pop duet between a male and a female singer about texting too late
at night, around 60 seconds, catchy back-and-forth chorus.

Mureka O2 — “Don’t Hit Send” · 3:18 · generated in 80 s

🎧 Play on useapi.net

Mureka V9 — “Midnight Dance” · 2:53 · generated in 62 s

🎧 Play on useapi.net

MiniMax music-2.6 · 2:40 · generated in 97 s

🎧 Play on useapi.net

ElevenLabs music-v1 · 1:00 · generated in 16 s

🎧 Play on useapi.net

Lyria 3 Pro — “Don’t Say Goodnight” · 2:58 · generated in 79 s

🎧 Play on useapi.net

Round 4: Spanish flamenco-pop

The language probe — the prompt is English, the song should not be:

A fiery flamenco-pop song in Spanish about summer rain, around 60 seconds,
passionate female vocals.

Mureka O2 — “El llanto del sol” · 3:59 · generated in 79 s

🎧 Play on useapi.net

Mureka V9 — “Lluvia de Verano” · 2:32 · generated in 63 s

🎧 Play on useapi.net

MiniMax music-2.6 · 2:57 · generated in 113 s

🎧 Play on useapi.net

ElevenLabs music-v1 · 1:00 · generated in 17 s

🎧 Play on useapi.net

Lyria 3 Pro — “Tierra Mojada” · 2:34 · generated in 64 s

🎧 Play on useapi.net

All five accepted the brief and every model sang in Spanish. Lyria even wrote a full Spanish lyric sheet ("Cae el peso del cielo gris / Sobre el polvo de este jardín…") and titled the track accordingly, as did both Murekas.

Part 3 — Vocals, our lyrics and an elaborate style brief

For the final format each model received the same original lyrics plus a detailed production brief. Mureka takes these through music/create-advanced (lyrics + a comma-separated style desc + vocal_gender), PixVerse and Flow Music take a lyrics field next to the style prompt.

Round 5: deep house

[Verse]
Two shadows in a velvet room
Moving slow to a midnight tune
Say it soft, we do not need more
The bass is talking through the floor

[Chorus]
Keep it low light, low light, hold me near
All we need is the bassline here
Round and round till the morning shows
Low light, low light, do not let go
(do not let go, do not let go)

Deep house at 121 BPM. Rolling sub-bass groove, shuffled hi-hats, warm Rhodes
chord stabs, subtle chopped vocal echoes, smoky intimate female lead vocal,
understated hypnotic late-night club production.

Mureka O2 — “Low Light” · 3:13 · generated in 60 s

🎧 Play on useapi.net

Mureka V9 — “Low Light” · 2:39 · generated in 57 s

🎧 Play on useapi.net

MiniMax music-2.6 · 1:06 · generated in 59 s

🎧 Play on useapi.net

ElevenLabs music-v1 · 0:40 · generated in 29 s

🎧 Play on useapi.net

Lyria 3 Pro — “Low Light (Take 2)” · 2:32 · generated in 44 s

🎧 Play on useapi.net

Round 6: jazzy house duet

The hardest brief of the set — a two-voice arrangement with live-jazz layers over a house groove, voice roles tagged in the lyrics. The tags are a hint, not an API parameter, so listen for who actually trades verses between a male and a female voice and who flattens it into one singer:

[Verse 1 - male]
Blue hour settles on the avenue
Trumpet smoke and a table for two
I talk in rhythm, you answer in rhyme
We swing together on borrowed time

[Verse 2 - female]
You bring the thunder of a double bass
I bring the shimmer of a satin dress
Piano is asking what the night is about
We are the answer when the lights go out

[Chorus - both]
Meet me in the blue hour, where the bass goes slow (blue hour, blue hour)
Sax on the corner and the lights burn low (burn low, burn low)
You take the high note, I will hold the ground
Blue hour, blue hour - do not stop the sound

Jazzy deep house duet at 120 BPM. Rolling deep-house groove with swung hi-hats,
walking upright-bass motif over the sub, smoky muted trumpet and tenor-sax licks
answering the vocals, extended jazz piano chords, a male and a female lead
trading verses and joining in harmony on the chorus, small backing ensemble
echoing the hook, warm vinyl texture, sophisticated late-night club production.

Mureka O2 — “Blue Hour” · 2:49 · generated in 59 s

🎧 Play on useapi.net

Mureka V9 — “Blue Hour” · 2:27 · generated in 72 s

🎧 Play on useapi.net

MiniMax music-2.6 · 1:35 · generated in 62 s

🎧 Play on useapi.net

ElevenLabs music-v1 · 1:12 · generated in 32 s

🎧 Play on useapi.net

Lyria 3 Pro — “Blue Hour Duet (Retry)” · 3:03 · generated in 60 s

🎧 Play on useapi.net

What we learned

Nobody has a duration parameter, and only one model listens to the prompt

None of the five APIs exposes a track-length parameter. Every brief above asked for "around 60 seconds" — here is what that request was worth across all our runs, including test takes not published here:

Model	Asked for ~60 s, got	Verdict
ElevenLabs music-v1	1:00 on every prompt-only run	the only model that treats it as a spec
Lyria 3 Pro	~0:59 on 2 prompts, 2:30–3:03 on the rest	occasionally
MiniMax music-2.6	1:20–2:57	ignores it
Mureka O2 / V9	2:30–4:00	ignores it

The lever that actually works is lyric length. With our short one-verse-one-chorus lyrics in part 3, ElevenLabs came in at 0:40, MiniMax dropped to 1:06, and Mureka fell from its usual 3–4 minutes to as short as 0:50 in test takes. If you need a fixed-length cue, write fixed-length lyrics — or trim in post.

ElevenLabs refuses named artists and works, the rest do not

In side experiments we prompted "in the spirit of the James Bond GoldenEye title sequence" and, separately, "in the spirit of Pendulum and The Prodigy". ElevenLabs music-v1 failed both generations at the service level — evidently a copyrighted-reference filter that catches both named works and named artists. Mureka O2, Mureka V9, MiniMax music-2.6, and Lyria 3 Pro accepted and generated both times. Style-descriptive prompts (like round 1's unnamed secret-agent brief) sail through everywhere.

Speed, titles, and what lands in your bucket

ElevenLabs is in a different speed class — 16 to 32 seconds per track in our runs, wall-clock through the API. Lyria followed at 34–79 s, with Mureka V9 at 57–85 s and both Mureka O2 and MiniMax spanning 59–119 s. Mureka and Lyria name their own tracks — every title above is model-written, and in part 3 both pulled the name from our lyric hook, quirky suffixes included ("Take 2" and "Retry" on the Lyria tracks are Lyria's own). The PixVerse-routed models return untitled files. Mureka gives you two variants per generation at 320 kbps, PixVerse one track at 192 kbps, and Flow Music usually an A/B pair with a lossless WAV available — the only lossless source in the group.

FAQ

Which AI music API is the cheapest? Per track in this lineup: Lyria 3 Pro via Flow Music at roughly $0.008–0.013, then Mureka at $0.0135 (Premier plan rate, two variants per generation), MiniMax music-2.6 at $0.16, and ElevenLabs music-v1 at $0.60 via PixVerse. See the lineup for how these compare with the official APIs.

Can I control how long the generated song is? Not with a parameter — no API here has one. Asking in the prompt only works reliably on ElevenLabs. The dependable lever is lyric length: short lyrics produce short songs on every model that accepts custom lyrics.

Can I bring my own lyrics? Yes on all five models: Mureka through music/create-advanced, MiniMax and ElevenLabs through the PixVerse lyrics field, and Lyria through the Flow Music lyrics field. Tag structure with [Verse] and [Chorus].

Will these models imitate a named artist or song? ElevenLabs refuses generation when the prompt names a work or artist — we hit its filter twice. The other four accepted named-reference prompts in our tests. Describing a style without names works on all five.

Ready to run your own listening test? The whole experiment is one script — github.com/useapi/ai-music-comparison sends any brief (the six above are included) to all five models and downloads every track. Then dig deeper with the Mureka and Flow Music tutorials, the PixVerse music endpoint, and a useapi.net subscription — one token, all five models.

Nano Banana 2 Lite vs 2 vs Pro: Google Flow Image Models Compared

useapi.net — Thu, 02 Jul 2026 22:22:01 +0000

Introduction

Google Flow ships three Nano Banana image models — nano-banana-2-lite, nano-banana-2, and nano-banana-pro — and you can drive all three from one prompt through the useapi.net Google Flow API. You use your own Google Flow account, so there's no Google Cloud project, no API key, and no per-image metering — image generation is included on any Google AI plan, even a free one, where the official Gemini API bills $0.034–$0.134 per image.

This guide runs the exact same prompt through Lite, 2, and Pro so you can see how they differ, then hands you a runnable Node.js script that generates the whole set in one command. Want a from-scratch how-to first? See the sibling image-generation tutorial.

What are the three Nano Banana models?

Pick a model per request with the model field. If you omit it, Google Flow uses nano-banana-2-lite — its default since July 2026. All three run on any Google AI subscription, including a free account.

Model id	Marketing name	Best for	References (I2I)	Speed
`nano-banana-2-lite` (default)	Nano Banana 2 Lite / Gemini 3.1 Flash-Lite Image	fast, high-volume generation on any plan	max 10	fastest
`nano-banana-2`	Nano Banana 2 / Gemini 3.1 Flash Image	balanced quality and speed	max 10	fast
`nano-banana-pro`	Nano Banana Pro / Gemini 3 Pro Image	highest fidelity and instruction-following	max 10	slower

All three accept the same aspect ratios (16:9, 4:3, 1:1, 3:4, 9:16, plus auto in image-to-image mode), count (1–4), seed for reproducibility, up to 10 reference images, inline @-mentions, and 2K/4K upscaling. The deprecated aliases imagen-4 (Google removed Imagen from Flow in July 2026) and nano-banana are still accepted and map to nano-banana-2-lite and nano-banana-2 respectively. Full per-model detail is on the POST /images reference.

Upscaling to 2K/4K

Any generated image can be upscaled with POST /images/upscale: pass its mediaGenerationId and a resolution of 2k (default) or 4k. The response is base64 in encodedImage. 2k works on any plan; 4k requires a paid Google account.

Pricing

Image generation is included. You keep your normal Google AI account — even a free one works for images (a paid plan is only needed for video and 4k upscales) — plus a flat $15/month to useapi.net for API access to every service. No per-image metering, no per-call surcharge.

Third-party Google Flow API by useapi.net vs. the official Gemini API — drive your own Google Flow subscription instead of metered, per-call API billing:

Model	Official Gemini API	useapi.net (Flow Pro)	useapi.net (Flow Ultra)
Veo 3.1 Fast — 8s clip	$0.80	~$0.40	~$0.10
Veo 3.1 Quality — 8s clip	$3.20	~$2.00	~$1.00
Veo 3.1 Lite — 8s clip	$0.40	~$0.20	~$0.05
Veo 3.1 Lite, lower priority	—	—	$0 (Ultra $199)
Gemini Omni Flash — 8s clip	— (Flow only)	~$0.50	~$0.25
Nano Banana Pro — per image	$0.134	included	included
Nano Banana 2 — per image	$0.067	included	included
Nano Banana 2 Lite — per image	$0.034	included	included

Expected daily output — Ultra ($199/mo) plan. Daily averages observed on top real accounts. These are expected, not guaranteed: Google governs the underlying Flow allowances and they vary with demand.

Free workload (no Flow credits spent)	Avg generations / day*
Veo 3.1 Lite — lower priority video	~1,000
Images — Nano Banana 2 Lite, Nano Banana 2, Nano Banana Pro	up to ~500

*Averages from the busiest real accounts — not guarantees. They are set by Google's own allowances and fluctuate with demand. Applies only to the free lower-priority video queue and image generation. Credit-metered models (Veo 3.1 Fast / Quality and Gemini Omni Flash) are not shown here — their volume is bounded by your plan's monthly Flow credits (see the credit table), not a free allowance.

Veo is billed per second on the Gemini API (an 8-second 720p clip shown) and images are priced per image. Through useapi.net you spend your own Flow plan credits and pay a flat $15/month — image generation is included on any Google AI plan, and there is no Google Cloud project, API key, or per-call metering.

Full plan and credit details are on the Google Flow overview. See the setup guide to connect your account.

The comparison prompt

A model comparison is only useful if the prompt is hard. This one is a deliberately absurd, single-frame scene that stress-tests several things at once: a named photographic style (David LaChapelle), a multi-subject spatial layout (a swarm forming an arrow in the top-left, a forced-perspective bee in the bottom-right), prop fidelity (dripping honeycomb), a specific comedic facial expression (o_O cartoon eyes), and a clashing tone — all in one cohesive image.

A visually breathtaking, beautifully absurd, single-frame photograph in the hyper-saturated,
glossy, surreal-comedy editorial style of David LaChapelle, shot at a sun-dappled backyard
apiary at golden hour on an 85mm f/1.4 lens with creamy shallow depth of field. In the center
midground, a gorgeous, radiant young woman beekeeper with an elegant figure, flawless glowing
sun-kissed skin and a warm playful smile, incongruously wearing a tiny mini bikini and a
beekeeper's veil hat pushed back off her face, stands among the wooden hive boxes on the grass and lifts a single
open beehive frame heavy with golden honeycomb, thick honey oozing and stringing down in glossy
ribbons and catching the light. She looks directly into the camera, delighted and completely
unbothered by the bees swirling around her. In the top-left of the frame, a dense swarm of bees
bunches together and organizes into a bold, unmistakable arrow / pointer shape aimed straight at
her, as if frantically calling everyone's attention. In the extreme bottom-right foreground of
the exact same scene, photobombing the lens, is a huge forced-perspective close-up of a single
frazzled worker bee, staring directly into the camera with bulging, mind-blown "o_O" cartoon
googly eyes, completely frozen in comical disbelief. Single cohesive image, seamless depth of
field, no cut-ins, warm dynamic backlighting, glistening honey highlights, crazy situational
comedy, hyper-detailed, masterpiece.

Generate across all three models

You need a useapi.net API token and a connected Google Flow account. POST /images is synchronous — one call blocks until the images are ready (typically 20–60 seconds, and the Pro model can take up to ~2 minutes under load) and returns a media[] array with one entry per image, so there's no jobid to poll.

A single call — swap model to compare:

curl -X POST "https://api.useapi.net/v1/google-flow/images" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "nano-banana-pro",
    "aspectRatio": "9:16",
    "count": 4,
    "prompt": "A beekeeper at golden hour lifting a dripping honeycomb frame, a swarm forming an arrow in the sky, a forced-perspective bee with o_O googly eyes in the foreground"
  }' > result.json

# each image is at .media[N].image.generatedImage.fifeUrl
curl -o pro_1.jpg "$(jq -r '.media[0].image.generatedImage.fifeUrl' result.json)"

To run the full comparison in one command, the Node.js script reads prompts.json — one entry per model, all with the same prompt — submits each, and downloads every returned image with a model-labeled filename. You need Node.js v21+. Put both files in a folder and run node ./google-flow-nano-banana-compare.mjs API_TOKEN EMAIL, where API_TOKEN is your useapi.net API token and EMAIL is your connected Google Flow account. The script looks the account up by email and checks its health before submitting, and sends no captchaToken — the useapi.net worker solves the reCAPTCHA automatically.

Prefer to clone and run it? The complete script, a Python port, and prompts.json are on GitHub in useapi/google-flow-api.

Examples

Here is the same beekeeper prompt rendered by each model at 9:16, generated through this Google Flow API. The differences are consistent: Pro is the most polished and the most literal about the instructions, 2 is the most dynamic, and Lite is the fastest while staying close.

nano-banana-pro — the most polished and editorial, and the only model that reliably renders the veil netting, the bees crawling on the comb, and the literal o_O cartoon eyes.

nano-banana-2 — the most dynamic and energetic interpretation, with the clearest arrow-shaped swarm and lots of situational detail (work boots, bees on the frame).

nano-banana-2-lite — the fastest of the three (roughly half Pro's time in our runs) while keeping the composition, the honey drip, and the googly-eyed foreground bee.

Which Nano Banana model should you use?

Reach for nano-banana-pro when fidelity matters most — hero shots, complex multi-subject scenes, precise text or instruction-following. It is the slowest of the three.
Reach for nano-banana-2 for a strong balance of quality and speed, or when you want a more dynamic, stylized read of a prompt.
Reach for nano-banana-2-lite (the default) for iteration and high-volume batches where speed matters and the quality is still very close.

Because they share the same request shape, switching is a one-word change to model — generate a batch across all three and pick the winner, exactly like the script above does.

Run it yourself

The complete Node.js script, a Python port, and prompts.json live in useapi/google-flow-api/nano-banana-compare. Clone it, edit prompts.json, and run one command to generate the full comparison set from your own account.

Frequently asked questions

Is there a Nano Banana 2 or Nano Banana Pro API? Yes — two ways. Google offers these models on the official Gemini API, which meters per image on a Google Cloud project. Or use useapi.net's Google Flow API, which exposes the same models as nano-banana-2, nano-banana-2-lite, and nano-banana-pro on the POST /images endpoint — driving your own Google Flow account with no Cloud project and no per-image metering, on any Google AI plan including the free tier.
What is the difference between Nano Banana 2 Lite, 2, and Pro? They are three tiers of Google's Nano Banana image family. nano-banana-pro (Gemini 3 Pro Image) is the highest-fidelity model, nano-banana-2 (Gemini 3.1 Flash Image) balances quality and speed, and nano-banana-2-lite (Gemini 3.1 Flash-Lite Image) is the fastest and the default. All three accept up to 10 reference images, the auto aspect ratio in image-to-image mode, and 2K/4K upscaling.
Which Nano Banana model is best? For maximum quality, nano-banana-pro. For everyday and high-volume work, nano-banana-2-lite is the default and the fastest, with quality very close to the larger models. See Which model should you use? above.
Is it free? Image generation works on any Google AI plan, including a free account, plus a flat monthly subscription to useapi.net for API access to every service. The official Gemini API meters per image instead — see Pricing.
How much does the Nano Banana API cost? Through useapi.net there is no per-image charge — you keep your own Google AI plan (a free account works for images) and pay a flat $15/month for API access to every service. On the official Gemini API the same models meter per image: roughly $0.034 (2 Lite), $0.067 (2), and $0.134 (Pro) per 1K image — see Pricing.
Do generations get moderated? Google applies content moderation, and a rejected request returns an empty result. Moderation decisions vary between requests and between models, so retrying, editing the prompt, or switching models often succeeds — each Nano Banana model moderates a little differently.
Do I need a captcha or a Google Cloud project? No Google Cloud project. Generation requires reCAPTCHA, but you don't solve it — the useapi.net worker does it automatically, and your first Google Flow account comes with 300 free captcha credits (a one-time grant powered by CapSolver). The script here sends no captchaToken and relies on that automatic solving.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

Check our GitHub repo with code examples.

Cross posted

17+ AI Image Models: The Showdown

useapi.net — Sat, 27 Jun 2026 20:03:57 +0000

Midjourney v7 · GPT Image 2/1.5/Mini · Nano Banana Pro/2/1 · Kling Kolors v3.0/v2.1 · Seedream 5.0→4.0 · Imagen 4 · Qwen Image · Runway Gen4

Introduction

We ran the same text-to-image prompt through 17 image generation models — all of them available through the useapi.net API — to see how each one interprets it. useapi.net is a third-party API that automates these models across six provider platforms (MiniMax, PixVerse, Dreamina, Kling, Runway, and Google Flow), so every model in this showdown is reachable from one account and token. All images use 16:9 aspect ratio with resolution closest to 1080p — not all models support it since some start at 2K and up.

Google Flow's version of Nano Banana models was too restrictive for this prompt, so Nano Banana generation was done via PixVerse instead.

Why this prompt

This prompt stress-tests NSFW content moderation boundaries, multi-subject composition with precise spatial layout, forced perspective depth of field, contradictory context (bikini + jackhammer), specific animal facial expressions, prop fidelity, single cohesive frame rendering, dynamic action, and clashing tone contrast — all in one image.

Prompt

14 of 17 models used the same prompt:

A visually breathtaking, beautifully absurd, single-frame street photography
shot on a sunny city sidewalk. In the center midground, a gorgeous, stunningly
beautiful young woman with a soft, elegant feminine figure, a flawless glowing
complexion, and a radiant, upbeat laugh is wearing a tiny, elegant black-lace
string bikini. She is effortlessly operating a heavy, rattling, bright yellow
pneumatic jackhammer, busting up the concrete pavement while dust and debris
fly around her beautifully. In the extreme bottom-right foreground of the exact
same scene, standing on the sidewalk and photobombing the camera lens, is a
huge forced-perspective close-up of a city squirrel. The squirrel is holding a
half-eaten hotdog, staring directly into the lens with bulging, mind-blown
"o_O" eyes, completely frozen in comical disbelief. Single cohesive image,
seamless depth of field, no cut-ins, dynamic lighting, crazy situational
comedy, delicate feminine features contrasting with heavy machinery, masterpiece.

Imagen 4 — Google's content moderation required a toned-down version: ...is wearing a stylish summer swimsuit... (all other text identical).

GPT Image 2 — like Imagen 4, OpenAI's content moderation required the toned-down version (...stylish summer swimsuit...).

Midjourney v7 — rewritten for Midjourney's style:

A wide-angle GoPro action-camera shot of a sunny city sidewalk. In the extreme
bottom-right foreground, a shocked squirrel's face photobombs the lens while
holding a hotdog. In the center midground, a stunning woman in a tiny black
lace bikini is clearly visible and in sharp focus, operating a heavy yellow
jackhammer. Concrete debris flying, 8k, deep depth of field, f/11, high-speed
shutter, absurd comedy

How it was generated

All images were generated on the actual provider websites (PixVerse, Dreamina, MiniMax/HailuoAI, Runway, Google Flow, Kling, Midjourney) — our third-party API is just a smart proxy service that automates interaction with the provider websites and does not generate images itself.

Unlimited generations

PixVerse, Google Flow, Dreamina, and Runway support unlimited image generations for select models depending on the underlying website subscription plan.

Midjourney v7

open in new tab

Midjourney v7 via MiniMax API — POST images/create (model midjourney-v7)

GPT Image 2

open in new tab

GPT Image 2 (OpenAI) via MiniMax API — POST images/create (model gpt-image-2)

GPT Image 1.5

open in new tab

GPT Image 1.5 (OpenAI) via MiniMax API — POST images/create

GPT Image 1 Mini

open in new tab

GPT Image 1 Mini (OpenAI) via Runway API — POST images/create

Nano Banana Pro

open in new tab

Nano Banana Pro (Gemini 3.0) via PixVerse API — POST images/create

Nano Banana 2

open in new tab

Nano Banana 2 (Gemini 3.1 Flash) via PixVerse API — POST images/create

Nano Banana

open in new tab

Nano Banana (Gemini 2.5 Flash) via PixVerse API — POST images/create

Kling Kolors v3.0

open in new tab

Kling Kolors v3.0 via Kling API — POST images/kolors

Kling Kolors v2.1

open in new tab

Kling Kolors v2.1 via Kling API — POST images/kolors

Seedream 5.0 Lite

open in new tab

Seedream 5.0 Lite via PixVerse API — POST images/create

Seedream 4.6

open in new tab

Seedream 4.6 via Dreamina API — POST images

Seedream 4.5

open in new tab

Seedream 4.5 via PixVerse API — POST images/create

Seedream 4.1

open in new tab

Seedream 4.1 via Dreamina API — POST images

Seedream 4.0

open in new tab

Seedream 4.0 via PixVerse API — POST images/create

Imagen 4

open in new tab

Imagen 4 (Google) via Google Flow API — POST images Note: uses toned-down prompt (see above)

Qwen Image

open in new tab

Qwen Image (Qwen2.5-VL) via PixVerse API — POST images/create

Runway Gen4

open in new tab

Runway Gen4 via Runway API — POST images/create

How to Generate AI Video with Kling v3 via the Kling API

useapi.net — Mon, 22 Jun 2026 05:46:24 +0000

Introduction

Kling AI is rated by independent text-to-video leaderboards among the strongest models for prompt adherence and motion realism — and you can drive every Kling model from code against your own account. Kling AI is the generative video service from Chinese short-video giant Kuaishou Technology, and useapi.net fronts it with a third-party Kling API that runs your own Kling account over a standard REST endpoint — no enterprise contract, no per-call billing from us.

Supported models

Pick a model per request with the model_name field on POST /videos/text2video. kling-v1-6 is the default. Capabilities differ by version:

Model	Durations	Modes / resolution	Audio
`kling-v3-0`	3–15s	`std` 720p · `pro` 1080p · `4k` 4K	Default on
`kling-v3-0-turbo`	3–15s	`std` 720p · `pro` 1080p	Always on
`kling-v2-6`	5 / 10s	`std` 720p · `pro` 1080p	Native Audio (`pro`)
`kling-v2-5`	5 / 10s	`pro` 1080p only	Sound effects
`kling-v2-1-master`	5 / 10s	`pro` 1080p only	Sound effects
`kling-v1-6` (default)	5 / 10s	`std` 720p · `pro` 1080p	Sound effects
`kling-v1-5`	5 / 10s	`std` 720p · `pro` 1080p	Sound effects

Model v3-0 is the most capable: it adds 4k mode and audio on by default. Model v3-0-turbo is the faster v3 — it keeps v3.0 quality with shorter generation times, audio always on, and std/pro modes (no 4k). Model 2.6 produces Native Audio, but only in pro mode. The negative_prompt and cfg_scale parameters apply only to the 1.x models — 2.5, 2.6, and 3.0 do not support negative_prompt, and cfg_scale is a 1.x-only control. The same account and token also drive Kling's multi-shot storytelling, Video Elements, Avatars, and lip-sync — see the Kling API overview for the full lineup.

Pricing

You keep your normal Kling website subscription for the underlying account — Kling starts with a free tier and a $10/month Standard plan — and add a single flat $15/month to useapi.net that covers API access to every supported service, with no per-generation surcharge from us. Generations draw from your Kling account's own credit balance at Kling's standard rates, which vary by model, mode, duration, and audio. The Kling API overview has a live cost calculator that maps each model and mode to its credit cost for your plan.

This is the consumer-account route. Kuaishou's official Kling API bills per generation at developer rates on a separate developer account, while useapi.net automates the consumer account you already pay for at the website subscription price.

Generate a video in two API calls

You need a useapi.net API token and a connected Kling account — export the token so the curl examples below run as-is:

export USEAPI_TOKEN="user:1234-..."

Generation is asynchronous — the create call returns a task object immediately, then you poll until the video is ready.

1. Submit the job — POST https://api.useapi.net/v1/kling/videos/text2video:

curl -X POST "https://api.useapi.net/v1/kling/videos/text2video" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "A majestic mountain landscape with snow-capped peaks and flowing rivers, camera slowly panning right",
    "model_name": "kling-v3-0",
    "aspect_ratio": "16:9",
    "mode": "pro",
    "duration": "5"
  }'

The response returns immediately with a task object. The task id you poll on is task.id (a number):

{
  "task": {
    "id": 123456789,
    "type": "m2v_aio2video",
    "status": 5,
    "status_name": "submitted",
    "status_final": false
  },
  "works": [],
  "status": 5,
  "status_name": "submitted",
  "status_final": false,
  "message": ""
}

The email field is required in the body only when you have more than one Kling account configured. A 500 from Kling almost always means a content-moderation rejection rather than a server fault — read the error text (the message field is generic and often misleading) to tell them apart.

2. Poll for the result — GET https://api.useapi.net/v1/kling/tasks/{task_id}:

curl "https://api.useapi.net/v1/kling/tasks/123456789?email=user@example.com" \
  -H "Authorization: Bearer $USEAPI_TOKEN"

The task is done when status_final is true. Success is status_name: "succeed" (status: 99); the MP4 is in works[0].resource.resource:

{
  "status": 99,
  "status_name": "succeed",
  "status_final": true,
  "works": [
    {
      "workId": 123456789,
      "status_name": "succeed",
      "resource": {
        "resource": "https://s21-kling.klingai.com/....mp4",
        "height": 1268,
        "width": 724,
        "duration": 5041
      }
    }
  ]
}

The MP4 at works[0].resource.resource is watermarked. To get the clean, non-watermarked master, take the workId from the works array and call GET /assets/download — it returns a cdnUrl to the file (a single workId plus a single fileTypes value yields a direct MP4 link, otherwise a .zip):

curl "https://api.useapi.net/v1/kling/assets/download?email=user@example.com&workIds=123456789&fileTypes=MP4" \
  -H "Authorization: Bearer $USEAPI_TOKEN"

A video typically finishes in a few minutes depending on model, mode, and duration — std is faster than pro or 4k. Prefer not to poll? Pass a replyUrl in the create body to receive a webhook callback when the task completes. On the poll, a 404 means the task was deleted, failed at moderation, or your Kling account ran out of credits — check your balance at GET /accounts/email. The terminal failure statuses are 6, 7, 9, 50, 53, 54, and 58 (all status_final: true); see GET /tasks/task_id for what each one means.

Image-to-video

To animate a still image, use POST /videos/image2video-frames. Upload your image first with POST /assets, then pass the returned URL as image (the start frame) and optionally image_tail (the end frame, for a start→end transition):

curl -X POST "https://api.useapi.net/v1/kling/videos/image2video-frames" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "image": "https://example.com/start-frame.jpg",
    "image_tail": "https://example.com/end-frame.jpg",
    "prompt": "the character turns and smiles, camera pushes in",
    "model_name": "kling-v2-5",
    "mode": "pro"
  }'

At least one of image or image_tail is required. On kling-v3-0 / kling-v3-0-turbo the aspect ratio is derived from the input image, so there is no aspect_ratio parameter — and kling-v3-0-turbo supports the start frame only (no image_tail). The response is the same task object as text-to-video, and you poll and download it exactly the same way (with GET /assets/download for the clean master).

Batch-generate with a script

Finding the right shot takes many attempts, and running them by hand is tedious. The Node.js script reads a list of prompts from prompts.json, submits each text-to-video job, then polls every task until it is final and downloads the finished MP4 — preferring the clean, non-watermarked master via GET /assets/download and falling back to the watermarked works[0].resource.resource if needed. So you can queue a batch and come back to the winners.

You need Node.js v21 or newer. Put prompts.json and kling.mjs in the same folder and run node ./kling.mjs API_TOKEN EMAIL, where API_TOKEN is your useapi.net API token and EMAIL is your connected Kling account email. The script looks the account up by email automatically.

Examples

The clip below is a real Kling generation produced through this Kling API, straight from our blog walkthrough.

Kling v3 Turbo — `kling-v3-0-turbo`, image-to-video, 1080p 10s with spoken dialogue and scene cuts

— from Kling 3.0 Turbo: faster video with dialogue and scene changes

Frequently asked questions

Is there a Kling API? Yes — a few ways. Kuaishou offers an official Kling developer API, and third-party resellers (fal.ai, Replicate, PiAPI, and others) expose Kling too, all billed per generation at developer rates. useapi.net is the consumer-account route: programmatic access to every Kling model by driving your own Kling account at the website subscription price through a standard REST endpoint.

How do I access Kling v3 (and v3 Turbo) through the API? Pass "model_name": "kling-v3-0" (or "kling-v3-0-turbo" for the faster variant) to POST /videos/text2video or POST /videos/image2video-frames. Kling v3 supports 3–15s durations, std/pro/4k modes, and audio on by default. See Supported models above.

Can I turn an image into a video (image-to-video)? Yes. Upload the still with POST /assets, then pass the returned URL as image (start frame) and optionally image_tail (end frame) to POST /videos/image2video-frames. See Image-to-video above.

How much does the Kling API cost? You keep your normal Kling website subscription, plus a flat $15/month to useapi.net for API access to all services. Generations draw from your Kling account's own credits at Kling's standard rates, which vary by model, mode, duration, and audio — the Kling API overview has a live cost calculator. See Pricing above.

Why is my video watermarked? The MP4 at works[0].resource.resource returned by the poll is the watermarked preview. To get the clean, non-watermarked master, take the workId from the task's works array and call GET /assets/download — it returns a cdnUrl to the watermark-free file. This requires a paid Kling account. See Generate a video in two API calls above.

How is this different from the official Kling API? Kuaishou's official Kling API bills per generation at developer rates on a separate developer account. useapi.net instead automates your own consumer Kling account, so you generate at the website subscription price plus a flat $15/month — and the same one subscription covers 10+ other AI services.

My generation returns a 500 — what does that mean? Kling reuses the 500 response for content-moderation rejections as well as genuine server faults, and the generic message field rarely makes the difference clear. Read the error text instead — a moderation rejection reads like "The content you uploaded appears to violate the community guidelines." If a job clears creation but the poll later returns 404, the task was deleted, failed at moderation, or your account ran out of credits.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

The full runnable example is in the kling-api GitHub repo.

Cross posted

How to Generate AI Video with Veo 3.1 via the Google Flow API

useapi.net — Thu, 18 Jun 2026 04:23:24 +0000

Introduction

Veo 3.1, Google's flagship video model, runs from a single curl through useapi.net. You drive your own Google Flow account — no Google Cloud project, no enterprise approval, and up to several times lower cost per generation than the official metered API.

The official Gemini API and Vertex meter Veo per second of output. This third-party Google Flow API runs on a flat subscription instead — you spend your normal Flow credits plus one monthly fee for API access, far cheaper per clip. Below: the models you get, the price gap versus the official API, then the two-call workflow and a runnable batch script.

Supported models

Pick a model per request with the model field (default veo-3.1-fast). Credit costs come from Google's official Flow credits table:

Model id	Tier / speed	Durations	Credits per generation
`veo-3.1-lite`	Cheapest Veo	4s, 6s, 8s	10 (Non-Ultra) · 5 (Ultra)
`veo-3.1-lite-low-priority`	Lite, lower priority	4s, 6s, 8s	0 — Ultra $199 only
`veo-3.1-fast` (default)	Fast Veo	4s, 6s, 8s	20 (Non-Ultra) · 10 (Ultra)
`veo-3.1-quality`	Highest-quality Veo	8s only	100
`omni-flash`	Gemini Omni Flash, audio-native	4s, 6s, 8s, 10s	15 / 20 / 25 / 30 (by length)

Notes from the overview: 4s/6s are Ultra-only on Veo, veo-3.1-quality is 8s only, veo-3.1-lite-low-priority costs 0 credits but is available only to Google AI Ultra $199 subscribers, and 10s clips are omni-flash only. Google Flow can also generate stills with Imagen 4 and the Nano Banana models via the separate POST /images endpoint.

Pricing

You spend your Google AI plan's Flow credits as usual, plus a flat $15/month to useapi.net for API access to every supported service — no per-call surcharge.

Third-party Google Flow API by useapi.net vs. the official Gemini API — drive your own Google Flow subscription instead of metered, per-call API billing:

Model	Official Gemini API	useapi.net (Flow Pro)	useapi.net (Flow Ultra)
Veo 3.1 Fast — 8s clip	$0.80	~$0.40	~$0.10
Veo 3.1 Quality — 8s clip	$3.20	~$2.00	~$1.00
Veo 3.1 Lite — 8s clip	$0.40	~$0.20	~$0.05
Veo 3.1 Lite, lower priority	—	—	$0 (Ultra $199)
Gemini Omni Flash — 8s clip	— (Flow only)	~$0.50	~$0.25
Nano Banana Pro — per image	$0.134	included	included
Nano Banana — per image	$0.039	included	included
Imagen 4 — per image	metered	included	included

Free workload (no Flow credits spent)	Avg generations / day*
Veo 3.1 Lite — lower priority video	~1,000
Images — Nano Banana, Nano Banana Pro, Imagen 4	up to ~500

Full per-tier credit allowances and the per-model cost breakdown live on the Google Flow overview. See the setup guide to connect your account.

Generate a video in two API calls

You need a useapi.net API token and a connected Google Flow account. Generation is asynchronous: pass async: true and the create call returns a jobid immediately, then you poll until the video is ready.

Submit the job — POST https://api.useapi.net/v1/google-flow/videos:

curl -X POST "https://api.useapi.net/v1/google-flow/videos" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "A serene mountain landscape at sunset, camera slowly panning right",
    "model": "veo-3.1-fast",
    "aspectRatio": "landscape",
    "duration": 8,
    "async": true
  }'

In async mode the response returns immediately with 201 Created, a lowercase jobid, and status: "created":

{
  "jobid": "j1731859234567v-u12345-email:jo***@gmail.com-bot:google-flow",
  "type": "video",
  "status": "created",
  "created": "2026-06-15T12:34:56.789Z",
  "request": {
    "async": true,
    "prompt": "A serene mountain landscape at sunset, camera slowly panning right",
    "model": "veo-3.1-fast",
    "aspectRatio": "landscape",
    "duration": 8
  }
}

Poll for the result — GET https://api.useapi.net/v1/google-flow/jobs/{jobId}:

curl "https://api.useapi.net/v1/google-flow/jobs/{jobId}" \
  -H "Authorization: Bearer $USEAPI_TOKEN"

status moves through created → started → completed. When it reaches completed, the finished MP4 is in response.media[].videoUrl (a single prompt with count > 1 returns one entry per clip):

{
  "jobid": "j1731859234567v-...",
  "type": "video",
  "status": "completed",
  "response": {
    "media": [
      {
        "mediaGenerationId": "user:12345-email:6a6f...-video:a1d95d21-...",
        "videoUrl": "https://flow-content.google/video/a1d95d21-...?Expires=...",
        "thumbnailUrl": "https://flow-content.google/image/a1d95d21-...?Expires=..."
      }
    ],
    "remainingCredits": 18760
  }
}

Veo 3.1 typically finishes in 60–180 seconds depending on model and mode. The signed videoUrl is valid for about 24 hours, so download promptly. Prefer not to poll? Pass a replyUrl in the create body to receive a webhook callback when the job completes.

Image-to-video and reference-to-video

Veo takes image inputs two different ways. Upload each image first with POST /assets/email (raw bytes, an image Content-Type, PNG/JPEG/WebP up to 20 MB). The upload response nests the id at mediaGenerationId.mediaGenerationId — that nested string is what you pass back. When you supply any image input you can omit email: the request routes to the account where the image was uploaded.

First / last frame (I2V)

Your image becomes a literal frame of the clip. Pass it as startImage to start from that frame:

curl -X POST "https://api.useapi.net/v1/google-flow/videos" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Brave Captain Cat chasing away the pirates!",
    "model": "veo-3.1-fast",
    "aspectRatio": "portrait",
    "startImage": "user:12345-email:6a6f...-image:ff9aa5cc-...",
    "async": true
  }'

Add endImage (a second uploaded reference id) to pin the last frame so Veo generates the transition between the two. endImage requires startImage — end-frame-only is not supported. On omni-flash, only startImage is accepted.

Reference images (R2V)

Your images guide the whole clip — subject, character, or style — rather than a specific frame. Pass referenceImage_1 through referenceImage_3 (Veo accepts up to 3, on 8-second clips only, and not on veo-3.1-quality). R2V cannot be combined with startImage/endImage:

curl -X POST "https://api.useapi.net/v1/google-flow/videos" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "A lady says to the dog, \"Say meow meow meow.\" The dog looks at the lady with a surprised, frustrated look and woofs in a human voice, \"What the heck lady?!\"",
    "model": "veo-3.1-fast",
    "aspectRatio": "portrait",
    "referenceImage_1": "user:12345-email:6a6f...-image:abcde-...",
    "async": true
  }'

Mention each reference inline with an @referenceImage_N marker in the prompt, add a referenceAudio_1 (a system voice name like Zephyr) for narration, or pass a reusable character as character_1 (it drives the same R2V mode and counts toward the 3-reference budget). Omni Flash takes references further — up to 7, plus video-to-video editing and synced voices — see the Omni Flash tutorial.

Batch-generate with a script

Finding the right shot takes many attempts, and running them by hand is tedious. The Node.js script reads a list of prompts from prompts.json, uploads any start/end frame images, submits each job in async mode, then polls and downloads every finished MP4 — so you can queue a batch and come back to the winners.

You need Node.js v21 or newer. Put prompts.json and google-flow.mjs in the same folder and run node ./google-flow.mjs API_TOKEN EMAIL, where API_TOKEN is your useapi.net API token and EMAIL is your connected Google Flow account email. The script looks the account up by email automatically and checks its health field before submitting.

Prefer to clone and run it locally? The complete google-flow.mjs and prompts.json are on GitHub in useapi/google-flow-api.

Examples

Real Veo 3.1 clips generated through this Google Flow API, taken straight from our release notes.

veo-3.1-fast » Brave Captain Cat chasing away the pirates (image-to-video)

From Google Flow API v1: Initial Release. Animated from a Nano Banana still passed as startImage.

veo-3.1-fast » Lady and her dog, with AI voice narration

From Veo 3.1 Lite and Voice Narration. A reference-to-video generation with the referenceAudio_1: "Zephyr" preset adding spoken dialogue.

veo-3.1-fast » Dancing cha-cha (portrait reference-to-video)

From Veo 3.1 Portrait R2V. Portrait R2V from a single reference image.

Frequently asked questions

Is there a Veo 3.1 API? Yes — two ways. Google offers Veo 3.1 directly through the official Gemini API (and Vertex AI), billed per second on a Google Cloud project. Or use useapi.net's Google Flow API, which gives you programmatic access to Veo 3.1 (Quality, Fast, Lite) by driving your own Google Flow account through a standard REST endpoint — no Cloud project, and you pay your flat Flow subscription instead of metered per-second rates (often cheaper per clip — see Pricing).
What's the difference between Veo 3.1 Quality, Fast, and Lite? They trade quality for speed and cost: veo-3.1-quality is the highest-fidelity model, veo-3.1-fast is the default balance, and veo-3.1-lite is the cheapest, with veo-3.1-lite-low-priority available to Ultra subscribers at lower scheduling priority. See Supported models above for per-model credits and durations.
Can I do image-to-video with Veo? Yes. Upload your start frame with POST /assets/email, then pass the returned reference id (nested at mediaGenerationId.mediaGenerationId) as startImage — and optionally endImage for a first→last transition (Veo only, requires startImage). See Image-to-video above.
Do I need to solve a captcha? Google Flow video generation requires reCAPTCHA, but you do not solve it yourself. The useapi.net worker solves the captcha automatically — your first Google Flow account comes with 100 free captcha credits as a one-time grant (powered by CapSolver), and after that you configure your own provider keys via POST /accounts/captcha-providers. The script in this guide sends no captchaToken and relies on this automatic solving.
How much does it cost? You keep your paid Google AI subscription (needed for video) and add a flat useapi.net subscription for API access to all services. Each generation then spends your normal Flow credits from your Google plan — far cheaper than the official metered API; see Pricing above.
How is this different from the official Google / Gemini API? Google's official Veo 3.1 access runs through the Gemini API / Vertex AI on a Google Cloud project, billed per second. Google Flow — the consumer app — has no public API of its own. useapi.net bridges that gap by driving your own consumer Flow account at its flat subscription price — no Cloud project or per-second metering (see the side-by-side Pricing comparison above), and the same subscription covers other AI services too.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

Check our GitHub repo with code examples.

Cross posted

Create breath-taking videos with PixVerse AI

useapi.net — Sun, 09 Jun 2024 06:19:23 +0000

Introduction

In this article we will show hot to use an experimental API for the PixVerse Discord Bot by PixVerse.AI to generate videos. PixVerse currently supports text and image inputs for generating 4-second-long videos. The available video styles include Realistic, Anime, and 3D Animation. For the Anime style you can reference one of the anime characters. PixVerse can also create a meme face video from a provided image.

Examples

/animate

Source image

/meme_face

Source image

A girl smiling by the beach, sunset in the background

/create_single

A cinematic shot of a tiny hedgehog dressed in a complete astronaut suit, floating in the vastness of outer space. The hedgehog is repairing a small satellite with tiny tools. The Earth shines in the distance, and stars and constellations illuminate the dark cosmic background. Nearby, a futuristic spaceship with another animal peeking from a window completes the cosmic scene

/create

A front view, head to toe, beautiful female model walking the runway. Emphasis is on the Great Gatsby inspired evening gown in the style of John Galliano

A women silhouette dancing provocative with flashing strobe lights flashing with laser beams

A girl smiling in a magic redwood forest

Setup

We will use the experimental API provided by useapi.net to interact with Midjourney, InsightFaceSwap, Pika and PixVerse Discord bots.

Useapi.net

You need a monthly subscription to use the useapi.net experimental APIs mentioned in this article.
Follow these steps to get started.

PixVerse

The PixVerse Discord bot is currently free, please follow these simple steps to obtain the following:

Discord server ID number, referred to in this article as server.
Discord channel ID number, referred to in this article as channel.
Discord token, referred to in this article as discord. Verify Discord access.
Once you have all the above, please create or update your PixVerse account information so that you no longer need to provide them with every API call.

Useapi.net provides an easy way to experiment with all API endpoints without writing any code. Check the Try It section at the end of each document page, such as PixVerse's /create, /animate, or /meme_face.

For your convenience, we have published all the source code used in this article. You can choose between JavaScript and Python examples. Clone this repository locally and use it as a starting point for your experiments.

Ngrok

Follow official instructions to sign up for an ngrok account and copy your ngrok authtoken from your ngrok dashboard.

Preparing PixVerse prompts

An array of desired prompts should be saved to a locally cloned prompts.json file.

Executing prompts using PixVerse experimental API by useapi.net

Create a file locally in the same folder named example.sh with the following content:

JavaScript

USEAPI_TOKEN="useapi API token" NGROK_AUTHTOKEN="ngrok authtoken" node ./example.js

Python

USEAPI_TOKEN="useapi API token" NGROK_AUTHTOKEN="ngrok authtoken" python3 ./example.py

Execute it from the command line like this: ./example.sh and observe the magic of the experimental API.

The generated videos will be saved locally. You may proceed with the generation process within a Discord channel to further refine your creations. Alternatively, you can continue automate the process by using the /button API endpoint.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

Discord CDN Proxy

useapi.net — Mon, 13 May 2024 21:44:20 +0000

Host your images and videos on Discord CDN

Suppose you want to take advantage of the free Discord CDN to host your images or videos. With the simple script below, you can upload your assets to a desired Discord channel:

curl -X POST "https://discord.com/api/v10/channels/<Discord channel>/messages" \
-H "Authorization: <Discord token>" \
-F 'payload_json={"content":"Here is your file!","attachments":[{"id":0,"filename":"<file name>"}]}' \
-F 'files[0]=@<path to file name>'

Example:

curl -X POST "https://discord.com/api/v10/channels/123456789/messages" \
-H "Authorization: ABc.your.discord.token.xYZ" \
-F 'payload_json={"content":"Here is your file!","attachments":[{"id":0,"filename":"source.jpg"}]}' \
-F 'files[0]=@./source.jpg'

Please refer to our guide on how to obtain your Discord token and set up a private channel. Omit the Midjourney setup steps if you do not plan to use it.

Response JSON will contain attachments[0].url with Discord CDN attachment link.

Create a Proxy for Discord CDN

Starting December 2023 all Discord CDN attachment links have following format: https://cdn.discordapp.com/attachments/channel/message/filename.ext?ex=EXPIRES&is=ISSUED&hm=CODE

Query parameters values EXPIRES and ISSUED are timestamps in unix/epoch hex format, CODE is encoded checksum used to verify EXPIRES and ISSUED values.

Attempt to retrieve Discord CDN attachments URL without above query parameters or with EXPIRES past current time will result in 404 This content is no longer available. response, see example.

In practical terms this means that you can no longer link attachments from Discord on your website, share them on Reddit, Facebook.

This article provides you with effective solution to continue sharing your Discord CDN content publicly without incurring any costs.

The Discord CND proxy especially handy for users of Midjourney API, Pika API or InsightFaceSwap API.

Once your public proxy deployed you can use public image links using https://your-discord-cdn-proxy-url/?https://cdn.discordapp.com/attachments/channel/message/filename.ext format.

These links can be shared publicly, published on your website, etc.

The proxy will refresh the links provided after the ? and redirect the browser to the refreshed Discord CDN link.

You can include original Discord attachment link query parameters as well ?ex=EXPIRES&is=ISSUED&hm=CODE, the proxy will check if the link has expired, and may return the original URL immediately if it is not expired.

When responding with HTTP 302 the proxy will set response headers Expires with link expiration time.

Custom response header x-discord-cdn-proxy will be set to one of following values:

original - provided link query parameters ?ex=EXPIRES&is=ISSUED&hm=CODE indicate that link is still "fresh"
refreshed - call to https://discord.com/api/v9/attachments/refresh-urls Discord API was made to retrieve refreshed link
memory - refreshed link returned from the memory cache
bucket - refreshed link returned from the R2 bucket cache (optional for Cloudflare Worker deployment)

Diagram

Original Discord CDN link open (404: This content is no longer available.)
Discord CDN link using proxy open
Discord CDN link using proxy (without query parameters) open

Two deployment options covered in the article:

Google App Engine instructions.
- F1 instance is free to run 24/7/365 link.
- Google asks for a credit card or other payment method when you sign up for the Free Trial/Free Tier link.
Cloudflare Worker instructions.
- 100K requests per day are included in the free tier account link.
- Cloudflare does not require the entering of payment information.

You can choose either option based on your preferences.

The source code for Google App Engine is a standard Node.js Express server.

You can deploy it in any compatible environment, see the instructions below:

Deploy Google App Engine

Assuming you have Google Cloud account and installed gcloud CLI.

Clone git repository discord-cdn-proxy.

Navigate to ./google-app-engine folder and install npm packages:

npm install

You can follow along the official Google App Engine deployment steps for Node.js.

gcloud auth login

Create new project:

gcloud projects create discord-cdn-proxy

Select created project:

gcloud config set project discord-cdn-proxy

Find created project on your Google Cloud Dashboard and link billing account to the project.

Create App Engine project:

gcloud app create

Create .env.yaml file with following yaml:

env_variables:
  DISCORD_TOKEN: "discord token"
  CHANNELS: "['channel id', 'another channel id', 'channel id etc']"

How to extract discord token.

Optional array CHANNELS defines which Discord channels should be proxied.

You can remove it but it is strongly not recommended for public proxies.

Deploy App Engine project:

gcloud app deploy

You may have to run the above command a few times, as it often fails on the first run.

Notice the name of the deployed service, which will look like:
Deployed service [default] to [https://discord-cdn-proxy.it.r.appspot.com]

Update .env.yaml file and add DISCORD_CDN_PROXY_URL with value from deployed service:

env_variables:
  DISCORD_TOKEN: "discord token"
  CHANNELS: "['channel id', 'another channel id', 'channel id etc']"
  DISCORD_CDN_PROXY_URL: "https://discord-cdn-proxy.it.r.appspot.com"

Deploy App Engine project with updated configuration:

gcloud app deploy

Now you can test deployed proxy.

Example (adjust to include actual values): https://discord-cdn-proxy.it.r.appspot.com/?https://cdn.discordapp.com/attachments/channel/message/filename.ext

Debugging locally

Update DISCORD_TOKEN value in your package.json file:

{
  "name": "discord-cdn-proxy",
  "version": "1.0.0",
  "description": "Discord CDN proxy",
  "main": "server.js",
  "type": "module",
  "scripts": {
    "start": "node server.js",
    "debug": "DISCORD_TOKEN='discord token' DISCORD_CDN_PROXY_URL='http://localhost:8090/' node server.js"
  },
  "author": "useapi.net",
  "license": "ISC",
  "dependencies": {
    "express": "^4.19.2"
  }
}

Execute script with npm:

npm run debug

Deploy Cloudflare Worker

Assuming you have free Cloudflare account setup completed and installed Wrangler CLI.

Clone git repository discord-cdn-proxy.

Navigate to ./cloudflare-web-worker folder and install npm packages:

npm install

If you are familiar with Cloudflare Workers, you can adjust the deployment configuration in the wrangler.toml file.

You can fine-tune it later at any time once you have acquired some initial experience.

Deploy Worker:

wrangler deploy --keep-vars

Notice deployment url which will look like https://discord-cdn-proxy.your-user-name.workers.dev

You can use that url to test by adding Discord link at the end after ?

Example: https://your-discord-cdn-proxy-url/?https://cdn.discordapp.com/attachments/channel/message/filename.ext

Create .secrets file with following JSON:

{
    "DISCORD_TOKEN": "discord token",
    "CHANNELS": "['channel id', 'another channel id', 'channel id etc']"
}

How to extract discord token.

Optional array CHANNELS defines which Discord channels should be proxied.

You can remove it but it is strongly not recommended for public proxies.

Deploy secrets from local file .secrets:

wrangler secret:bulk .secrets

Now you can test deployed proxy.

Example (adjust to include actual values): https://your-discord-cdn-proxy-url/?https://cdn.discordapp.com/attachments/channel/message/filename.ext

Debugging locally

Create .dev.vars file with following text:

DISCORD_TOKEN="discord token"
CHANNELS=["channel id", "another channel id", "channel id etc"]

Run local development using .dev.var secrets:

wrangler dev

Refreshing Discord links using an R2 bucket for caching

This allows you to store refreshed Discord links in a Cloudflare R2 bucket to minimize the number of calls to the Discord API.

To create an R2 bucket, execute:

wrangler r2 bucket create discord-cdn-proxy-cache
wrangler r2 bucket list

Uncomment r2_buckets configuration in wrangler.toml file.

Redeploy Worker:

wrangler deploy --keep-vars

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

Check our GitHub repo with code examples.

Face swap and animate images generated by Midjourney using InsightFaceSwap and Pika

useapi.net — Mon, 26 Feb 2024 02:50:16 +0000

Introduction

This article covers multiple experimental APIs provided by useapi.net.

You will learn how you can easily generate and upscale images from your prompt(s) using Midjourney, apply face swap via InsightFaceSwap, and finally animate the result using Pika.

First, we will be generating images using the /imagine command from Midjourney and upscaling them with the /button command using the experimental Midjorney API.

Next, we will use the InsightFaceSwap Discord Bot by Picsi.Ai using the experimental InsightFaceSwap API to swap faces on the upscaled images mentioned above.

Finally, animation provided by the Pika Discord Bot will be applied to the face swapped images via the experimental Pika API.

Please check out the 👉 YouTube video 👈 showcasing the final results of these generations from this article.

This article explains how to use a webhook to retrieve generated results and how to structure a basic query to submit requests to the API. This approach is much more performant and consumes fewer resources.

Setup

We will use the experimental API provided by useapi.net to interact with Midjourney, InsightFaceSwap and Pika Discord bots.

Useapi.net

You need a monthly subscription to use the useapi.net experimental APIs mentioned in this article.
Follow these steps to get started.

Midjourney

Naturally you'll need a Discord account with an active Midjourney subscription. The $10 Basic Plan will suffice.

Follow these simple steps to obtain the following:

Discord server ID number, referred to in this article as server.
Discord channel ID number, referred to in this article as channel.
Discord token, referred to in this article as discord. Verify Discord access.
Once you have all the above, please create or update your Midjourney account information so that you no longer need to provide them with every API call.

InsightFaceSwap

The InsightFaceSwap setup is similar to Midjourney's, please follow our instructions.

InsightFaceSwap allows users to swap faces from source images onto different target images. It offers free and paid subscriptions. Paid subscribers have access to a wide selection of extra features, such as HiFidelity Mode, ARTIFY, oldify/youngify, morphing multiple faces in one image, and many more.

You can add the InsightFaceSwap Discord bot to the same server and channel as the Midjourney bot to speed up and simplify the setup process. If you're planning to use the free plan, you may want to consider setting up multiple Discord/InsightFaceSwap accounts so that you can execute more operations daily, since one account alone may not suffice.

Pika

The Pika Discord bot is currently free. The setup process is very similar to the ones above. Please refer to the Pika setup steps. Since you have already retrieved your Discord token during the Midjourney setup, you only need to identify the channel for Pika Direct Messages.

Useapi.net provides an easy way to experiment with all API endpoints without writing any code. Check the Try It section at the end of each document page, such as Midjourney's jobs/imagine, InsightFaceSwap's faceswap/swap, or Pika's pika/animate.

Ngrok

Follow official instructions to sign up for an ngrok account and copy your ngrok authtoken from your ngrok dashboard.

Preparing Midjourney Prompts

Let's use ChatGPT to create a list of prompts. Here's our ChatGPT prompt:

Create a simple JSON array of strings containing Midjourney prompts to generate the world's most renowned portrait paintings.

The output will look something like this:

[
  "Portrait of a Young Man by Raphael",
  "Salvator Mundi by Leonardo da Vinci",
  …
  "Mona Lisa (La Gioconda) by Leonardo da Vinci"
]

An array of prompts generated by ChatGPT needs to be saved to a locally cloned prompts.json file.

Executing Prompts Using the Midjourney, InsightFaceSwap and Pika experimental API by useapi.net

Create a file locally in the same folder named example.sh with the following content:

JavaScript

USEAPI_TOKEN="useapi API token" NGROK_AUTHTOKEN="ngrok authtoken" node ./example.js

Python

USEAPI_TOKEN="useapi API token" NGROK_AUTHTOKEN="ngrok authtoken" python3 ./example.py

Examples

Upscaled image generated by Midjourney.
Face swapped image generated by InsightFaceSwap from upscaled image above.
Video generated from face swapped image above using text + image animation by Pika.

We used Rick Astley as a source image for face swapping, feel free to change it per your liking.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

Execute it from the command line like this: ./example.sh and observe the magic of the experimental API.

The generated images and videos will be saved locally. You may proceed with the generation process within a Discord channel to further refine your creations. Alternatively, you can continue automate the process by using the jobs/button along with Pika or perhaps InsightFaceSwap, following the same process as demonstrated above.

Examples

Upscaled image generated by Midjourney.

Face swapped image generated by InsightFaceSwap from upscaled image above.

Video generated from face swapped image above using text + image animation by Pika.

We used Rick Astley as a source image for face swapping, feel free to change it per your liking.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

Automating Asset Generation with the Midjourney API • Part I

useapi.net — Sun, 12 Nov 2023 05:12:39 +0000

Introduction

If you are a designer, a game developer, or simply experimenting with Midjourney and want to create a large number of /imagine generations based on your ideas, it may be very tedious and time-consuming to do so manually.

In this article, we will explore methods to efficiently execute such tasks with minimal effort.

We will also attempt to measure the time it takes to generate 50 Midjourney /imagine generations and compare it with the time reported by Midjourney for their Fast GPU.

Please check a YouTube video covering this article.

Setup

We will use the Midjourney API provided by useapi.net to interact with Midjourney.

To get started, you'll need a Discord account with an active Midjourney subscription. The $10 Basic Plan will suffice.

Follow these simple steps to obtain the following:

Discord server id number, referred to in this article as server.
Discord channel id number, referred to in this article as channel.
Discord token, referred to in this article as discord. Verify Discord access.
useapi.net API token, referred to in this article as token. Verify useapi.net API access.

Useapi.net provides an easy way to experiment with all API endpoints without writing any code. Check the Try It section at the end of each document page, such as jobs/imagine.

For your convenience, we have published all the code used in this article. You can choose between JavaScript and Python examples. Clone this repository locally and use it as a starting point for your experiments.

Preparing Midjourney Prompts

Let's use ChatGPT to create a list of prompts. For this article, we will be generating fairy tale characters. Here's our ChatGPT prompt:

Create a JSON array of strings with 50 Midjourney prompts. Each prompt should describe a popular fairy tale protagonist or antagonist placed in the modern world, solving contemporary problems using fairy tale methods. Be creative!

The output will look something like this:

[
    "Cinderella, now a well-known fashion designer, uses her knack for transforming rags into fabulous outfits to help those in poverty dress for success.",
    "Jack, of Jack and the Beanstalk fame, is a successful botanist who tackles the issue of world hunger by growing gigantic, genetically modified crops.",
    "Rapunzel, a professional rock climber, uses her long-braided hair for safety ropes during rescue missions in difficult terrains.",
    ...
    "The Big Bad Wolf, a top-notch security consultant, fortifies homes against break-ins, teaching the importance of strong construction materials."
]

An array of prompts generated by ChatGPT needs to be saved to a locally cloned prompts.json file.

Executing Prompts Using the Midjourney API

Create a file locally in the same folder named example.sh with the following content:

JavaScript

USEAPI_TOKEN="useapi API token" USEAPI_SERVER="Discord server" USEAPI_CHANNEL="Discord channel" USEAPI_DISCORD="Discord token" node ./example.js

Python

USEAPI_TOKEN="useapi API token" USEAPI_SERVER="Discord server" USEAPI_CHANNEL="Discord channel" USEAPI_DISCORD="Discord token" python3 ./example.py

Execute it from the command line like this: ./example.sh and observe the magic of the API. We have created a YouTube video covering this entire process.

The generated images will be saved locally. You can continue the generation process in a Discord channel to refine your desired creations, or you can use the jobs/button to automate it, following the same process as demonstrated above.

Conclusion

As shown in the YouTube video, you can observe the following:

Time to generate 50 Midjourney /imagine creations using the Midjourney API: ~19 minutes
Utilization of the Midjourney Fast GPU: ~26 minutes

Visit our Discord Server for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

DEV Community: useapi.net

MiniMax H3 vs Seedance 2.0: 2K with native audio, head to head on the same omni references

Text to video

A start frame, with speech

Omni references — image, video, and audio together

What it costs

Where H3 fits

How to Generate AI Music with the Mureka API (Suno / Udio Alternative)

Introduction

Pricing

Supported models

Generate a song in two API calls

Write your own lyrics, or force an instrumental

Reference tracks, melody seeding, and custom vocals

Clone a voice and generate multi-speaker speech

Batch-generate with a script

Examples

Astro Gardener — V9, female-vocal indie pop with custom lyrics (create-advanced)

Cascading Sunrise — V9 instrumental (create-instrumental)

Galactic Odyssey — flagship O2 instrumental (create-instrumental)

Pirate Programmer — V7.6, male-vocal sea-shanty-meets-electronic (create-advanced)

Custom vocal clone — an uploaded voice singing custom lyrics over a reference track (create-advanced with vocal_id + ref_id)

Multi-speaker speech — two cloned voices in one conversation (POST /speech)

Frequently asked questions

Conclusion

Seedance 2.0 API Pricing: The Cheapest Ways to Run It, Compared

Introduction

What a Seedance 2.0 clip costs at the source

Four ways to run Seedance 2.0 through useapi.net

The real-faces gap

The wider market, priced honestly

Show me the API call

Which route should you use for Seedance 2.0?

Examples

FAQ

AI Music APIs Compared: Mureka vs MiniMax vs ElevenLabs vs Lyria 3 Pro

Introduction

The lineup and what a track costs

How we tested

Part 1 — Instrumentals

Round 1: big-band noir

Round 2: liquid drum and bass

Part 2 — Vocals, model writes the lyrics

Round 3: pop duet

Round 4: Spanish flamenco-pop

Part 3 — Vocals, our lyrics and an elaborate style brief

Round 5: deep house

Round 6: jazzy house duet

What we learned

Nobody has a duration parameter, and only one model listens to the prompt

ElevenLabs refuses named artists and works, the rest do not

Speed, titles, and what lands in your bucket

FAQ

Nano Banana 2 Lite vs 2 vs Pro: Google Flow Image Models Compared

Introduction

What are the three Nano Banana models?

Upscaling to 2K/4K

Pricing

The comparison prompt

Generate across all three models

Examples

Which Nano Banana model should you use?

Run it yourself

Frequently asked questions

Conclusion

Cross posted

17+ AI Image Models: The Showdown

Introduction

Why this prompt

Prompt

How it was generated

Unlimited generations

Midjourney v7

GPT Image 2

GPT Image 1.5

GPT Image 1 Mini

Nano Banana Pro

Nano Banana 2

Nano Banana

Kling Kolors v3.0

Astro Gardener — `V9`, female-vocal indie pop with custom lyrics (`create-advanced`)

Cascading Sunrise — `V9` instrumental (`create-instrumental`)

Galactic Odyssey — flagship `O2` instrumental (`create-instrumental`)

Pirate Programmer — `V7.6`, male-vocal sea-shanty-meets-electronic (`create-advanced`)

Custom vocal clone — an uploaded voice singing custom lyrics over a reference track (`create-advanced` with `vocal_id` + `ref_id`)

Multi-speaker speech — two cloned voices in one conversation (`POST /speech`)

Kling v3 Turbo — `kling-v3-0-turbo`, image-to-video, 1080p 10s with spoken dialogue and scene cuts