---
title: "Viggle API free inference"
description: "$0.01 for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for Viggle API."
canonical_url: "https://freeinferencing.com/provider/viggle_api/"
md_url: "https://freeinferencing.com/provider/viggle_api.md"
last_updated: "2026-09-19"
---

# Viggle API

> $0.01 for new accounts; it does not recur.

## Classification

- **Directory:** Current
- **Free access:** One-time trial
- **Status:** Current trial
- **Confidence:** High
- **Payment card:** No
- **Account:** Required
- **Equivalent paid value:** $1.00 once
- **API endpoint:** `https://apis.viggle.ai/v1`

## Models mentioned

- `JST-2`
- `MiniMax H3`

## Limits and terms

```yaml
signup_credits: 100
credit_value_usd: 0.01
signup_value_usd: 1
recurrence: false
expiry: not_published
rate_limits: not_numerically_published
maximum_minimax_h3_or_single_character_remix_seconds: 100
```

## What happens to your prompts?

**Not private.** Viggle's API-specific terms require confidentiality and exclude training, but inputs and generated resources are retained by default until deletion with no fixed automatic TTL.

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: Viggle API under API-specific Section 25; consumer app and PINOC
    provisions differ.
  prompt_retention: API User Inputs are treated as confidential and restricted to
    service performance, but uploaded inputs create account resources and no
    fixed storage TTL is published.
  response_retention: Outputs remain retrievable through resource endpoints;
    signed download URLs last one hour and can be reissued, so URL expiry is not
    data deletion.
  ordinary_logging: Account, billing, job, credit-reservation, security, and
    operational records are retained; content-log boundaries are not defined
    separately.
  model_training: API-specific terms prohibit use of User Inputs and API Outputs
    to train Viggle models without prior written consent.
  product_improvement: API-specific terms restrict content use to service
    obligations and override the broader consumer-app improvement license.
  human_or_operator_access: Confidentiality and service-performance restrictions
    apply, but operator-access procedures are not published.
  subprocessors_and_routing: Affiliates and service providers may support the API;
    MiniMax H3 is a separately named model family and route-specific
    subprocessor terms are not published.
  deletion_controls: Resource DELETE operations are available, but no universal
    automatic content deletion period is stated.
  caveat: API-specific protections are materially stronger than the consumer
    terms, yet persistent account resources prevent a zero-retention
    classification.
agreements:
  terms_of_use: https://viggle.ai/terms-of-use
  privacy_policy: https://viggle.ai/privacy-policy
```

## Eligibility

```yaml
account_required: true
payment_method_required: not_documented
```

## API compatibility and modalities

- **Compatibility:** Viggle Rest
- **Modalities:** Video, Image To Video, Text To Video, Motion, 3d, Image / vision


## Before you build with Viggle API

### 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. “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 2 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 Viggle's API-specific terms require confidentiality and exclude training, but inputs and generated resources are retained by default until deletion with no fixed automatic TTL. 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 5 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

- [Viggle API](https://viggle.ai/developers): Official Product
- [API documentation](https://docs.viggle.ai/): Official Docs
- [Terms of Use](https://viggle.ai/terms-of-use): Official Terms
- [Privacy Policy](https://viggle.ai/privacy-policy): Official Privacy
- [Pricing and retention](https://docs.viggle.ai/v1/pricing): Official Docs

## Sitemap

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