Higgsfield API vs MiniMax Video API

Higgsfield API

One asynchronous API for 67 video and 17 image catalogue entries, with idempotency keys, per-second list prices public without a login, and failed or moderated jobs not charged. API inputs and outputs train Higgsfield's models unless the workspace opts out, and the docs carry no changelog. The API returns 400 at the concurrency limit, with no Retry-After.

MiniMax Video API

2K with stereo audio at $0.13 a second, 768P at $0.08. No statement found on whether API inputs train models, and the privacy policy needs a browser.

Higgsfield API

1. Send Authorization: Key <key_id>:<key_secret> to https://api.higgsfield.ai. A Bearer token is rejected
2. Send a fresh Idempotency-Key with every generation. After a timeout or 5xx, repeat the same request with the same key, then read status_url
3. Treat a 400 whose detail mentions concurrent requests as a limit, not a bad request. Wait for a running job to finish before submitting more
4. Poll status_url from 2 seconds up to 10 with jitter, and stop on completed, failed, nsfw or canceled
5. Download output within seven days. Media files may be deleted after that
6. Read the model's own docs page for its schema. The OpenAPI file lists only a few models

MiniMax Video API

1. Use POST /v2/video_generation for H3 and poll GET /v2/query/video_generation/{task_id}. Tasks stay queryable for 7 days
2. Set ratio for text-to-video. adaptive isn't allowed there
3. Pass callback_url to skip polling. Your endpoint must echo the challenge within 3 seconds
4. A 402 means the balance is empty and a 422 means moderation blocked the content. Don't retry either unchanged