--- title: "BazaarLink free inference" description: "3 model routes currently listed at zero price. See verified limits, model IDs, privacy terms, and primary sources for BazaarLink." canonical_url: "https://freeinferencing.com/provider/bazaarlink/" md_url: "https://freeinferencing.com/provider/bazaarlink.md" last_updated: "2026-09-19" --- # BazaarLink > 3 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:** Not quantifiable - **API endpoint:** `https://api.bazaarlink.ai/v1` ## Models mentioned - `qwen/qwen3.7-flash:free` - `deepseek/deepseek-v4-flash-0731free:free` - `auto:free` ## Limits and terms ```yaml requests_per_minute: 10 requests_per_day: 50 requests_per_day_after_any_topup: 100 request_quota_cost: Can grow with prompt context and selected model rather than always consuming one unit. paid_fallback: A free-route failure can fall back to a paid route and consume balance unless the caller sends X-Free-Fallback with value false. ``` ## What happens to your prompts? **Partially private.** Prompt TTL, route-specific training, product-improvement scope, and upstream handling remain 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: BazaarLink gateway and free API routes. prompt_retention: The public agreements were located, but no clear API prompt-content TTL was verified. response_retention: not_documented ordinary_logging: Account, usage, security, and service data may be collected; content/metadata separation is not clearly documented. model_training: No route-specific no-training guarantee was found for all free models. product_improvement: General improvement uses are permitted without a precise API-content scope. human_or_operator_access: not_documented subprocessors_and_routing: The gateway routes requests to model providers; upstream terms can apply independently. deletion_controls: General privacy requests exist, but no per-request or upstream deletion guarantee was found. caveat: A legal policy exists, but it does not resolve the central inference-data questions for the free gateway. agreements: terms_of_service: https://bazaarlink.ai/terms privacy_policy: https://bazaarlink.ai/privacy ``` ## Eligibility ```yaml account_required: true payment_method_required: false ``` ## API compatibility and modalities - **Compatibility:** OpenAI Compatible - **Modalities:** Model inference - **Geography:** Taiwan ## Before you build with BazaarLink ### 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 3 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 **Partially private** because Prompt TTL, route-specific training, product-improvement scope, and upstream handling remain 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 9 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 - [Free models](https://bazaarlink.ai/free): Official Product - [API docs](https://bazaarlink.ai/en/docs/api): Official Docs - [Terms](https://bazaarlink.ai/en/terms): Official Terms - [Models API](https://api.bazaarlink.ai/v1/models): Live Catalog - [BazaarLink Terms](https://bazaarlink.ai/terms): Official Terms - [BazaarLink Privacy](https://bazaarlink.ai/privacy): Official Privacy - [BazaarLink Security](https://bazaarlink.ai/security): Official Security - [BazaarLink LLMprobe-engine repository](https://github.com/Bazaarlinkorg/LLMprobe-engine): Official Repository - [About BazaarLink (operator 集聯科技有限公司, Taiwan)](https://bazaarlink.ai/en/about): Official Product ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.