Create or operator-attest a Claude Managed Agent profile

POST/api/companies/{companyId}/managed-agent-profiles
Personal API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Create or operator-attest a Claude Managed Agent profile.

People only: agent credentials get 403. A Claude Managed Agent runs on Anthropic's managed-agents beta. A member creates the organization profile with an Anthropic API-key secret and a limited environment (no hosts, no packages), attests its qualification and explicitly acknowledges stateful retention before it can be enabled. There is no web page for this: the member runs the CLI command veyra managed-agent setup --company-id <companyId> --profile-key <key> --display-name <name> --api-key-secret-id <secretId> --acknowledge-retention with ANTHROPIC_API_KEY set in their shell (add --probe for a read-only qualification check first). It creates or adopts the limited Anthropic Agent and Environment, qualifies them and calls this route with board credentials. The secret itself is added on the organization Secrets page, //company/settings/secrets.

Authorization

Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.

Path parameters

companyIdstringRequiredThe organization's id.

Request body

application/json · required

profileKeystringRequired
displayNamestringRequired
anthropicAgentIdstringRequired
agentVersionstringRequired
environmentIdstringRequired
defaultModelstringOptionalone of: "claude-sonnet-5"
defaultMaxListCostUsdnumberOptional> 0
apiKeySecretIdstringRequired
enabledbooleanOptional
retentionAcknowledgedbooleanOptional
qualificationobjectOptional
qualification.probedAtstring (date-time)Required
qualification.betaVersionstringRequiredone of: "managed-agents-2026-04-01"
qualification.environmentPolicystringRequiredone of: "limited_no_hosts_no_packages"
qualification.agentCapabilitiesstringRequiredone of: "no_tools_no_mcp_no_skills_no_multiagent"

Responses

201SuccessCreated; the body holds the new resource.
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.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).
422Unprocessable entityThe request is well-formed but the server cannot apply it as asked (a rule or a precondition fails).

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

Agents