ITP/TTP Organizational LLM Service

🤖 Purpose

Provide fast and secure access to local large language models
Automate repetitive research tasks like summarization, information extraction, and data cleaning using agentic loops
Support organization-specific fine-tuning and prompt engineering experiments
Offer a unified API gateway with LDAP-based identity for NLP-driven internal platforms

🔐 Quick Start

Obtain your primary API key by authenticating above with your ITP/TTP account credentials.
Send a generation request using Bearer token authentication:

curl -s https://llm.particle.kit.edu/llm/api/generate \
  -X POST \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "llama3",
    "prompt": "What are the latest papers on quantum computing from KIT?"
  }'

If your key is invalid, you will receive a 403 Forbidden response from the gateway.

🔑 Key Management (Admin API)

The following endpoints allow you to list, create, and revoke secondary named keys — useful for CI/CD pipelines or dedicated tools.

Task	Endpoint
List all keys	`/api/keys`	GET
Create a named key	`/api/keys?name=label`	POST
Revoke a specific key	`/api/<key_id>`	DELETE
Revoke all named keys	`/api/logout-all`	POST

All require a valid primary key in the Authorization header:

curl -s https://llm.particle.kit.edu/api/keys \
  -H "Authorization: Bearer YOUR_PRIMARY_KEY"

🛡 Security & Privacy

The authentication requests are logged on our servers.
In case of successful authentication, your queries to /llm/ endpoints are not logged anywhere.
All tokens are 64-character raw hex strings, hashed with SHA-256 before storage. Only hashes are stored on disk.
The primary key is bound to your LDAP DN and persists — it never expires unless you revoke it.

📊 Current Status

The LLM gateway and authentication service are operational. If this page is loading, the frontend is healthy. API access works both internally and over HTTPS externally.