--- title: "LUMI AI Factory Aitta shared inference API free inference" description: "A possible free offer exists, but a decisive term still needs verification." canonical_url: "https://freeinferencing.com/provider/lumi_ai_factory_inference/" md_url: "https://freeinferencing.com/provider/lumi_ai_factory_inference.md" last_updated: "2026-09-19" --- # LUMI AI Factory Aitta shared inference API > A possible free offer exists, but a decisive term still needs verification. ## Classification - **Directory:** Watchlist - **Free access:** Not a free offer - **Status:** Shared Aitta API Live Free Status Unverified - **Confidence:** Medium High - **Payment card:** Unknown - **Account:** Not documented - **Equivalent paid value:** Not quantifiable - **API endpoint:** `https://aitta-api.csc.fi/openai/v1` ## Models mentioned - `LumiOpen/Llama-Poro-2-70B-Instruct` - `Unbabel/Tower-Plus-9B` - `TinyLlama/TinyLlama-1.1B-Chat-v1.0` - `meta-llama/Llama-3.3-70B-Instruct` - `swiss-ai/Apertus-70B-Instruct-2509` - `swiss-ai/Apertus-8B-Instruct-2509` - `MiniMaxAI/MiniMax-M2.7` ## Limits and terms ```yaml requests_per_minute: numeric_value_not_public intended_use: research_and_development production_use_allowed: false service_level: no_SLA ``` ## What happens to your prompts? **Partially private.** Privacy protections are incomplete, conditional, or 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: not_found plan_scope: LUMI Aitta shared OpenAI-compatible research and development API for active LUMI projects. prompt_retention: not_documented response_retention: not_documented ordinary_logging: Rate limiting and project authentication are documented, but request log fields and retention are not. model_training: not_documented product_improvement: not_documented human_or_operator_access: not_documented subprocessors_and_routing: CSC operates the shared Aitta API on LUMI AI Factory infrastructure; additional processing parties are not enumerated. deletion_controls: not_documented caveat: The live shared endpoint and catalog are verified, but no Aitta-specific content-retention, training, operator-access, or deletion policy was found. ``` ## Eligibility ```yaml valid_LUMI_account_required: true active_project_required: true identity_paths: - Haka - MyAccessID - Puhuri - CSC ``` ## API compatibility and modalities - **Compatibility:** OpenAI Compatible - **Modalities:** Text generation - **Geography:** Finland ## Before you build with LUMI AI Factory Aitta shared inference 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. “Not a free offer” should be interpreted together with the Watchlist directory placement, Medium High confidence, Unknown payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 7 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 not documented. 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 Privacy protections are incomplete, conditional, or 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 3 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 - [LUMI AI Factory inference](https://docs.lumi-supercomputer.eu/laif/inference/): Official Docs - [Aitta API status](https://aitta-api.csc.fi/status): Live Status - [Aitta models](https://aitta-api.csc.fi/model): Live Catalog ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.