---
title: "Goethe University AI-ToolLab LLM API free inference"
description: "A recurring no-cost API allowance covering 17 cataloged models."
canonical_url: "https://freeinferencing.com/provider/goethe_ai_toollab/"
md_url: "https://freeinferencing.com/provider/goethe_ai_toollab.md"
last_updated: "2026-09-19"
---

# Goethe University AI-ToolLab LLM API

> A recurring no-cost API allowance covering 17 cataloged models.

## Classification

- **Directory:** Current
- **Free access:** Always-free quota
- **Status:** Restricted access
- **Confidence:** High
- **Payment card:** Unknown
- **Account:** Required
- **Equivalent paid value:** At least €50.00 once
- **API endpoint:** `https://litellm.s.studiumdigitale.uni-frankfurt.de/v1/`

## Models mentioned

- `gpt-oss:20b`
- `gemma3:12b`
- `llama3.1:8b`
- `llama3:8b`
- `llama2:7b`
- `mistral:7b`
- `codellama:7b`
- `ollama_default`
- `all-minilm:33m`
- `bge-large:335m`
- `bge-m3:567m`
- `granite-embedding:278m`
- `mxbai-embed-large:335m`
- `nomic-embed-text:v1.5`
- `paraphrase-multilingual:278m`
- `snowflake-arctic-embed2:568m`
- `snowflake-arctic-embed:335m`

## Limits and terms

```yaml
local_models: free_fair_use
gwdg_models: free_fair_use_dynamic
paid_model_introductory_budget_eur: 50
exhausted_behavior: Access is restricted; user is not charged.
caveat: Azure routes are excluded from the ongoing-free catalog.
```

## What happens to your prompts?

**Partially private.** The gateway says prompts are never stored and logs metadata only, but GWDG-routed handling and deletion controls are not fully documented.

Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data.

## Data governance and agreements

```yaml
data_governance:
  review_status: partial
  plan_scope: Goethe AI-ToolLab gateway, local routes, and qualifying GWDG fair-use routes.
  prompt_retention: The gateway says prompts are never stored.
  response_retention: An equally explicit response-retention statement is absent;
    GWDG routes inherit GWDG handling.
  ordinary_logging: Endpoint/model, timestamp, input/output token counts, success
    status, and access-account data are logged without prompt text.
  model_training: No gateway-specific rule is stated; GWDG qualifying routes
    separately exclude training.
  product_improvement: Content-based improvement is not documented.
  human_or_operator_access: Stored metadata is administratively accessible;
    transient troubleshooting is not fully described.
  subprocessors_and_routing: Local routes use Goethe infrastructure and GWDG routes use Academic Cloud.
  deletion_controls: Prompt storage is excluded, but response, metadata, account,
    and upstream deletion controls are incomplete.
```

## Eligibility

```yaml
account_required: true
eligible_users: Goethe University employees
requirements:
  - valid_HRZ_account
  - completed_EU_AI_Act_training_badge
  - approved_email_request
```

## API compatibility and modalities

- **Compatibility:** OpenAI Compatible
- **Modalities:** Text generation, Embeddings
- **Geography:** Germany

## Before you build with Goethe University AI-ToolLab LLM API

### Read the classification narrowly

This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “Always-free quota” should be interpreted together with the Current directory placement, High confidence, Unknown payment-card status, and the plan-specific sources below.

### Resolve the live model route

The snapshot records 17 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online.

### Match the quota to the workload shape

Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms.

### Preserve billing and privacy boundaries

The recorded payment-card requirement is Unknown, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Partially private** because The gateway says prompts are never stored and logs metadata only, but GWDG-routed handling and deletion controls are not fully documented. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content.

### Follow the evidence, then re-check it

This record links 2 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term.

### Plan fallback without policy drift

A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable.

### Monitor the offer as a dependency

Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity.

### Test one complete request before scaling

Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement.

## Primary sources

- [AI-ToolLab LLM API access](https://gki.studiumdigitale.uni-frankfurt.de/ai-toollab-2-0/ai-toollab-llm-api-access/?lang=en): Official Product
- [GWDG Chat AI privacy](https://docs.hpc.gwdg.de/services/ai-services/chat-ai/data-privacy/index.html): Official Privacy

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.