--- title: "Puter.js AI free inference" description: "Free to the developer; each end user signs in and consumes their own allowance." canonical_url: "https://freeinferencing.com/provider/puter_js/" md_url: "https://freeinferencing.com/provider/puter_js.md" last_updated: "2026-09-19" --- # Puter.js AI > Free to the developer; each end user signs in and consumes their own allowance. ## Classification - **Directory:** Current - **Free access:** User pays - **Status:** End-user funded - **Confidence:** High - **Payment card:** Unknown - **Account:** Not documented - **Equivalent paid value:** Not quantifiable ## Models mentioned - `google:google/gemma-4-26b-a4b-it` - `google:google/gemma-4-31b-it` - `togetherai:prism-ml/ternary-bonsai-27b` - `infron:deepseek/deepseek-v4-flash:free` - `infron:deepseek/deepseek-v4-flash-0731:free` - `infron:motif/motif-3` - `infron:qwen/qwen3.8-27b:free` - `openrouter:deepseek/deepseek-v4-flash-0731:free` - `openrouter:qwen/qwen3.8-27b:free` - `openrouter:z-ai/glm-5.2:free` - `openrouter:inclusionai/ling-3.0-flash-vl:free` - `openrouter:nex-agi/nex-n2.5-mini:free` - `openrouter:nex-agi/nex-n2.5-pro:free` - `openrouter:inclusionai/ling-3.0-flash-sante:free` - `openrouter:inclusionai/ling-3.0-flash-fin:free` - `openrouter:dots-studio/dots-3-note-preview:free` - `openrouter:liquid/lfm-2.5-2.6b:free` - `openrouter:nvidia/nemotron-3.5-lightning:free` - `openrouter:thinkingmachines/inkling-small:free` - `openrouter:poolside/laguna-s-2.1:free` - `openrouter:thinkingmachines/inkling:free` - `openrouter:poolside/laguna-xs-2.1:free` - `openrouter:cohere/north-mini-code:free` - `openrouter:nvidia/nemotron-3.5-content-safety:free` - `openrouter:nvidia/nemotron-3-ultra-550b-a55b:free` - `openrouter:nvidia/nemotron-3-nano-omni-30b-a3b-reasoning:free` - `openrouter:google/gemma-4-26b-a4b-it:free` - `openrouter:google/gemma-4-31b-it:free` - `openrouter:google/lyria-3-pro-preview` - `openrouter:google/lyria-3-clip-preview` - `openrouter:nvidia/nemotron-3-super-120b-a12b:free` - `openrouter:openrouter/free` ## Limits and terms ```yaml free_monthly_end_user_allowance: amount_not_documented exhausted_behavior: End user is prompted to upgrade. ``` ## What happens to your prompts? **Partially private.** Puter and the selected upstream both process requests, while AI-specific TTL and training protections are unresolved. 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: partial plan_scope: Puter platform and Puter.js user-pays AI integrations; selected upstream model providers also apply. prompt_retention: Puter's general terms permit platform processing, scanning, monitoring, and deletion of User Data, but do not give an AI-request TTL. response_retention: not_documented ordinary_logging: Account, activity, device, cookie, and usage data is collected; AI content logging is not isolated in the public policy. model_training: No universal no-training commitment was found for Puter.js AI requests or all selected upstream providers. product_improvement: Service providers may assist Puter with operation and improvement; content scope remains unclear. human_or_operator_access: Terms permit Puter to monitor and review User Data, including private messages, while upstream AI providers necessarily receive routed content. subprocessors_and_routing: Puter.js routes to third-party AI providers and charges the end user's account; both Puter and the chosen upstream are relevant processors. deletion_controls: Users can delete accounts and stored User Data, subject to the terms; no per-inference upstream deletion control is documented. caveat: The privacy policy says Puter does not collect personal information contained in User Data, while the terms permit operational processing and review. Neither document establishes a model-route-specific privacy guarantee. agreements: terms_of_service: https://puter.com/terms privacy_policy: https://puter.com/privacy ``` ## Eligibility ```yaml developer_provider_key_required: false end_user_account_required: true ``` ## API compatibility and modalities - **Compatibility:** Browser And Node JavaScript Puter.ai.chat() Plus Puter Workers; Not A Conventional Shared Server API Key. - **Modalities:** Text generation, Safety ## Before you build with Puter.js 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. “User pays” should be interpreted together with the Current directory placement, High confidence, Unknown payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 32 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 Puter and the selected upstream both process requests, while AI-specific TTL and training protections are unresolved. 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 8 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 - [User-pays model](https://docs.puter.com/user-pays-model/): Official Docs - [Puter AI](https://docs.puter.com/AI/): Official Docs - [Free LLM API tutorial](https://developer.puter.com/tutorials/free-llm-api/): Official Tutorial - [Model details API](https://api.puter.com/puterai/chat/models/details): Live Catalog - [Puter Terms of Service](https://puter.com/terms): Official Terms - [Puter Privacy Policy](https://puter.com/privacy): Official Privacy - [Puter.js developer site citing 80K+ developers, 130K+ apps powered, and 400K+ installations](https://developer.puter.com/): Official Product - [Puter open-source repository](https://github.com/HeyPuter/puter): Official Repository ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.