What does Sume's TikTok trending search cost? $0.10 per call, cached

Each accepted call to Sume's trending-videos search reserves and captures $0.10 of usage, and summary_mode: metadata is included in that price. Repeat browse calls may be served from cache so they do not re-hit the upstream provider. Confirm the live price in GET /v1/catalog before you budget.

This is a research utility, not a generator. It returns metadata about public TikTok videos, not downloadable files.

What exactly costs $0.10?

Per the Trending videos page, one accepted call is one charge, whatever limit you pick. In production the legacy contract applies: query is required (up to 200 characters) and limit runs 1 to 50 with a default of 10. So asking for 50 results costs the same as asking for 10, which makes a larger limit the cheaper way to read more rows.

What can I vary without extra cost?

window takes yesterday, this-week, this-month, last-3-months, last-6-months or all-time; production generic queries default to this-month. region is an optional two-letter country code. summary_mode is none, metadata or transcript, and transcript currently returns metadata plus an unsupported warning, so do not plan around transcripts. These are parameters on the same $0.10 call, not add-ons.

What does the cache mean for my budget?

The docs say repeat browse calls may be served from cache. The word is may: it is not a promise that a repeated call is free, and the page does not state a cache lifetime. Budget every call at $0.10 and treat any saving as a bonus. A params.cached flag appears when the rebuild is on; production, which keeps the legacy contract, omits it.

What does a call look like?

This searches one keyword for the week in the US, with metadata summaries, at the maximum production limit:

curl -X POST https://api.sume.com/v1/trending-videos/search \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "vitamin c serum",
    "window": "this-week",
    "region": "US",
    "limit": 50,
    "summary_mode": "metadata"
  }'

What does it not do?

It does not return raw video CDN links, and download values above zero return an unsupported warning because mirroring is reserved for later. So the next step in a trend-to-video workflow is to describe what you saw, then generate your own clip; the recipes page shows the call in context.