TikTok trend search then import over Sume MCP: $0.10 + $0.15
Searching TikTok trend metadata costs about $0.10 and importing one video about $0.15 over Sume MCP, so a find-and-mirror step is about $0.25 before generation.
Finding a trending TikTok and mirroring it into Sume costs about $0.25: roughly $0.10 for one trending-videos_search and roughly $0.15 for one media-imports_create. Both numbers come from the tool descriptions in Sume's MCP server code, which call them estimates, so run dry_run to see the figure for your call.
The search is discovery only. It returns metadata and does not download or mirror video. The import is what turns a TikTok or Instagram URL into a durable media.sume.com URL you can pass to later tools.
Cost and limits per step
| Step | Tool | Cost | Limits |
|---|---|---|---|
| Discover | trending-videos_search | About $0.10 per search | Metadata only; production requires a query |
| Mirror | media-imports_create | About $0.15 per accepted import | TikTok and Instagram public video URLs; about 2 GB cap |
| Collect | jobs_wait, then media-imports_get | Read | Returns the media.sume.com URL |
| Unsupported | YouTube and other hosts | None | Rejected with unsupported_platform in v1 |
Run it with a spend cap
The import is a paid write: it needs an idempotency_key, and it accepts dry_run and max_spend_usd (tools and gates). Preview first, then submit once, then wait with jobs_wait. If a wait slice expires, call jobs_wait again; do not resubmit the import.
Both tools need a session that can see paid tools, so a read-only OAuth token will not work. Use mcp:write or an API key, as the hosted MCP docs explain.
Arithmetic for a batch
- One search plus one import: about $0.10 + $0.15 = $0.25.
- One search plus five imports: about $0.10 + 5 x $0.15 = $0.85.
- Generation after the import is extra and is priced by the tool you call next.
- Use
max_spend_usdso a loop cannot import more than you planned.
Sources
Related posts
More in Agents
- What did my seller agent spend? Read Sume usage by thread
Amazon's Seller Assistant plugin logs its actions with audit trails. For the media your agent made through Sume, read the cost by thread_id and run_id.
- Who authorizes agent spend on Sume: mcp:write, key and balance
On Sume, spend is authorized by the token: mcp:read hides paid tools, mcp:write allows them, and an API key sees all. There is no mcp:paid scope.
- x402 upto vs exact: how each maps to a Sume spend cap
Apify's x402 upto charges actual usage up to an allowance; exact takes a fixed $1.00 deposit and refunds the rest. Sume's analogue is a per-call spend cap.
- 200 from an Action run call: replay or skipped? Read the receipt
A 200 on POST /v1/actions/:id/runs means an idempotency replay or a skipped run. Branch on status, idempotency_hit and skip_reason, not on the HTTP code.
Written by Sume