Bing Maps Search API

Please help me write a data collection script with the EveryInfra Bing Maps Search endpoint (bing_maps/search).

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 bing_maps and action to search, and put the parameters inside params.
- Required parameters:
  - keyword: What to look for on the map, a business name or category such as coffee or pizza.
- Optional parameters:
  - language: A two-letter language code such as en or de for the returned listings.
  - latitude: The latitude of the map center, from -90 to 90, given together with longitude. Without a center Bing chooses the location, which may not be the city you want.
  - longitude: The longitude of the map center, from -180 to 180, given together with latitude.
  - page: Which page of listings to return, starting at 1, with limit businesses per page (up to 20 pages).
  - limit: The most rows to return in this call, an integer from 1 to 30. 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: rank, place_id (Bing Maps business ID, such as YNF9439D…), name, url, category, address, lat, lng, phone, website, rating (Rating from the review site named in ra…), rating_scale; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=bing_maps.
- Example request body:
{
  "platform": "bing_maps",
  "action": "search",
  "params": {
    "keyword": "coffee"
  }
}
- 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.