Douyin Search API

Please help me write a data collection script with the EveryInfra Douyin Search endpoint (douyin/search).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to douyin and action to search, and put the parameters inside params.
- Required parameters:
  - keyword: Search term for the video search action, passed as a string, for example latte art. It finds videos; it is not an account nickname or a video ID.
- Optional parameters:
  - publish_time: Filters video search results by publishing time window. Allowed values are unlimited (default), one_day (last 24 hours), one_week (last 7 days), and half_year (last 6 months). (allowed: half_year / one_day / one_week / unlimited)
  - sort: Sorts video search results. Allowed values are relevance (default), newest for the latest publish date, and most_liked for highest likes. (allowed: most_liked / newest / relevance)
  - limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 10)
- Returns a list of records. Main fields of each record: id, url, text, media_type (Media type: video, or image for image p…), video_url (Video playback URL (signed, expires), like_count, comment_count, share_count, collect_count, author_name, author_id, author_douyin_id (The author's Douyin ID); 40 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=douyin.
- Example request body:
{
  "platform": "douyin",
  "action": "search",
  "params": {
    "keyword": "城市骑行"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.