G2 Vendor API

Please help me write a data collection script with the EveryInfra G2 Vendor endpoint (g2/vendor).

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 g2 and action to vendor, and put the parameters inside params.
- Required parameters:
  - url: Specifies the target G2 resource URL or bare slug. For profile, reviews, and alternatives, pass a /products/<slug> URL or product slug; for vendor, pass a /sellers/<slug> URL or seller slug.
- Optional parameters:
  - slug: Specifies the path slug for the target resource: product actions accept the slug following /products/, while vendor accepts the vendor slug following /sellers/. Do not mix slugs across object types.
  - vendor: Specifies either the seller path slug from /sellers/ or a direct vendor page URL. It does not perform a free-text company name search, and vendor action calls must still include the required url parameter.
  - vendor_url: Provides the /sellers/<slug> vendor landing page URL as a compatibility input for vendor targeting. It does not replace the required url parameter on the vendor action.
- Returns one object. Main fields: slug, name, url, description, founded, hq_location, ownership, total_revenue, employees, phone, product_count, total_reviews; 13 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=g2.
- Example request body:
{
  "platform": "g2",
  "action": "vendor",
  "params": {
    "url": "https://www.g2.com/sellers/slack"
  }
}
- 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.