Dribbble Shots API

Please help me write a data collection script with the EveryInfra Dribbble Shots endpoint (dribbble/shots).

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 dribbble and action to shots, and put the parameters inside params.
- Required parameters:
  - keyword: Serves as the design work search term in shots queries, or as the fallback designer category in search queries when category is omitted. Can be left empty when only browsing the designer directory.
- Optional parameters:
  - query: Alias for search terms in shots actions. The keyword parameter takes precedence and remains required; this field is not used for category selection in designer directory searches.
  - sort: Sorts design work lists in shots actions; allowed values are popular, newest, and most_viewed. When passed to profile actions, this parameter has no verified sorting effect on user objects and should not be relied upon. (allowed: most_viewed / newest / popular)
  - limit: The most rows to return in this call, an integer from 1 to 60. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 24)
- Returns a list of records. Main fields of each record: shot_id, title, url, author_name, author_url, view_count, like_count, comment_count, tags, image_url, is_pro, is_animated.
- Example request body:
{
  "platform": "dribbble",
  "action": "shots",
  "params": {
    "keyword": "coffee"
  }
}
- Price: $1.39 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.