gem-llm-admin-cli

Manage GEM-LLM users and API keys using a local CLI backed by admin REST endpoints to provision users, issue keys, and revoke access. The CLI executes bash scripts for deterministic command routing to handle administrative tasks safely.

Bulk register GEM-LLM users from a CSV file using the admin CLI's user provisioning feature. This workflow supports selecting a service plan (free, pro, or enterprise) for each batch of users during the automated onboarding process.

Issue and rotate LLM gateway API keys safely using the admin CLI, which exposes the raw_key only at issuance time. This approach prevents raw_key leakage by ensuring sensitive credentials are not stored or displayed after the initial generation.

Yes, checking recent token usage for GEM-LLM users requires loading the GATEWAY_ADMIN_KEY from the /home/jovyan/gem-llm/.env file. This admin key authenticates the CLI's requests to the gateway's REST endpoints to retrieve usage reporting data.

Yes, you can revoke a specific user's API key without impacting others by running the revoke-key command through the admin CLI. This targeted revocation process interfaces directly with the gateway admin REST endpoints to invalidate single credentials.

The API key issuance process shows the raw key only once to prevent credential leakage and enforce secure key lifecycle management. Storing or displaying the raw_key after initial generation would create unnecessary security risks for the GEM-LLM gateway.