---
title: "SovInfra / SovAPI free inference"
description: "1B tokens for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for SovInfra / SovAPI."
canonical_url: "https://freeinferencing.com/provider/sovinfra_sovapi/"
md_url: "https://freeinferencing.com/provider/sovinfra_sovapi.md"
last_updated: "2026-10-06"
---

# SovInfra / SovAPI

> 1B tokens for new accounts; it does not recur.

## Classification

- **Directory:** Current
- **Free access:** One-time trial
- **Status:** Available now
- **Confidence:** High
- **Payment card:** No
- **Account:** Required
- **Equivalent paid value:** Up to $380.00 once
- **API endpoint:** `https://api.sovinfra.ai/v1`

## Models mentioned

- `sovapi`
- `gemma-4-31b`
- `qwen3.8-27b`

## Limits and terms

```yaml
signup_tokens: 1000000000
token_scope: Shared input/output billing-token allocation
expiry: not_published
requests_per_minute: not_published
exhausted_behavior: No automatic charge; continuing use requires explicitly accepting paid billing.
```

## What happens to your prompts?

**Private.** API content is excluded from persistent retention and secondary model use; per-key volatile prefix caching and content-free billing/security records are documented exceptions.

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: SovAPI inference trial; separate SovAgent chat-history storage is excluded.
  prompt_retention: Not persisted; per-key volatile prefix cache may survive a
    request until eviction or model restart.
  response_retention: Not persisted after processing.
  ordinary_logging: Content-free usage/billing records for 12 months and security
    events for 30 days.
  model_training: Customer inference content is never used to train or improve models.
  product_improvement: No secondary use of inference content.
  human_or_operator_access: Content processed transiently by the EU-operated infrastructure.
  subprocessors_and_routing: EU request chain; infrastructure providers include
    VSHosting, Hetzner and RINF, disclosed in the policy.
  deletion_controls: Account deletion within 30 days; legally required billing
    records retained up to 10 years.
agreements:
  terms_of_service: https://sovinfra.ai/terms
  privacy_policy: https://sovinfra.ai/privacy
```

## Eligibility

```yaml
account_required: true
payment_method_required: false
signup_verification: Registration requests a professional profile URL such as
  GitHub, LinkedIn or a company/personal site.
```

## API compatibility and modalities

- **Compatibility:** OpenAI Compatible
- **Modalities:** Model inference


## Before you build with SovInfra / SovAPI

### Read the classification narrowly

This record 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 account and region. “One-time trial” 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 **Private** because API content is excluded from persistent retention and secondary model use; per-key volatile prefix caching and content-free billing/security records are documented exceptions. 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

- [SovInfra one-billion-token signup trial](https://sovinfra.ai/pricing): Official Pricing
- [SovAPI Terms of Use](https://sovinfra.ai/terms): Official Terms
- [SovAPI model IDs and OpenAI-compatible endpoint](https://arena.sovinfra.ai/): Official Docs
- [SovInfra registration requirements](https://app.sovinfra.ai/register): Official Signup
- [SovInfra API privacy and prefix-cache boundaries](https://sovinfra.ai/privacy): Official Privacy
- [SovInfra product and infrastructure links](https://sovinfra.ai/): Official Product

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.