> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opper.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a project

> Creates a project in the calling organization. Requires the `projects:write` scope.



## OpenAPI

````yaml post /management/v1/projects
openapi: 3.1.0
info:
  description: Schema-driven generative API that orchestrates LLM-powered workflows.
  title: Task API
  version: 3.0.0
servers:
  - description: Production
    url: https://api.opper.ai
  - description: Local development
    url: http://localhost:8080
security:
  - BearerAuth: []
tags:
  - description: Schema-driven function management and execution
    name: Functions
  - description: OpenAI-compatible chat completions
    name: Chat
  - description: OpenAI Responses API compatible endpoint
    name: Responses
  - description: Google-compatible interactions endpoint
    name: Interactions
  - description: Model registry and capabilities
    name: Models
  - description: Synchronous image generation
    name: Images
  - description: Text-to-speech and speech-to-text
    name: Audio
  - description: Asynchronous video generation
    name: Videos
  - description: Reusable file storage for media inputs and generated outputs
    name: Files
  - description: Async generation status and downloads
    name: Artifacts
  - description: OpenAI-compatible embeddings
    name: Embeddings
  - description: Recorded HTTP request/response generations
    name: Generations
  - description: System health and status
    name: System
  - description: Roundtable endpoint — fan out a query to multiple LLMs and combine results
    name: Roundtable
  - description: Web search, fetch, and other utility tools
    name: Tools
  - description: Caller identity, credits, and usage
    name: Account
paths:
  /management/v1/projects:
    post:
      tags:
        - Management
      summary: Create a project
      description: >-
        Creates a project in the calling organization. Requires the
        `projects:write` scope.
      operationId: createManagementProject
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateManagementProjectRequest'
        required: true
      responses:
        '201':
          content:
            application/json:
              schema:
                properties:
                  data:
                    $ref: '#/components/schemas/ManagementProject'
                  meta:
                    description: >-
                      Empty for a single resource. Endpoint-specific context
                      appears here rather than as a sibling of `data`.
                    type: object
                type: object
          description: Successful response
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Bad request
        '401':
          description: Unauthorized - missing or invalid API key
        '403':
          content:
            application/json:
              schema:
                properties:
                  allowed_plans:
                    description: Present on the plan-gate refusal.
                    items:
                      type: string
                    type: array
                  current_plan:
                    description: Present on the plan-gate refusal.
                    type: string
                  error:
                    type: string
                  required_scope:
                    description: Present on the scope refusal.
                    type: string
                type: object
          description: >-
            Either the organization's plan does not include the Management API
            (`current_plan` / `allowed_plans` are returned), or the token lacks
            the scope this endpoint requires (`required_scope` is returned).
            Presenting a runtime `op-…` key instead of a management `op-mak-…`
            token also lands here.
        '409':
          content:
            application/json:
              schema:
                properties:
                  error:
                    type: string
                type: object
          description: A project with this name already exists in the organization.
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Internal server error
      security:
        - ManagementBearer: []
components:
  schemas:
    CreateManagementProjectRequest:
      properties:
        description:
          type: string
        name:
          type: string
      required:
        - name
        - description
      type: object
    ManagementProject:
      properties:
        created_at:
          format: date-time
          type: string
        description:
          type: string
        name:
          type: string
        uuid:
          type: string
      required:
        - uuid
        - name
        - description
      type: object
    ErrorResponse:
      properties:
        error:
          properties:
            code:
              type: string
            details:
              description: Any value
            message:
              type: string
          required:
            - code
            - message
          type: object
        meta:
          type: object
      required:
        - error
      type: object
  securitySchemes:
    BearerAuth:
      bearerFormat: API Key
      description: API key authentication. Pass your API key as a Bearer token.
      scheme: bearer
      type: http
    ManagementBearer:
      bearerFormat: Management API Key
      description: >-
        Management API authentication. Pass an `op-mak-…` management token as a
        Bearer token. Runtime `op-…` API keys are rejected with 403 — they
        belong on the data-plane endpoints. Mint a management key from the
        platform UI under Settings → API keys.
      scheme: bearer
      type: http

````