Viggle API
$0.01 for new accounts; it does not recur.
https://apis.viggle.ai/v1Models mentioned
JST-2MiniMax H3Equivalent paid value
How this was valued: Face value of 100 signup credits at $0.01 each; the balance can fund up to 100 generated seconds on $0.01/second operations.
Limits and terms
- Signup Credits
- 100
- Credit Value USD
- 0.01
- Signup Value USD
- 1
- Recurrence
- No
- Expiry
- not published
- Rate Limits
- not numerically published
- Maximum Minimax H3 Or Single Character Remix Seconds
- 100
What happens to your prompts?
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.
- 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.
Governing documents
- Terms Of Use
- https://viggle.ai/terms-of-use
- Privacy Policy
- https://viggle.ai/privacy-policy
Eligibility
- Account Required
- Yes
- Payment Method Required
- not documented
Primary sources
Before you build with Viggle API
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label 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 region.
Resolve the live model route
This snapshot records 2 model IDs. Match the exact ID against the provider's live catalog before using it in code; zero-price routes and aliases can rotate while an older documentation page remains online. The recorded base endpoint is https://apis.viggle.ai/v1, but the provider's current API reference remains authoritative for paths, authentication, and request shape.
Confirm account and billing boundaries
An account is required, so public catalog evidence cannot by itself prove the limits, balance, or billing behavior attached to your workspace. The reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. 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 “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. 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 5 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.