Eventbrite Search API

Please help me write a data collection script with the EveryInfra Eventbrite Search endpoint (eventbrite/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 eventbrite and action to search, and put the parameters inside params.
- Required parameters:
  - keyword: Defines the city directory slug (for example, ny--new-york) rather than full-text event title keywords. The search action queries events by city and does not include online events.
- Optional parameters:
  - city: Specifies the Eventbrite city path slug (for example, ny--new-york). It takes precedence over location and keyword.
  - location: Serves as a compatibility alternative to city using the same city slug format. It is evaluated only when city is omitted and takes precedence over keyword. It does not accept street addresses or geographic coordinates.
  - 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, text, category, format, start_at, end_at, is_online, capacity, attendee_count, is_sold_out; 15 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=eventbrite.
- Example request body:
{
  "platform": "eventbrite",
  "action": "search",
  "params": {
    "keyword": "ny--new-york"
  }
}
- 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.