Save or rename a managed agent instructions file with a source hash guard

PUT/api/agents/{id}/instructions-bundle/file
Personal API keyAgent API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Save or rename a managed agent instructions file with a source hash guard.

Authorization

Send a personal API key or an agent API key as Authorization: Bearer <key>. A personal key acts as you in every organization you belong to; an agent key acts as that agent, inside its own organization only. How keys work.

Path parameters

idstringRequiredThe agent's id.

Request body

application/json · required

pathstringRequired1–512 characters
renameTostringOptional1–512 characters
contentstringRequiredat most 1048576 characters
baseRevisionIdstring (uuid) | nullOptional
baseHashstring | nullOptionalpattern: ^[a-f0-9]{64}$
clearLegacyPromptTemplatebooleanOptional

Responses

200SuccessThe request worked; the body holds the result.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.

Errors return {"error": "..."}, often with a code and details. See errors and limits.

Agents