Entrim.ai
$10 for new accounts; it does not recur.
Models mentioned
authentication_requiredGLM 5.3 FlashQwen 3.8 27BDeepSeek V4 FlashQwen 3.6 35B-A3BGemma 4 26B A4BGemma 4 31BQwen3 Embedding 8BGPT OSS 120BGPT OSS 20BGLM 5.2Equivalent paid value
How this was valued: Face value of the one-time card-setup credit. It expires 14 days after grant for accounts under the current rule unless a paid top-up stops expiry.
Limits and terms
- Signup Credit USD
- 10
- Recurrence
- No
- Claim Within Days Of Activation
- 7
- Credit Expires After Days
- 14
- Paid Top Up Stops Expiry
- Yes
- Effective For Accounts Activated At Or After
- 2026-09-02T20:00:00Z
- Rate Limits
- applied but not numerically published
What happens to your prompts?
Content records and training are excluded, but derived prompt state may persist in a cross-request cache for up to seven days unless ZDR is requested.
- Plan Scope
- Entrim hosted LLM inference API, including the signup-credit trial.
- Prompt Retention
- Prompts are not written to content logs or stored as records, but derived prompt state may persist in memory or limited persistent caches for up to seven days; ZDR that disables cross-request caching is available on request.
- Response Retention
- Outputs are not written to content logs or stored as records.
- Ordinary Logging
- Token counts, timestamps, request IDs, user agent, cost, IP address, access, error, security, and billing metadata are retained.
- Model Training
- Entrim states it does not use customer prompts or outputs to train models.
- Product Improvement
- Content reuse is excluded; the temporary derived-state cache is used for inference performance.
- Human Or Operator Access
- Terms say Entrim does not monitor or control Customer Content, but do not define operator access to transient caches for incident response.
- Subprocessors And Routing
- Inference runs on Entrim-operated infrastructure in Slovenia; Stripe handles payments and ordinary infrastructure/security providers process operational data.
- Deletion Controls
- GDPR access and deletion requests are available through Entrim; exact operational-log deletion periods vary by purpose.
- Caveat
- The default cross-request cache lasts up to seven days unless ZDR is approved, so protection depends on account configuration.
Governing documents
- Terms Of Service
- https://entrim.ai/terms-of-service/
- Privacy Policy
- https://entrim.ai/privacy-policy/
Eligibility
- Account Required
- Yes
- Email Verification Required
- Yes
- One Account Per Person Or Organization
- Yes
- Payment Card Required To Claim
- Yes
- Card Authorization Hold USD
- 1
- Authorization Hold Released Without Charge
- Yes
Primary sources
Before you build with Entrim.ai
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 11 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. No stable base endpoint is published in this record, so use the linked provider documentation to identify the current request URL and protocol.
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. A payment method is required. A zero-cost allowance can still be useful, but protect the account with provider-side budgets or alerts before sending production traffic. 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”: Content records and training are excluded, but derived prompt state may persist in a cross-request cache for up to seven days unless ZDR is requested. 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 4 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.