Client OS API
Assets and repositories
A Client’s assets and code repositories.
Records of the assets and repositories that belong to each Client.
Operations
| Request | What it does |
|---|---|
| GET /api/clientos/assets | List records (org:viewer or above) |
| POST /api/clientos/assets | Create a record (org:contributor or above) |
| GET /api/clientos/assets/{id} | Get one record (org:viewer or above) |
| PATCH /api/clientos/assets/{id} | Update a record (org:contributor or above) |
| DELETE /api/clientos/assets/{id} | Delete a record (org:admin) |
| GET /api/clientos/repositories | List records (org:viewer or above) |
| POST /api/clientos/repositories | Create a record (org:contributor or above) |
| GET /api/clientos/repositories/{id} | Get one record (org:viewer or above) |
| PATCH /api/clientos/repositories/{id} | Update a record (org:contributor or above) |
| DELETE /api/clientos/repositories/{id} | Delete a record (org:admin) |
Methods and paths come from packages/api-client/openapi.json, which CI regenerates from the route definitions; this site builds its lists from that file. Every /api operation needs a Supabase Auth JWT or a PAT and is rate limited. /health and /health/deep are plain routes outside the spec.