TikTok hashtag frequency

Hashtag counts with source post IDs. Give your connected LLM the build instructions to create this reusable tool.

ScrapeCreators

treg

Already connected? Set up and tiktok hashtag frequency

Tool specification · Live providers not tested

What you provide: A public TikTok profile or channel identifier, bounded sample size, and any stated comparison inputs.
What you get: Hashtag counts with source post IDs.

How your tool works.

Join profile and post text; extract literal hashtags; normalize case and count appearances.

Your agent writes and saves the Python tool. Recurse supplies eligible API access and cloud execution. You can ask your agent to edit it and run it again.

The output.

Hashtag counts with source post IDs.

The APIs in your tool.

Use eligible APIs through your Recurse balance. You do not need to open a separate provider account or fund a separate wallet for these operations. Operations requiring your own connected account remain subject to availability.

ScrapeCreators$0.00188 / callscrapecreators.tiktok.user.profile
Price evidence and conditions
per_call · 1 credit per 1 call. Checked 2026-07-28. Source: rate_card_api. Confidence: verified.
Price source · API documentation
treg$0.0005 / successful calltreg.tiktok.user.videos
Price evidence and conditions
per_success · 0.0005 USD per 1 call. Checked . Source: inferred. Confidence: documented.
the children's range $0.0005–$0.01476 per hit, 0% markup; you pay the child that served AND every child tried before it that bills a miss (0 of 4 do), up to X-Treg-Route-Max-Cost (default $1 a call). X-Treg-Route-Exclude them, or X-Treg-Route-Waterfall: 0, to pay for one provider only
Price source URL was not captured. · Documentation URL was not captured.

These are dated API unit rates, not a whole-task quote. Your agent checks current availability and costs before execution. Settled provider costs pass through at 1×; preparation and execution compute are charged at 4×.

Build it with your agent.

Your agent asks for missing inputs and a total spending cap before chargeable work.

Read the full build instructions

Build and save a reusable Recurse tool called tiktok_hashtag_frequency.
Inputs: A public TikTok profile or channel identifier, bounded sample size, and any stated comparison inputs.
Execution logic: Join profile and post text; extract literal hashtags; normalize case and count appearances.
Output contract: Hashtag counts with source post IDs.
Declared APIs: scrapecreators.tiktok.user.profile, treg.tiktok.user.videos.
Inspect these APIs' current executable status, native parameters, response examples and costs. Resolve and test response-field mappings before writing dependent steps; supplier response schemas in this research snapshot are incomplete. Do not silently substitute APIs. Implement the sequence, joins, filters and calculations in plain Python with from recurse_apis import call. Validate input and JSON output schemas in tools.yaml; lock dependencies in uv.lock. Keep interpretation outside the tool. Use at most 20 sequential API requests, 64 KiB inputs, 256 KiB results and 300 seconds. Limit fetched pages/posts and truncate evidence explicitly. Return null with a reason for missing fields; do not invent dates, contacts, prices or counts. Create success, empty, malformed-response and provider-error tests. Ask me for the missing inputs and one total spending cap before chargeable preparation. Build the standard source archive and perform Recurse's scoped HTTP upload; never send inline source to private_stage. Inspect the prepared function before private_call. Reuse prepared source for later invocations and retain its version ID. If this interface cannot build files and perform the upload, explain the missing capability and provide the source project for a capable interface. Return the receipt and structured result here. Do not publish, send messages or start ongoing monitoring.

Before you start.

Your interface needs file creation, source bundling and scoped HTTP upload as well as a Recurse connection.

Limits and validation

20 sequential API requests, 300 seconds, 64 KiB input and 256 KiB result per private run.

A connected Recurse account and sufficient wallet funds are required.
Authoring requires file creation, source bundling and scoped HTTP upload in addition to MCP.
Public data may be incomplete, stale, unavailable or sample-limited.
Recheck current API access, prices and response-field mappings before paid execution.
A fresh invocation is required for a fresh observation; no background scheduler is included.

This specification was checked against API metadata; a ready-made implementation is not included. Live provider execution has not been tested.