TikTok Comments Scraper API

# Integrate HasData TikTok Comments API

## Task

Add the requested public-video comments or selected-comment replies workflow to this project using HasData TikTok Comments API.
Inspect project instructions, the server-side runtime, existing HTTP client, and tests first.
Follow the project's conventions and preserve unrelated code. No new SDK is required.
Implement only the requested workflow. If the workflow is unclear, ask which public video to use and whether the application needs top-level comments or replies to a selected comment.
Keep the integration as REST API calls; do not replace it with an MCP connection or a custom TikTok scraper.

## References

Read the endpoint documentation before implementing:

- Video comments, replies, and pagination: https://docs.hasdata.com/apis/tiktok/comments.md
- Error handling: https://docs.hasdata.com/api-codes.md
- Documentation index: https://docs.hasdata.com/llms.txt
- Full documentation (fallback): https://docs.hasdata.com/llms-full.txt

Start with the endpoint reference. Use `llms.txt` to find additional pages.
Use `llms-full.txt` only when needed; extract relevant sections instead of loading everything into context.
If a `.md` reference is unavailable, try its HTML URL without `.md`.
If it is still unavailable, ask for the missing documentation rather than guessing.

## Optional agent skill

If the official `hasdata` skill is already available, use its relevant guidance.
Otherwise, if this agent supports skills, ask before installing it in this project:

```sh
npx skills add hasdata/agent-skills --skill hasdata
```

Run from the project directory and select the coding agent in use.
The `hasdata-cli` skill is not required. If installation is declined or unsupported, continue with the docs.
Flag conflicts between skill guidance and current API docs rather than guessing.

## Implementation

- Use `GET https://api.hasdata.com/scrape/tiktok/comments` with required `videoId`. Extract the numeric identifier after `/video/` when accepting a TikTok URL; do not send the full URL as `videoId`.
- Preserve `videoId`, `commentId`, author IDs, and returned comment IDs as strings to avoid numeric precision loss.
- For replies, send the same `videoId` with `commentId` from a comment on that video. This returns the selected comment’s replies in the `comments` array. Retain the requested parent ID in application context.
- For requested pagination, pass `pagination.nextPageToken` as `nextPageToken` when `pagination.hasMore` is true, retaining the video and selected comment context. Tokens are opaque strings; do not calculate offsets.
- Read `comments` and `pagination` separately. Comment `text`, `replyCount`, and optional inline `replies` may be absent. Dedicated reply records need not include `replyCount`.
- Deduplicate records by comment ID. Neither `pagination.total`, a reply count, nor an inline reply selection guarantees a complete discussion or historical archive.
- Do not invent page-size, sorting, language, country, or date-filter parameters. Apply requested sorting or analysis to the collected data in application code.
- Topic grouping, sentiment scores, review priorities, summaries, scheduling, and alerts belong to the application. Preserve original text and allow ambiguous or unclassified results in any requested analysis.
- Embedded authors are limited public attributes. Profile and posts links require separate API requests; do not treat full bios or follower counts as included, and do not expand links automatically.
- Handle empty results and unavailable public videos. Do not infer why a comment lacks text or claim recovery of deleted or private content.
- Handle timeouts and documented errors before reading data. Keep requests server-side. If no suitable runtime exists, discuss options before changing the architecture.

## Credentials

- Implement the integration and mocked tests without requiring a live API key.
- Read `HASDATA_API_KEY` from the project's existing environment or secret store and send it as `x-api-key`.
- If the key is missing before live verification, ask the user to configure it from https://app.hasdata.com/api-keys.
- Never ask the user to paste the key into chat. Check only that it is configured, without printing its value.
- Never put the key in browser code, logs, or version control. Add only a placeholder to the project's example configuration.
- If using a local `.env` file, make sure it is gitignored.
- Send the key only to `https://api.hasdata.com`. Never forward it to documentation, TikTok, media links, bio links, or redirects to another origin.

## Verification

- Add mocked tests for video and comment ID validation, string precision, reply-parent context, pagination, duplicate IDs, missing text, replies without replyCount, empty results, timeouts, and errors. Include a usage example and run local checks.
- With a configured key and explicit user approval, including approval already given for this task, make one live verification request with agreed inputs. A successful TikTok request consumes 10 credits.
- Verify only the requested comments or replies query.
- Validate the HTTP status, documented API status, and response structure. An empty result set can be valid.
- Do not automatically repeat paid requests to obtain a nonempty response or follow pagination during this check.
- Report changed files, setup commands, and test results. State separately whether live verification passed, failed, or was skipped.
- Ask before deploying.