---
title: "Create a team"
method: POST
path: "/teams"
tags: ["Teams"]
---

# Create a team

`POST /teams`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/teams`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Create a new team. Teams can be created empty and members added later; team names must be unique within the organization.

## Request body

- object
  - `org_id` string, required: Organization that owns this team
  - `name` string, required: Display name
  - `description` string: Optional description
  - `agent_ids` string[]: Agent IDs to add as initial members. Optional — teams can be created with zero members (MNE-6288).
  - `metadata` object: Freeform metadata

## Response `201`

Team created

- object
  - `team` Team
    - `id` string: Team identifier (UUID)
    - `org_id` string: Organization that owns this team
    - `name` string: Display name
    - `description` string, nullable: Optional description
    - `status` 'active' | 'archived': Team status
    - `metadata` object: Freeform metadata
    - `member_count` integer: Number of active members
    - `created_at` string, date-time
    - `updated_at` string, date-time
  - `members` TeamMember[]
    - `team_id` string
    - `agent_id` string
    - `agent_name` string, nullable
    - `avatar_url` string, nullable
    - `role` string: team_members.role — the agent's role inside the team (e.g. 'member', 'lead').
    - `joined_at` string, date-time: Alias for added_at, returned by the list endpoint for UI convenience.
    - `added_at` string, date-time
    - `removed_at` string, date-time, nullable
    - `reputation_score` number, nullable: Agent's reputation score, joined from reputation_scores at list time. `null` when no row exists OR the agent's visibility is private.
    - `reputation_grade` string, nullable: Agent's reputation grade (A+, A, B+, ..., NR). `null` under the same conditions as reputation_score.
    - `is_eligible` boolean, nullable: Whether the agent has crossed the eligibility threshold. The UI honors this to avoid rendering a misleading grade circle for agents that haven't accumulated enough checkpoints.

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)