Skip to main content
On Kimi Open Platform, an organization is the top-level unit for account and resource management. You can create multiple projects in an organization and multiple API keys in each project.

Basic Concepts: Organizations, Projects, and API Keys

To find your organization ID, open General under Organization in the console. All projects in an organization share the organization’s account balance and rate limits. API usage is tracked separately for each project, so you can monitor and manage spending by project.

Project and API Key Limits

The project and API key limits depend on your organization verification type: If you need higher limits, fill out the Contact Sales form.

Example Use Cases

Multi-Member Collaboration in a Research Group

An enterprise-verified research group is working on topics A and B. The group administrator creates a project for each topic and invites members to the appropriate projects. Each member creates their own API key in each project they participate in:
Member A works on both topics and therefore creates one API key in each project. Consumption for the two topics is recorded separately in their respective projects, making it easier to track costs by topic. Consumption analysis by API key also helps attribute consumption to individual members. Consumption is tracked separately by project, but all projects still share the organization’s account balance.

Separate Production and Testing Environments

When a product handles both production traffic and automated testing, you can create separate production and testing projects and use each project’s API keys for the corresponding calls. Consumption for production and testing is then recorded separately in their respective projects. Set production budgets and TPM limits based on actual production usage. For the testing project, you can set a lower daily consumption budget to reduce spending from faulty test scripts. Each project’s available TPM still cannot exceed the organization’s TPM.

Organization Management

Manage Organization Members

Only enterprise-verified organizations can invite members. Before inviting members, visit Set Organization Information to keep your organization’s information up to date and complete enterprise verification. To invite a member, open Members under Organization. The platform generates a dedicated invitation link. The invitee can use the link to register and log in to the Open Platform and join your organization.

Configure Organization Balance Alerts

To prevent service interruptions due to an insufficient account balance, configure balance alerts in Organization Management Settings. The default alert threshold is $5 and can be customized. When your account balance falls below the threshold, the platform sends an email to the organization’s registered email address.

Configure IP Whitelist

IP Whitelist is an organization-level security setting on Kimi Open Platform. After you save the configuration, only IP addresses in the whitelist can access APIs under the current organization. API requests from other IP addresses are denied. When the IP whitelist is empty, API requests are not restricted by source IP. When saved, the current list overwrites the existing configuration.

Entry and Permissions

After logging in to Kimi Open Platform, open General under Organization. If the current organization is eligible, the IP Whitelist entry is displayed in the upper-right corner of the page.
IP Whitelist entry on the General page
The entry and configuration permissions are as follows: If you do not see the IP Whitelist entry, check whether organization verification has been completed and whether your account has the required permission. For enterprise organizations, only the organization creator and organization administrators can configure the whitelist.

Fill in the IP / CIDR List

Click IP Whitelist, then enter the allowed IP addresses or CIDR ranges in the IP / CIDR List field.
IP Whitelist configuration dialog
Please note:
  • Enter one item per line. You can also separate items with commas or spaces.
  • You can configure up to 20 items.
  • Only public IPv4 addresses and valid IPv4 CIDR ranges are supported.
  • IPv6 is not currently supported.
  • Saving the whitelist overwrites the existing configuration. Before saving, make sure the list contains every IP address or CIDR range you want to keep.
Example:
You can also write them as:
Before configuring the whitelist, make sure your service uses a fixed public IPv4 egress address. If your service is hosted by a cloud provider or calls the Kimi API through a proxy gateway, NAT gateway, or corporate network, enter the actual public egress IP address used for those calls.

Format Validation

The system validates the input before saving. The following items cannot be saved:
  • IPv6 addresses;
  • private IPv4 addresses or private IPv4 ranges;
  • loopback addresses, link-local addresses, multicast addresses, reserved addresses, and other non-public IPv4 addresses;
  • invalid CIDR ranges;
  • lists with more than 20 items.
Common invalid examples: If the input contains invalid items, the dialog shows an error message and marks the invalid entries. Fix the issues before saving.

Clear the IP Whitelist

To remove IP whitelist restrictions, open the IP Whitelist dialog, clear all entries in the IP / CIDR List field, and click Save. After the empty list is saved, API access under the current organization is no longer restricted by IP whitelist checks.

Scope

The IP whitelist applies to API access under the current organization. After it is configured, all API calls made with API keys under the current organization are subject to this whitelist. If your service is deployed in multiple regions or uses multiple network egress points, add every public egress IP address or CIDR range that needs to access the Kimi API to the whitelist. This helps prevent disruptions to production requests after saving.

View Organization Consumption

The console provides Account Overview and Project Overview pages for reviewing consumption at each level. Click the current project name at the top of the page, select Organization Overview from the project menu, then open Overview under Billing in the left navigation to view total organization consumption and consumption analysis by product, model, project, and API key.
Account Overview in Organization Overview

Project Lifecycle Management

Create a Project

  1. Click the current project name at the top of the page to open the project menu, then click Create Project.
  2. Enter a project name and description, then confirm.
Create Project entry in the project menu
If the console prompts you to add funds to your account, do so before creating a new project. After creating a project, open Project Settings to configure its budgets and rate limits.

Set Consumption Budgets and the TPM Limit

Switch to the target project from the project menu at the top of the page, then open Project Settings in the left navigation and find Project Budget/Rate Limit Settings: For more information about organization rate limits, see Recharge and Rate Limiting.
Project budget and rate limit settings

Manage Project Members and API Keys

Organization administrators can create projects and invite organization members to join them. Project members can create API keys within a project to use its resources. Do not share API keys. Each project member should create their own API key within the project so that your organization can manage project resources effectively. When a member is removed from a project, all API keys created by that member are invalidated.

View Project Consumption

Click the current project name at the top of the page, select the target project from the project menu, then open Project Overview under Project Information in the left navigation to view monthly consumption, daily consumption, project rate limits, and consumption analysis by product, model, and API key.
Project Overview with consumption details and rate limits

Archive a Project

If you no longer need a project, you can archive it. Archived projects appear on the Archived tab of the project list. In the left navigation, open Projects under Organization. Find the target project in the project list and click Settings.
Settings entry in the project list
On the Project Settings page, click Archive Project in the upper-right corner.

FAQ

No. All projects in the same organization share the organization’s account balance.
Not entirely. All projects in an organization share the organization’s rate limits. You can set a TPM limit for each project, but the project’s available TPM cannot exceed the organization’s TPM.
All API keys created by that member are invalidated.
Project budgets are used to track and manage spending. When spending reaches a configured daily or monthly budget greater than 0, subsequent API requests for that project are rejected. Consumption statistics and limit enforcement may be delayed, and charges incurred during the delay must still be paid.
Consumption statistics may take about 10 minutes to update, so recent usage may not appear immediately.