TikTok Profile Scraper API

# Integrate HasData TikTok Profile API

## Task

Add the requested public-profile lookup workflow to this project using HasData TikTok Profile 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 handles and profile fields the application needs.
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:

- Public profile lookup, parameters, and response: https://docs.hasdata.com/apis/tiktok/profile.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/profile` with required `handle`. Accept the documented handle format, with or without `@`; encode it as a query parameter.
- Read the `profile` object. Preserve account IDs as strings and distinguish `username`, `nickname`, and `biography`.
- Treat `bioLink`, verification, business flags, and other optional fields as optional. An absent flag is unknown unless current documentation explicitly defines it.
- Keep follower, following, like, and video counts as separate observations. Follower counts are not follower lists; language and biographies do not establish audience demographics.
- If the requested workflow compares changes, store observation times and snapshots in the application. This endpoint does not return historical growth, schedules, alerts, or a computed engagement rate.
- Returned `hasdataLink` points to a separate posts request. Do not fetch it automatically or treat posts as part of this profile response.
- Handle absent or unavailable public accounts and expiring avatar URLs. Do not turn missing fields into invented contact details or zero values.
- 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 handle validation and encoding, success, missing optional fields, unavailable accounts, timeouts, and errors. Cover ID string preservation and any requested snapshot comparison. 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 profile handle.
- 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.