LinkedIn Profile search API

Please help me write a data collection script with the EveryInfra LinkedIn Profile search endpoint (linkedin/profile_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 linkedin and action to profile_search, and put the parameters inside params.
- Required parameters:
  - keyword: Specifies the search string, acting as a post search keyword in search, a current job title in profile_search, or a job search term or full job URL in jobs.
- Optional parameters:
  - location: Specifies location text for person profiles in profile_search or job locations in jobs. When keyword in the jobs action is already a full search URL, the URL's embedded criteria take precedence and location is ignored.
  - locations: Accepts a location array as a compatibility alias. Prefer location: this array is not guaranteed to behave the same way, and it is not a way to run cross-country batch searches.
  - 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: 10)
- Returns a list of records. Main fields of each record: id, username, name, url, headline, location, current_company, current_title, avatar_url, is_premium, is_open_profile, email (Email address); 22 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=linkedin.
- Example request body:
{
  "platform": "linkedin",
  "action": "profile_search",
  "params": {
    "keyword": "software engineer"
  }
}
- 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.