Update a persona
Partial update. Journeys reference the persona by id, so renaming one does not disturb anything pointing at it.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the hosted project that contains the server.
Persona ID, as returned by the project's persona list.
Body
Fields to change.
At least one field is required — an empty patch is a 400 rather than a silent no-op.
1–120 characters.
120What this person is, in the product's terms — "finance ops lead", "first-time buyer". 1–120 characters.
120Free-text context the model is grounded in. Up to 2000 characters.
2000Index into the app's fixed shape set. Out of range is a 400 naming the field, not an upstream error about a constant you have never seen.
x >= 0Index into the app's fixed palette set.
x >= 0Response
The updated persona.
A reusable synthetic character. The GOAL lives on the journey, not here — one persona can be pointed at many different tasks.
Durable id — what journeys reference and what every route here addresses.
Stable slug key, shared with exported session data. Useful for correlating transcripts; NOT an address for this API.
How the persona came to exist.
manual, generated, cluster Look, as indices into the app's fixed shape/palette sets. null when unset — the app then derives one from the id.
Epoch milliseconds.
Epoch milliseconds.
Present on cluster-derived personas: the terms the cluster was built from.

