Create or operator-attest a remote AgentCore profile

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

Create or operator-attest a remote AgentCore profile.

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
servicestringRequiredone of: "aws_bedrock_agentcore_harness"
configurationobjectRequired
enabledbooleanOptional
retentionAcknowledgedbooleanOptional
qualificationobjectOptional
qualification.suitestringRequiredone of: "aws-agentcore-harness-context-v2"

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