Configure & Manage API Keys¶

MinT uses an API key starting with sk- as the client's identity credential. Enterprise keys are issued through an onboarding session, and configuration is the same as in Community.

Request an API key¶

Enterprise accounts are activated through an onboarding session, and an administrator assigns a workspace and compute quota to your enterprise account; the key is claimed at mint.macaron.im or mintcn.macaron.xin. If you don't have an invitation yet, contact sales: sales@mindlab.ltd.

Configure environment variables¶

After you get a key starting with sk-, set it as an environment variable. For the Chinese mainland region, use the mintcn endpoint:

export MINT_API_KEY=sk-your-api-key-here
export MINT_BASE_URL=https://mint.macaron.im/   # Mainland: https://mintcn.macaron.xin/
export TINKER_BASE_URL=$MINT_BASE_URL
export TINKER_API_KEY=$MINT_API_KEY

Automatic .env loading¶

A .env file in the project root is also loaded automatically, which makes it easy to share config within a team. Example:

# .env
MINT_API_KEY=sk-your-api-key-here
MINT_BASE_URL=https://mint.macaron.im/
TINKER_BASE_URL=https://mint.macaron.im/
TINKER_API_KEY=sk-your-api-key-here

Add .env to your .gitignore to keep the key out of version control.

Verify the configuration¶

python -c "import mint; print(mint.ServiceClient._require_api_key)"

If _require_api_key throws an error or the preflight times out, check that MINT_API_KEY and MINT_BASE_URL are exported correctly, and that mint.macaron.im / mintcn.macaron.xin are reachable.

Permission management and audit¶

Enterprise offers a workspace-based RBAC model, letting you authorize training jobs, datasets, and model weights individually. Every API call and console action is written to the audit store, with configurable retention (up to 1 year).

Credentials in private deployment¶

Private delivery explicitly offers "optional SM-crypto, SSO, AD integration, and log forwarding." The specific protocols and integration paths are negotiated during onboarding between the Mind Lab solution team and the customer's IT, and deployed together with the cluster.

Next steps

Once the key is configured, run step 4 of the Quick Start (run your first training job). For the full list of available environment variables, see Environment Variables.