Skip to navigation

Create team member

View as Markdown

Add a team member (loop agent) to a team. Instructions must be a registry prompt reference with a semver range (e.g. ‘cto@^1.0.0’) — the range is re-resolved on every loop, so newly published satisfying versions apply automatically. No inline instructions.

Authentication

X-API-Keystring

API key supplied via the X-API-Key header. Takes precedence over bearerApiKey when both are present. Listed only on operations that actually accept a key.

OR
AuthorizationBearer

Same organization API key supplied as a Bearer token in the Authorization header (Authorization: Bearer <key>). Compatible with OpenAI-SDK-standard clients. Accepted wherever this scheme is listed on the operation — not every endpoint; if both X-API-Key and Authorization: Bearer are present, X-API-Key wins.

OR
AuthorizationBearer

Supabase session JWT from a signed-in browser session, supplied as Authorization: Bearer <jwt>. This is what the web app sends. It shares the Authorization header with bearerApiKey; the server distinguishes them by the ela_ prefix on API keys.

Path parameters

teamIdstringRequired

Request

This endpoint expects an object.
orgSlugstringRequired
positionTitlestringRequired1-100 characters
stableKeystringRequiredformat: "^[a-zA-Z0-9_-]+$"1-100 characters
instructionsRefstringRequired
reportsToAgentIdstringOptional
toolRefslist of stringsOptional
kbRefslist of stringsOptional
intrinsicSkillslist of enumsOptional
llmProviderIdstringOptional
modelIdstringOptional
variablesmap from strings to anyOptional
targetEnvironmentIdstringOptional
budgetobjectOptional
heartbeatobjectOptional

Response

OK
any
OR
any