YouTube Posts by user API

Please help me write a data collection script with the EveryInfra YouTube Posts by user endpoint (youtube/user_posts).

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 youtube and action to user_posts, and put the parameters inside params.
- Required parameters:
  - url: The target URL required by YouTube actions. Use full channel URLs for profile and user_posts, or specific watch?v= and share links for video, comments, and transcript.
- Optional parameters:
  - since: The lower date bound for filtering channel videos, Shorts, or comments. It applies to those lists only.
  - sort: The sort order applied across YouTube actions. For search, accepted values are relevance, newest, most_viewed, and top_rated. For channel videos and Shorts, accepted values are newest, oldest, and popular. (allowed: newest / oldest / popular)
  - limit: The most rows to return in this call, an integer from 1 to 50. 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, url, title, text, author_name, author_username, author_id, author_url, like_count, comment_count, view_count, duration; 13 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=youtube.
- Example request body:
{
  "platform": "youtube",
  "action": "user_posts",
  "params": {
    "url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
  }
}
- 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.