Lemmy Feed API

Please help me write a data collection script with the EveryInfra Lemmy Feed endpoint (lemmy/feed).

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 lemmy and action to feed, and put the parameters inside params.
- No required parameters.
- Optional parameters:
  - instance: Selects the Lemmy instance domain, such as lemmy.world, which is also the default. A full instance URL is accepted but reduced to its hostname. This chooses the query entry point, not a community name.
  - sort: Sorts posts as hot, active, new, top, most_comments, or new_comments. Search and community default to hot, feed defaults to active, and comments defaults to most_comments. (allowed: active / hot / most_comments / new / new_comments / top)
  - top_range: Sets the score window only when sort is top: hour, sixhour, twelvehour, day, week (default), month, threemonths, sixmonths, ninemonths, year, or all. It is not a comment publication-date filter. (allowed: all / day / hour / month / ninemonths / sixhour / sixmonths / threemonths)
  - 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, title, body, url, external_url, community, community_url, instance, author_username, author_url, score, upvote_count; 21 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=lemmy.
- Example request body:
{
  "platform": "lemmy",
  "action": "feed",
  "params": {}
}
- 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.