Google Trends Search interest over time API

Please help me write a data collection script with the EveryInfra Google Trends Search interest over time endpoint (google_trends/interest_over_time).

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 google_trends and action to interest_over_time, and put the parameters inside params.
- Required parameters:
  - keywords: A list of 1 to 5 search terms to compare, such as ["openai", "anthropic"]. Each term is at most 80 characters and 10 words.
- Optional parameters:
  - country: A two-letter country code such as us, gb or jp for where to measure interest. Leave it out for worldwide.
  - language: A two-letter language code such as en or ja. Usually not needed.
  - search_type: Which Google search to measure: web (default), news, youtube, images or shopping.
  - time_window: The period to cover: day, week, month (30 days), quarter (90 days), year (12 months, the default) or five_years.
  - limit: The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- Returns a list of records. Main fields of each record: time (Start of this point in time, UTC, ISO 8…), date_from (First day of this point (YYYY-MM-DD)), date_to (Last day of this point (YYYY-MM-DD)), values (Interest per keyword at this point, 0 t…), period_averages (Average interest per keyword over the w…), partial (True when this point is still being cou…).
- Example request body:
{
  "platform": "google_trends",
  "action": "interest_over_time",
  "params": {
    "keywords": [
      "openai",
      "anthropic"
    ]
  }
}
- Price: $8.81 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.