Create Toolkit

POST /toolkits

Role floor

Requires member or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — ToolkitCreate

Field	Type		Notes
slug	string	required	—
name	string	required	min length 1 max length 200
description	string | null	optional	—
scope	workspace | organization | platform | null	optional	—
tools	string[]	optional	—
is_active	boolean	optional	Default true.

Responses

Status	Description	Body
201	Successful Response	ToolkitView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/toolkits \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "slug": "string",
       "name": "string"
     }'

Response — ToolkitView

Field	Type		Notes
id	string (uuid)	required	—
scope	workspace | organization | platform	required	—
organization_id	string (uuid) | null	required, nullable	—
workspace_id	string (uuid) | null	required, nullable	—
slug	string	required	—
name	string	required	—
description	string | null	required, nullable	—
active_revision_id	string (uuid) | null	required, nullable	—
revision_number	integer | null	optional	—
tools	string[]	optional	—
is_active	boolean	required	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—