add-org

Create a new organization on a LiteLLM proxy via POST /organization/new.

77|12|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BerriAI/litellm-skills --skill add-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-org
Source: https://github.com/BerriAI/litellm-skills/tree/main/add-org
Command: npx skills add https://github.com/BerriAI/litellm-skills --skill add-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a new organization on a live LiteLLM proxy by configuring the organization name, budget, and allowed models, enabling centralized access control across teams.

Core Features & Use Cases

  • Collects organization name, budget, and allowed models, then creates the organization via POST /organization/new.
  • Supports optional TPM/RPM limits and future extensions for governance of model access.
  • Use Case: Provision a new department with scoped model access in a single operation.

Quick Start

Ask for the organization name, budget, and allowed models, then run the creation flow to call the API.

Frequently Asked Questions about add-org

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an organization on a LiteLLM proxy?

To create an organization on a LiteLLM proxy, you POST to the /organization/new endpoint with the organization name, budget, and allowed models. This requires curl, a valid proxy URL, and an admin API key to execute the request successfully.

What do I need to set up a budgeted organization in LiteLLM?

Setting up a budgeted organization in LiteLLM requires a valid proxy URL, an admin API key, and curl installed. You must also specify the organization name, budget, and allowed models to provision centralized access control.

Can I limit TPM and RPM when creating a LiteLLM organization?

Yes, you can limit TPM and RPM when creating a LiteLLM organization. The creation workflow supports optional TPM and RPM limits alongside the required budget and allowed models for governance of model access.

What is the best way to provision department access on a LiteLLM proxy?

The best way to provision department access on a LiteLLM proxy is creating a new organization with scoped model access. By configuring the organization name, budget, and allowed models, you get centralized budgeted access control across teams.

Does the LiteLLM organization creation workflow support multiple organizations?

Yes, the LiteLLM organization creation workflow supports multiple organizations. It is designed for onboarding workflows where admins need centralized budgeted access control across multiple orgs through the proxy API.

Why do I need an admin API key to create an organization in LiteLLM?

An admin API key is required to create an organization in LiteLLM because the POST /organization/new endpoint needs authorized access to the live proxy. This ensures only admins can configure budgeted access control for teams.