Naver Reviews API

Please help me write a data collection script with the EveryInfra Naver Reviews endpoint (naver/reviews).

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 naver and action to reviews, and put the parameters inside params.
- Required parameters:
  - url: Specifies the target URL for Naver requests. The post and comments actions accept specific Blog or Cafe post URLs, whereas the reviews action requires Naver Place merchant links containing /restaurant/MERCHANT_ID or /pla…
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 50)
- Returns a list of records. Main fields of each record: id, place_id, place_name, text, rating, rating_scale, visited_at, posted_at, visit_count, view_count, item_name, origin_type; 19 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=naver.
- Example request body:
{
  "platform": "naver",
  "action": "reviews",
  "params": {
    "url": "https://map.naver.com/p/entry/place/2048090882"
  }
}
- 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.