Team provisioning API
Provision coordinated multi-agent teams for Collective and Label plan tiers. Each agent in the team receives its own container service, provisioned asynchronously in the background.
Team provisioning requires a Collective plan or higher. Solo plan users are limited to single-agent provisioning via
POST /api/provision.
Plan agent limits
Each plan tier determines how many agents are provisioned in a single team:
| Plan | Agents per team |
|---|
solo | 1 (team provisioning not available) |
collective | 3 |
label | 10 |
Provision a team
Creates a team of agents using a pre-built template. Requires session authentication.
Request body
| Field | Type | Required | Description |
|---|
plan | string | Yes | Plan tier. Must be one of collective or label. |
templateKey | string | Yes | Key of the pre-built team template to use. See list templates for available options. |
Response
{
"success": true,
"teamId": "team-a1b2c3d4e5f6",
"plan": "collective",
"templateKey": "dev-fullstack",
"agentCount": 3,
"message": "Team provisioning started. 3 agents are being deployed."
}
| Field | Type | Description |
|---|
success | boolean | Whether provisioning was initiated |
teamId | string | Unique team identifier (format: team-{hex}) |
plan | string | The plan tier used |
templateKey | string | The template key used |
agentCount | number | Number of agents being provisioned |
message | string | Human-readable status message |
Agent provisioning happens asynchronously after the response is returned. The endpoint confirms that provisioning has been kicked off, not that all agents are running.
Errors
| Code | Description |
|---|
| 400 | Invalid JSON body, missing or invalid plan, or missing templateKey |
| 401 | Unauthorized — missing or invalid session |
Example request
curl -X POST https://api.agentbot.raveculture.xyz/api/provision/team \
-H "Content-Type: application/json" \
-H "Cookie: session=YOUR_SESSION_COOKIE" \
-d '{
"plan": "collective",
"templateKey": "dev-fullstack"
}'
List team templates
GET /api/provision/team/templates
Returns all available pre-built team templates and their categories. Requires session authentication.
Response
{
"templates": [
{
"key": "music-label-ops",
"name": "Label Ops",
"description": "A&R, marketing, and distribution coordination for indie labels.",
"agent_count": 3,
"agents": [
{ "name": "ar-lead", "role": "A&R Lead" },
{ "name": "mktg-agent", "role": "Marketing" },
{ "name": "distro-agent", "role": "Distribution" }
]
}
],
"categories": [
{
"key": "music",
"label": "Music",
"templates": ["music-label-ops", "artist-management", "music-production", "event-production"]
}
]
}
| Field | Type | Description |
|---|
templates | array | Available team templates |
templates[].key | string | Template identifier used in the templateKey parameter |
templates[].name | string | Human-readable template name |
templates[].description | string | Summary of the team composition |
templates[].agent_count | number | Number of agents in the template |
templates[].agents | array | Agent definitions within the template |
templates[].agents[].name | string | Agent identifier |
templates[].agents[].role | string | Agent role |
categories | array | Template categories for organizing templates by use case |
categories[].key | string | Category identifier |
categories[].label | string | Human-readable category name |
categories[].templates | string[] | List of template keys belonging to this category |
Errors
| Code | Description |
|---|
| 401 | Unauthorized — missing or invalid session |
Available templates
Templates are organized into four categories: Music, Developer, Content, and Label.
Music
Label Ops (music-label-ops)
A&R, marketing, and distribution coordination for indie labels.
| Agent | Role |
|---|
ar-lead | A&R Lead |
mktg-agent | Marketing |
distro-agent | Distribution |
Artist Management (artist-management)
Booking, PR, and social media management for artists.
| Agent | Role |
|---|
booking-agent | Booking |
pr-agent | PR & Press |
social-agent | Social Media |
Production Suite (music-production)
Beat research, sample clearance, and release coordination.
| Agent | Role |
|---|
research-agent | Beat Research |
clearance-agent | Sample Clearance |
release-agent | Release Coord |
Event Production (event-production)
Venue research, logistics, and promotion for live events.
| Agent | Role |
|---|
venue-agent | Venue Research |
logistics-agent | Logistics |
promo-agent | Promotion |
Developer
Full Stack Dev (dev-fullstack)
Frontend, backend, and QA agents for software projects.
| Agent | Role |
|---|
frontend-agent | Frontend |
backend-agent | Backend |
qa-agent | QA |
Content
Content Studio (content-studio)
Writer, editor, and publisher agents for content pipelines.
| Agent | Role |
|---|
writer-agent | Writer |
editor-agent | Editor |
publisher-agent | Publisher |
Label (10 agents)
These templates require the label plan.
Label Expanded (label-expanded)
Full label team with 10 agents covering all aspects of label operations.
| Agent | Role |
|---|
ar-lead | A&R Lead |
sync-agent | Sync & Licensing |
marketing-agent | Marketing |
distro-agent | Distribution |
legal-agent | Legal |
finance-agent | Finance |
social-agent | Social Media |
live-agent | Live Events |
pr-agent | PR & Press |
data-agent | Data & Analytics |
Enterprise Dev (dev-enterprise)
Full enterprise development team with 10 specialized agents.
| Agent | Role |
|---|
architect-agent | Architect |
frontend-agent | Frontend |
backend-agent | Backend |
devops-agent | DevOps |
security-agent | Security |
qa-agent | QA |
docs-agent | Documentation |
ux-agent | UX Research |
pm-agent | Product Manager |
analytics-agent | Analytics |