Higgsfield failed and nsfw requests: no charge. What Sume bills

Higgsfield charges successful generations only: requests that end failed or nsfw are not charged, and any reserved credits are refunded. Sume reserves the cost when you submit, captures the actual cost on success, and refunds on failure or on cancellation before capture.

Higgsfield's rule

Higgsfield's billing page says successful requests are charged in account credits, and a successfully canceled queued request is refunded. The errors page repeats the rule for failed and moderated requests. Its FAQ describes pay-as-you-go top-ups, with invoice billing for committed contracts.

Sume's rule

Sume's /v1/videos page says billing is the workspace USD balance, reserved on submit at provider list times 1.25 for every model. The poll response carries usage.cost, which is the Sume billable amount. The core workflow page says the actual cost is captured on success, with a refund on failure or cancellation before capture, and GET /v1/usage lists reservations, captures, refunds and top-ups as ledger entries.

Reconcile it yourself

Sume's job error categories include generation_rejected (inspect events and fix unsupported input) and quota (add funds or lower request cost), so a rejected prompt shows up as a categorized failure, not a separate status. If you reconcile spend, match each failed job to a refund row in /v1/usage rather than assuming one.

• Record the job id and usage.cost when a job completes.
• Expect a reservation row and a refund row for a failed job.
• Do not resubmit a failed paid job without reading its public error first.

A timeout is not a failure

One difference to plan for: a client-side timeout is not a failure on either side. Higgsfield and Sume both keep running a request you stopped watching, and a completed result is billed whether or not you fetched it.