Arnict
$5 in credits refresh on a published schedule.
https://api.arnict.com/v1Models mentioned
zai/glm-5.3-flash-uncensoredqwen/qwen3.8-27bEquivalent paid value
How this was valued: Face value of the shared $5 monthly free-usage allowance; unused allowance does not roll over and per-model uses are not additive.
Limits and terms
- Included Credit USD Per Month
- 5
- Reset
- 00:30 UTC on the first day of each month
- Rollover
- No
- Default Requests Per Minute
- 120
- Exhaustion
- Paid requests are refused when available credit is insufficient.
What happens to your prompts?
Prompts and responses are excluded from archives, advertising, and training, but temporary content or derived caches have no fixed public maximum TTL.
- Plan Scope
- Arnict hosted inference, including the recurring personal-account allowance.
- Prompt Retention
- Prompts are processed transiently and not archived as conversation history; short-lived caches may hold content or derived representations until expiry or eviction, with no fixed maximum TTL published.
- Response Retention
- Responses follow the same transient-processing and cache policy and do not appear in the usage ledger as content.
- Ordinary Logging
- Request ID, model, status, timing, token counts, rates, cost, account, security, and support metadata are retained without prompt or response text.
- Model Training
- Arnict states inference prompts and responses are not used for model training.
- Product Improvement
- Inference content is excluded from advertising; operational metadata can support service delivery, billing, security, and troubleshooting.
- Human Or Operator Access
- Arnict keeps no ordinary content archive; access to transient processing or caches is not documented precisely, while support and security records can be accessed as needed.
- Subprocessors And Routing
- Service providers can process data for inference, hosting, authentication, email, security, support, and payments; their exact inference roles are not enumerated publicly.
- Deletion Controls
- Privacy requests go to support; some account, usage, security, financial, fraud, dispute, and legal records can survive account closure.
- Caveat
- The lack of a numeric cache TTL prevents treating this as strict zero retention.
Governing documents
- Terms Of Service
- https://arnict.com/terms
- Privacy Policy
- https://arnict.com/privacy
Eligibility
- Account Required
- Yes
- Email Verification Required
- Yes
- Active Personal Account Required
- Yes
- Payment Method Required
- No
Primary sources
Before you build with Arnict
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 2 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.arnict.com/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 reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. 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”: Prompts and responses are excluded from archives, advertising, and training, but temporary content or derived caches have no fixed public maximum TTL. 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 7 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.