Python API compatibility gaps

[gtema]

This is the umbrella issue for tracking python-rust API compatibility (missing implementation)

A dedicated document (part of the project documentation) must be created describing compatibility matrix

Category	Missing endpoint(s)	Typical HTTP actions
Service catalog	/v3/services (list, create, show, update, delete)	GET / POST / GET {id} / PATCH {id} / DELETE {id}
Endpoints	/v3/endpoints (list, create, show, update, delete)	GET / POST / GET {id} / PATCH {id} / DELETE {id}
Regions	/v3/regions (list, create, show, update, delete)	GET / POST / GET {id} / PATCH {id} / DELETE {id}
Limits	• /v3/limits (list, show) • /v3/limits-model (model discovery) • Unified Limits API (/v3/limits with include_limits flag, /v3/unified-limits if present)	GET / GET {id} / GET (with query)
Project tags	/v3/projects/{project_id}/tags (list, add, delete)	GET / PUT / DELETE
Application credentials (v3.10)	• /v3/users/{user_id}/application_credentials (create, list) • /v3/users/{user_id}/application_credentials/{app_cred_id} (show, update, delete)	POST / GET / GET {id} / PATCH {id} / DELETE {id}
Access rules (read‑only, v3.13)	/v3/users/{user_id}/access_rules (list)	GET
System role assignments	/v3/system/role_assignments (list)	GET
Project hierarchy	/v3/projects/{project_id}/parents, /v3/projects/{project_id}/subtree, create/delete subtree, list parents, etc.	POST / DELETE / GET
OS‑INHERIT – role inference list	/v3/role_inferences (list)	GET
OS‑TRUST (trusts)	/v3/OS-TRUST/trusts (CRUD)	POST GET PATCH DELETE
OAuth2	/v3/OS-OAUTH2/* (token exchange, introspection, etc.)	Various