--- title: "Mancer AI free inference" description: "1 model route currently listed at zero price. See verified limits, model IDs, privacy terms, and primary sources for Mancer AI." canonical_url: "https://freeinferencing.com/provider/mancer_ai/" md_url: "https://freeinferencing.com/provider/mancer_ai.md" last_updated: "2026-09-19" --- # Mancer AI > 1 model route currently listed at zero price. ## Classification - **Directory:** Current - **Free access:** Free model routes - **Status:** Available now - **Confidence:** High - **Payment card:** No - **Account:** Required - **Equivalent paid value:** Not quantifiable - **API endpoint:** `https://neuro.mancer.tech/oai/v1` ## Models mentioned - `mytholite` ## Limits and terms ```yaml numeric_quota: not_published official_claim: Free models continue working even with a negative credit balance. ``` ## What happens to your prompts? **Not private.** Default terms permit retention, third-party disclosure, model training, and service improvement unless the user opts out. 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: reviewed plan_scope: Mancer AI hosted inference platform and its catalog of open and proprietary third-party models. prompt_retention: Customer Content may be used and retained to provide, maintain, develop, improve, secure, and enforce the service; no prompt-specific maximum retention period is published. response_retention: Outputs fall within Customer Content under the same unspecified retention and use policy. ordinary_logging: Account, request, security, fraud, usage, and service information is retained while the account exists and afterward as needed for claims, fairness records, and legal requirements. model_training: Mancer's standard terms allow it to train models with Customer Content and to provide content to third parties for their business purposes unless the user follows the platform's opt-out process. product_improvement: Customer Content may be used to develop and improve Mancer's services by default. human_or_operator_access: Retained content can be processed for development, improvement, security, abuse prevention, support, and legal purposes; no operator-blind commitment is offered. subprocessors_and_routing: Requests may use multiple open-source or proprietary models with their own licenses and restrictions; third-party content access is allowed by default unless opted out. deletion_controls: A platform opt-out is offered for future training and third-party business access. Account deletion does not guarantee immediate removal of all violation, claim, or legally required records. caveat: Training and third-party business use are opt-out, not opt-in, and the public documents provide no fixed inference-content retention period. agreements: terms_of_use: https://mancer.tech/terms privacy_policy: https://mancer.tech/privacy ``` ## Eligibility ```yaml account_required: true payment_method_required: false ``` ## API compatibility and modalities - **Compatibility:** OpenAI Chat Completions, OpenAI Completions, OpenAI Models - **Modalities:** Text generation ## Before you build with Mancer AI ### 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. “Free model routes” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 1 model ID. 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 No, 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 **Not private** because Default terms permit retention, third-party disclosure, model training, and service improvement unless the user opts out. 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 6 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 - [Mancer AI](https://mancer.tech/): Official Product - [Pricing FAQ](https://mancer.tech/pricing): Official Pricing - [Models API](https://neuro.mancer.tech/oai/v1/models): Live Catalog - [OpenAPI specification](https://mancer.tech/resources/api-docs-webui.yml): Official API Reference - [Mancer AI Terms of Use](https://mancer.tech/terms): Official Terms - [Mancer AI Privacy Policy](https://mancer.tech/privacy): Official Privacy ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.