Dice Search API

Please help me write a data collection script with the EveryInfra Dice Search endpoint (dice/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 dice and action to search, and put the parameters inside params.
- Required parameters:
  - keyword: Specifies the job search term on Dice, such as software developer. Matches tech position job titles and descriptions rather than company IDs or applicant names.
- Optional parameters:
  - location: Filters job listings by geographic location text, such as New York, NY, defaulting to Remote.
  - posted_date: Filters job listings by posting recency: all (default), 24h, 3d, 7d, or 30d. Sets a relative publishing window rather than an application deadline or a YYYY-MM-DD date value.
  - 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: 20)
- Returns a list of records. Main fields of each record: id, url, title, company_name, location, posted_at, employment_type, is_remote, salary, text, employer_type, easy_apply.
- Example request body:
{
  "platform": "dice",
  "action": "search",
  "params": {
    "keyword": "data engineer"
  }
}
- 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.