Not a free offerHigh confidence

Hugging Face Inference Providers

Current pricing docs list Free Users with no monthly credits: free accounts must purchase credits or upgrade to PRO. Included monthly credits now go only to PRO ($2.00), Team, and Enterprise.

Visit provider
Free accessNot a free offer
Payment cardUnknown
AccountNot documented
Sources6 first-party links
API endpointhttps://router.huggingface.co/v1

Models mentioned

The offer covers a dynamic catalog, provider-selected route, or model class without stable model IDs in this snapshot.

What happens to your prompts?

Reviewed
Plan Scope
Hugging Face Inference Providers routing layer; each selected inference provider has separate data-security terms.
Prompt Retention
Hugging Face states it does not store request bodies or responses when routing requests. Debugging logs are kept up to 30 days without user data or tokens.
Response Retention
Hugging Face states routed responses are not stored.
Ordinary Logging
Debugging logs are retained up to 30 days but are described as excluding user data and tokens.
Model Training
Hugging Face states it does not store routed user data for training purposes; the selected upstream provider's separate policy still applies.
Product Improvement
No routed prompt or response use for Hugging Face training is disclosed; upstream provider policies must be reviewed separately.
Human Or Operator Access
Hugging Face says request and response bodies are not stored by its routing layer; upstream provider access remains provider-specific.
Subprocessors And Routing
The service is a proxy that sends requests to the selected external inference provider, which is independently responsible for its security and data handling.
Deletion Controls
No routed content is said to be stored by Hugging Face; account personal-data rights are governed by the Hugging Face privacy policy.
Caveat
The Hugging Face proxy policy does not replace the policy of the final inference provider. Automatic routing can change which upstream processes a request.

Governing documents

Primary sources

6

Before you build with Hugging Face Inference Providers

Read the classification narrowly

No current provider-funded hosted inference offer was verified for this record. The label describes the bounded offer supported by evidence on 2026-10-06; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every region.

Resolve the live model route

No stable model ID is recorded. The offer may use a dynamic catalog, a provider-selected route, or a model class, so resolve the current machine-readable ID before writing a fixed production configuration. The recorded base endpoint is https://router.huggingface.co/v1, but the provider's current API reference remains authoritative for paths, authentication, and request shape.

Confirm account and billing boundaries

The public evidence does not settle whether an account is required. Confirm the signed-in flow before treating anonymous or credential-free access as available. The payment-card requirement is conditional or not clearly documented. Treat signup friction and billing exposure as unresolved until the account flow confirms them. 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”: Privacy protections are incomplete, conditional, or not fully documented. 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 6 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.