Generate a client library from the OpenAPI spec

The OpenAPI document was valid but not much use for code generation. No endpoint carried an operationId, so a generator invented method names from the URL and you got get_jobs_types_type_schema. Worse, those names changed whenever a path changed. And every endpoint declared that it needed bearer auth while the document never defined the scheme, so generated clients shipped with no authentication wired at all.

Both are fixed. Every one of the 69 endpoints now has a stable, hand-picked operationId, and the security scheme resolves.

Point a generator at it and the result reads the way you would write it by hand:

uvx openapi-python-client generate --path https://api.rendobar.com/openapi.json

from rendobar_api_client.api.jobs import submit_job, get_job, cancel_job

• Method names come from the endpoint, not the URL shape, and they do not move when a path does.
• The generated client takes a token and sends Authorization: Bearer rb_....
• Three paths that used :id instead of {id} are corrected, so no endpoint is skipped.
• Team endpoints moved to their own Team tag, so they land in their own module instead of inside organizations.

Nothing about the API itself changed. This is the description of it catching up with what was already there, so existing clients are unaffected.

See the API reference for the endpoints, and job types for what you can run.