Instagram Hashtag API

Please help me write a data collection script with the EveryInfra Instagram Hashtag endpoint (instagram/hashtag).

How the endpoint works:
- 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 instagram and action to hashtag, and put the parameters inside params.
- Required parameters:
  - hashtag: Accepts an Instagram hashtag string without the leading # symbol (e.g., coffee) to list associated posts or reels. This parameter requires a hashtag name rather than an account handle.
- Optional parameters:
  - results_type: Selects the content type for discover and hashtag: omit it for regular posts, or pass reel or reels for short videos. posts cannot be passed explicitly, and any other value returns 422. (allowed: reel / reels)
  - tag: Provides compatibility input for the hashtag action, automatically stripping leading # symbols. When both are supplied, hashtag takes precedence. Public requests must still include the required hashtag parameter.
  - limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 30)
- Returns a list of records. Main fields of each record: post_id, url, text, media_type, like_count, comment_count, view_count, author_username, author_name, posted_at, location, id; 21 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=instagram.
- Example request body:
{
  "platform": "instagram",
  "action": "hashtag",
  "params": {
    "hashtag": "photography"
  }
}
- 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.