stt_create dry_run and max_spend_usd: cap an MCP transcription run
On Sume's hosted MCP, dry_run previews admission and cost without submitting, and max_spend_usd caps a paid stt_create. Add an idempotency_key to every write.

On the Sume hosted MCP, call stt_create with dry_run: true first to preview admission and cost without submitting a job, then call it again without dry_run to submit. Add max_spend_usd when you want Sume to enforce a ceiling; it is applied only when you pass it. Every paid write needs its own idempotency_key. These gates are documented in MCP tools and gates, read 2026-10-06.
What each argument does
The tool also accepts the STT request fields (audio_url, language_code, duration_seconds, segmentation, metadata). Send duration_seconds so the preview prices seconds rather than the one-minute default.
| Argument | Effect |
|---|---|
dry_run: true | Admission and cost preview only; does not submit the job |
max_spend_usd | Optional spend ceiling; enforced only when provided |
idempotency_key | Required on a paid write; a retry returns the same job |
The two calls
The first call is the preview. If the cost and queue room are acceptable, send the same arguments without dry_run.
{
"name": "stt_create",
"arguments": {
"audio_url": "https://media.sume.com/example/clip.wav",
"duration_seconds": 12,
"idempotency_key": "stt-clip-0001",
"max_spend_usd": 0.01,
"dry_run": true
}
}Previewing a whole batch
For many clips, the generation_admission_preview tool answers queue and balance questions for a request shape in one call, and usage_get reads the ledger afterward. Pair them with a jobs_wait on the wave.
Sources
Related posts
More in Integrations
- Can I swap a Sume MCP OAuth token for an API key? Why you should not
A hosted MCP OAuth token is not a Sume API key. Do not mint keys as a workaround for a read-only session; turn Write on at consent, or use a key on purpose.
- Trae IDE: add Sume as a remote MCP server with Add Manually
In Trae, open Settings > MCP > Add > Add Manually and paste a JSON entry with Sume's hosted URL and an Authorization header. Steps, trade-offs, key handling.
- v0 custom MCP: connect Sume with a Bearer token or OAuth
In v0, open the + menu, choose MCPs, add a custom MCP and pick Bearer Token or OAuth for auth. Which to use for Sume's hosted server, and what each grants.
- Vercel Sandbox static egress IP: do I need to allowlist Sume?
Secure Compute gives Vercel Sandbox static egress IPs. Calling Sume needs only an API key over HTTPS; for webhooks into your app, verify the signature.
Written by Sume