Higgsfield credits expire after one year: budget vs Sume's USD balance

Higgsfield credits expire one year after they are added. Sume bills a workspace USD balance reserved at list times 1.25. What to check before you top up.

4 min readSume
All posts

Higgsfield says credits expire one year after they are added to your account balance. Sume's video docs describe a workspace USD balance, reserved on submit at provider list times 1.25, and the docs read for this post do not describe an expiry date for that balance, so check the Billing page before a large top-up.

What Higgsfield says

The billing page states the expiry in one line: credits expire one year after they are added. The FAQ describes a pay-as-you-go model with account top-ups, and invoice billing for committed contracts. The same page gives a sample estimate of 1.500 credits, which it shows as $0.094 USD, so a credit in that example is worth about six cents.

What Sume says

Sume does not use credits for /v1/videos. Billing is the workspace USD balance. The cost is reserved when you submit at provider list times 1.25 for every model, captured as the actual cost on success, and refunded on failure. usage.cost on the poll response is the Sume billable amount, and GET /v1/usage lists reservations, captures, refunds and top-ups.

Balance rules, read 2026-10-02
QuestionHiggsfieldSume
UnitCredits (example: 1.500 credits = $0.094)USD balance
ExpiryOne year after credits are addedNot stated on the video or core workflow pages
Top upPay as you go; invoice for committed contractsPrepaid top-ups; see the dashboard
Concurrency tied to balanceLimits per account and modelConcurrency is plan-only; top-ups do not raise it

How to plan around it

A one-year expiry matters when you buy in bulk for a discount. If credits are bought for a promotion and used unevenly, the unused tail can lapse. With a USD balance the question is different: you want to know your cost per second, which on Sume comes from the model's pricing_skus and the usage.cost on completed jobs.

  • Buy to a 12-month forecast, not to the largest bundle.
  • Read the expiry rule on the billing page before each top-up.
  • On Sume, quote a clip from the catalog before you submit and compare it with usage.cost.
  • Keep a monthly reconciliation of captures and refunds from /v1/usage.

Failures are separate

Neither balance model changes how a failed job is billed. Both refund a failure, as covered in the failed and nsfw billing comparison.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume