ILMU API Free Plan
Operated by YTL AI Labs
A finite allowance for new accounts; it does not recur.
https://api.ilmu.ai/v1Models mentioned
ilmu-nemo-nanonemo-superilmu-glm-5.1Equivalent paid value
How this was valued: The published allowance or a defensible paid comparison is not precise enough to calculate.
The 30-day free offer omits its token allocation and model split; paid cards also hide comparable token quantities.
Limits and terms
- Token Allocation
- not published
- Recurrence
- No
- Expires After Days
- 30
- Must Redeem Before Paid Plan
- Yes
What happens to your prompts?
The API page promises memory-only processing, no training, and no third parties, while YTL's broader policy says AI prompts may be collected and used to train AI services.
- Plan Scope
- ILMU API free trial; API-specific and broader YTL disclosures conflict.
- Prompt Retention
- API docs say memory-only then discarded; the broader privacy policy says AI prompts may be collected.
- Response Retention
- API docs say memory-only then discarded; broader service handling is not reconciled.
- Ordinary Logging
- Operational metrics are exposed, but exact metadata fields and retention are incomplete.
- Model Training
- API docs say never used for training, while the broader policy says AI prompts may train AI services.
- Product Improvement
- The specific no-training statement does not fully reconcile broad improvement terms.
- Human Or Operator Access
- Memory-only processing suggests no ordinary stored review, but transient access is not described.
- Subprocessors And Routing
- API docs say Malaysia-only processing and no model-provider sharing; broader recipients are not fully enumerated.
- Deletion Controls
- API content is said to be automatically discarded; account-data controls follow the broader policy.
Eligibility
- Account Required
- Yes
- Phone Verification Required
- Yes
- Residency Restriction
- not documented on current production page
- Seat Limit
- 200 dynamic
- Observed Claimed Seats
- 82
- Observed Remaining Seats
- 118
- Seat Counter Observed At
- 2026-09-13
Primary sources
Before you build with ILMU API Free Plan
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label 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 region.
Resolve the live model route
This snapshot records 3 model IDs. Match the exact ID against the provider's live catalog before using it in code; zero-price routes and aliases can rotate while an older documentation page remains online. The recorded base endpoint is https://api.ilmu.ai/v1, but the provider's current API reference remains authoritative for paths, authentication, and request shape.
Confirm account and billing boundaries
An account is required, so public catalog evidence cannot by itself prove the limits, balance, or billing behavior attached to your workspace. The payment-card requirement is conditional or not clearly documented. Treat signup friction and billing exposure as unresolved until the account flow confirms them. The equivalent paid value shown here prices a documented allowance where possible; it is not cash, guaranteed savings, or protection from overage.
Re-read the prompt policy for your plan
This record classifies the reviewed handling as “Partially private”: The API page promises memory-only processing, no training, and no third parties, while YTL's broader policy says AI prompts may be collected and used to train AI services. Provider policies can distinguish free, paid, enterprise, opted-in, and feature-specific traffic, so verify the governing terms for the exact account and route that will receive your data.
Follow the evidence, then re-check it
The record links 5 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest governing document or live catalog when sources disagree, and submit a correction when a provider changes a material term.
Match the quota to the workload shape
Translate the published allowance into the traffic pattern you actually expect instead of comparing headline totals alone. A daily token pool can look generous while a low requests-per-minute or concurrency ceiling blocks interactive bursts; a high request limit can still fail a long-context job when input, output, or per-request tokens are capped. Separate prompt tokens from generated tokens, include retries and tool calls, and test the largest realistic payload. If the provider documents more than one limit window, the tightest window at your peak load is the practical ceiling. Research, experimental, and community access can also carry eligibility or fair-use constraints that cannot be modeled as a simple number.
Plan fallback without changing the rules
A fallback should preserve more than API syntax. Confirm that the substitute route supports the required modality, context length, streaming behavior, structured output, tools, and safety controls, then compare its prompt-retention and training terms. An OpenAI-compatible request shape does not make providers operationally or contractually equivalent. Decide which errors may trigger a retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. If deterministic output matters, record the model revision and sampling settings; rotating aliases and free-model pools can change behavior even when the endpoint remains available.
Monitor the offer as a dependency
Capture the model ID, response model field, rate-limit headers, usage fields, latency, HTTP status, and any provider request identifier for each test. Watch for authorization failures, quota exhaustion, catalog removal, policy revisions, and dashboard balance changes as separate failure modes. Re-check the provider’s live catalog and governing pages on a schedule proportionate to the workload’s importance, and keep the dated sources that supported your decision. Free capacity is especially suitable for prototypes, evaluations, fallbacks, and bounded workloads when the application can tolerate change; a production dependency still needs observability, an exit path, and an owner responsible for re-verification.
Test one complete request before scaling
Start with the smallest permitted request using the exact credential, model ID, endpoint, and account type you intend to deploy. Record the HTTP status, response headers, usage fields, latency, and any dashboard balance change. Then exercise the failure path: an invalid model, an exhausted quota, or a rate-limit response should fail clearly without silently switching to a paid route. If the provider supports streaming or tool calls, validate those features separately because a free model can expose a narrower capability set than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and avoid sending sensitive data until the observed route matches the reviewed data agreement.