Create a Render web service from a Git repo via the REST API (POST /v1/services)

Documented steps

1. Create an API key in the Render Dashboard Account Settings (https://dashboard.render.com/u/settings). Keys are shown in full only once at creation — store it immediately. Auth for every call: header `Authorization: Bearer <API key>` (https://api-docs.render.com/reference/authentication). Base URL: https://api.render.com/v1 (https://render.com/docs/api).
2. Get your workspace ID: GET https://api.render.com/v1/owners (supports name/email filters, cursor+limit pagination, limit 1-100 default 20). Use the returned owner/workspace id as ownerId (https://api-docs.render.com/reference/list-owners).
3. POST https://api.render.com/v1/services with JSON body. Required: type (enum: static_site, web_service, private_service, background_worker, cron_job), name (unique within workspace), ownerId. For a Git-backed web service also set repo (repository URL, no branch in it), branch (defaults to the repo default branch if omitted), autoDeploy ('yes'|'no', default 'yes'), envVars array, and a serviceDetails object with type-specific config (runtime etc.) (https://api-docs.render.com/reference/create-service).
4. Image-backed services use an `image` object in the body instead of repo fields (https://api-docs.render.com/reference/create-service).
5. 201 = created. Poll the deploy that the creation kicks off via GET /v1/services/{serviceId}/deploys (https://api-docs.render.com/reference/list-deploys).