Documentation Index
Fetch the complete documentation index at: https://docs.llmtune.io/llms.txt
Use this file to discover all available pages before exploring further.
Installation and Setup
This guide covers how to get access to LLMTune and configure your environment for API and dashboard use. For self-hosted or internal deployments, refer to your organization’s deployment guide.Using the Hosted Platform
- Sign up – Go to https://llmtune.io and sign up or log in (email, GitHub, Google, or X).
- Workspace – On first sign-in, a default workspace is created. All resources (datasets, jobs, API keys) are scoped to this workspace.
- API key – In the dashboard, open API Keys, create a key, and copy it. Keys use the
sk_...format. Store the key securely; it is not shown again. - Base URL – For the hosted public API, use
https://api.llmtune.io/v1(or the URL provided by your deployment). For direct platform routes, the base ishttps://llmtune.io/api.
Environment Variables (Integrations)
When integrating with the API from your app or scripts:Authorization header:
SDK / Client Usage
There is no LLMTune-specific SDK in the repository. The API is compatible with OpenAI-style clients:- Chat completions – Use the OpenAI SDK (or similar) with
baseURLset tohttps://api.llmtune.io/v1andapiKeyset to your LLMTune API key. - Custom inference – Use
fetchor any HTTP client to callPOST /models/{modelId}/inferenceandPOST /batch/inferencewith the same auth.
CLI
The repository does not include a dedicated CLI. You can drive the API from the shell usingcurl or a script. Example:
Self-Hosted / Custom Deployments
For deployments that use the platform codebase (e.g. Next.js app + optional infra backend):- Platform (Next.js) – Runs the dashboard and API routes under
/api/. Configure environment variables (database, Stripe, inference backend, etc.) as required by the deployment. - Backend (optional) – If using the separate infra/backend (e.g. for API key storage or worker coordination), set
INFRA_API_URL/BACKEND_API_URLin the platform so it can forward requests. - Worker – Fine-tuning execution may use a worker service (see llmtune-infra/worker). Configure
WORKER_API_URLand related secrets in the platform.
Next Steps
- Quickstart – Create a key, upload data, run a fine-tune, and call the API.
- Authentication – API key creation and security.
- API Overview – Base URL, endpoints, and errors.