Create Persona

POST /agents/{agent_id}/personas

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.

Parameters

Name	In	Type		Notes
agent_id	path	string (uuid)	required	—

Request body — PersonaCreate

Field	Type		Notes
slug	string	required	—
name	string	required	min length 1 max length 200
prompt_suffix	string | null	optional	—
tool_subset	string[] | null	optional	—
sub_agent_subset	string[] | null	optional	—
model_ref	string | null	optional	max length 200
model_params	object | null	optional	—
attributes	object	optional	—
is_active	boolean	optional	Default true.

Responses

Status	Description	Body
201	Successful Response	PersonaView
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/agents/{agent_id}/personas \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "slug": "string",
       "name": "string"
     }'

Response — PersonaView

Field	Type		Notes
id	string (uuid)	required	—
agent_id	string (uuid)	required	—
scope	workspace | organization | platform	required	—
slug	string	required	—
name	string	required	—
prompt_suffix	string | null	required, nullable	—
tool_subset	string[] | null	required, nullable	—
sub_agent_subset	string[] | null	required, nullable	—
model_ref	string | null	required, nullable	—
model_params	object | null	required, nullable	—
attributes	object	required	—
is_active	boolean	required	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—