--- title: "Requesty LLM Gateway free inference" description: "12 model routes currently listed at zero price. See verified limits, model IDs, privacy terms, and primary sources for Requesty LLM Gateway." canonical_url: "https://freeinferencing.com/provider/requesty/" md_url: "https://freeinferencing.com/provider/requesty.md" last_updated: "2026-09-19" --- # Requesty LLM Gateway > 12 model routes 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:** Up to $1,436.22/mo - **API endpoint:** `https://router.requesty.ai/v1` ## Models mentioned - `nvidia/nemotron-3-super-120b-a12b` - `nvidia/nemotron-3-nano-omni-30b-a3b-reasoning` - `nvidia/nemotron-3-nano-30b-a3b` - `nvidia/nemotron-3.5-content-safety` - `nvidia/nemotron-3-ultra-550b-a55b` - `nvidia/muse-glimmer-30b` - `nvidia/nemotron-3.5-lightning-30b-a3b` - `google/gemma-4-31b-it` - `poolside/laguna-xs.2` - `poolside/laguna-m.1` - `mistral/leanstral-1-5` - `novita/inclusionai/ling-3.0-tiny` ## Limits and terms ```yaml requests_per_day: 200 reset: daily caveat: The Free plan is restricted to zero-priced models; PAYG and BYOK catalogs are separate. ``` ## What happens to your prompts? **Not private.** Free self-service traffic is logged by default and can use upstream models that train on content. 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: Requesty LLM gateway. Self-service and Enterprise logging defaults differ, and each selected model provider has independent data rules. prompt_retention: Self-service plans store prompts and outputs encrypted in the EU for up to 30 days by default. Disabling logging enables gateway ZDR prospectively; Enterprise logging is disabled by default. response_retention: Same plan and logging-setting policy as prompts. Encrypted backups can remain up to 30 days after deletion. ordinary_logging: With content logging disabled, token counts, model ID, and timestamps remain for billing and statutory accounting retention of six years. model_training: Requesty itself does not train models on customer content. The privacy summary says free-plan accounts can be associated with models whose upstream provider trains on content; these are labeled Training Permitted Models and are free. product_improvement: Requesty uses aggregated, de-identified usage for performance, capacity planning, reporting, and service improvement rather than training on identifiable prompt content. human_or_operator_access: Logged content can be accessed for debugging, support, security, and legal obligations under access controls. ZDR prevents Requesty content logging but not upstream provider access. subprocessors_and_routing: Requests go to the selected third-party model provider. Requesty's EU endpoint constrains its own routing and storage geography, not necessarily the provider's inference location or policy. deletion_controls: Workspace admins can disable logging at any time for new requests. Logged content expires within 30 days, backups within another 30 days, and account deletion is available subject to statutory records. caveat: ZDR only controls Requesty's layer. Free Training Permitted Models can allow the final provider to retain or train on prompts even when gateway logging is off. agreements: terms_of_service: https://www.requesty.ai/terms privacy_policy: https://www.requesty.ai/privacy data_processing_agreement: https://www.requesty.ai/dpa ``` ## Eligibility ```yaml account_required: true payment_method_required: false ``` ## API compatibility and modalities - **Compatibility:** OpenAI Compatible, Anthropic Compatible - **Modalities:** Text generation, Safety ## Before you build with Requesty LLM Gateway ### 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 12 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 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 Free self-service traffic is logged by default and can use upstream models that train on content. 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 10 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 - [Pricing](https://www.requesty.ai/pricing): Official Pricing - [Documentation index](https://docs.requesty.ai/llms.txt): Official Docs - [Models API](https://router.requesty.ai/v1/models): Live Catalog - [Requesty Terms of Service](https://www.requesty.ai/terms): Official Terms - [Requesty Privacy Policy](https://www.requesty.ai/privacy): Official Privacy - [Requesty Data Processing Agreement](https://www.requesty.ai/dpa): Official Dpa - [Requesty providers and subprocessors](https://www.requesty.ai/privacy/subprocessors): Official Subprocessors - [OpenRouter models API paid rates for the identical model IDs](https://openrouter.ai/api/v1/models): Router Price Reference - [Requesty homepage stating 70,000+ developers and 90+ billion tokens processed daily](https://www.requesty.ai/): Official Product - [npm download stats for the official @requesty/ai-sdk client](https://www.npmjs.com/package/@requesty/ai-sdk): Package Registry Stats ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.