Higgsfield MCP has no credit cap: cap spend with Sume max_spend_usd

Higgsfield's MCP-for-marketers page says the connector has no built-in credit spending cap, and that an active subscription is required. If you let an agent make video, that matters. Sume's MCP generation tools take dry_run=true, which previews admission or cost without submitting, and max_spend_usd, which is enforced only when you provide it.

The facts

Quoted from the Higgsfield page and the Sume MCP tools and gates docs.

A safe agent loop

First call the tool with dry_run=true and read the cost. Then call it again with the same inputs, an idempotency_key and max_spend_usd set to the estimate plus a small margin. The agent cannot spend more than that on that call.

Note the wording: the cap applies only if you pass it. An agent prompt that forgets the field has no cap on that call, so put the rule in the tool wrapper rather than relying on a reminder.

What the cap does not do

max_spend_usd bounds one request. It is not an account budget. For a campaign limit, count spend in your own code across calls, and rely on plan concurrency and queue limits for volume.

Avatar tools in the docs include avatars_create, avatar-videos_create and avatar-video-previews_create.