GitHub Issue search API

Please help me write a data collection script with the EveryInfra GitHub Issue search endpoint (github/search_issues).

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 github and action to search_issues, and put the parameters inside params.
- Required parameters:
  - keyword: A GitHub issue search query for search_issues. GitHub qualifiers work, such as repo:openai/whisper is:pr, is:issue label:bug or author:octocat.
- Optional parameters:
  - sort: Order of the list. repository_issues: created (default), updated or comments. search_issues: best match by default, or comments, created, updated, reactions. forks: newest (default), oldest, stargazers, watchers. (allowed: comments / created / reactions / updated)
  - 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: 30)
- Returns a list of records. Main fields of each record: id (GitHub's numeric ID, as a string), number (Issue or pull request number within the…), url, title, text, state (open or closed), is_pull_request (true for a pull request, false for an i…), is_draft (Whether a pull request is a draft), labels (Label names), comment_count, reaction_count (Total emoji reactions), repository (Repository the row belongs to, as owner…); 21 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=github.
- Example request body:
{
  "platform": "github",
  "action": "search_issues",
  "params": {
    "keyword": "coffee"
  }
}
- Price: $1.92 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.