Manus agent calling paid Sume tools: cap spend per call

A Manus agent with a Sume API key can start paid generation. Tell it to send max_spend_usd, dry_run and an idempotency_key on every paid call. Why each matters.

5 min readSume
All posts

A Manus agent connected to Sume with an API key can call paid tools, so put three rules in its instructions: send max_spend_usd on every paid call, preview with dry_run=true first, and always send a fresh idempotency_key. Sume's docs say max_spend_usd is optional and enforced only when you send it, so an agent that omits it has no per-call cap.

Manus adds the server under Settings > Integrations > Custom MCP Servers, per its docs. The Sume rules are from MCP tools and gates, Generation admission and Safe automation, read 2026-10-06.

What does each control do?

The table below lists each item as documented.

Sume controls from docs.sume.com, read 2026-10-06.
ControlRequiredEffect
idempotency_keyYes, on writes and paid callsA retry returns the original job instead of billing twice
dry_run=trueNoPreviews the call without submitting
max_spend_usdNoRejects a call that would exceed it, when sent
generation_admission_previewNoShows whether generation would be admitted

What goes in the agent instructions?

A text instruction is not a hard limit. For a hard ceiling on an unattended run, use Agent Completions, where generation_spend_cap_usd is required.

  • Before any paid tool, read its contract with tools_schema.
  • Run the call with dry_run=true and show the cost.
  • Send the real call with max_spend_usd set to the amount you approved.
  • If a wait ends with wait_slice_expired, wait again; never create the job again.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume