Developer integration guide
Choose the right JST-2 API workflow
Viggle’s developer platform exposes JST-2 scene, character and motion workflows. JST-2 Studio is a separate application that uses the provider’s API. A studio account is not a direct API account.
Match the input and asset to your application
The official developer overview describes scenes from a text prompt or an existing panorama, characters from an image, and motion from text or video. These are distinct tasks. Choose the output your application needs before choosing a request workflow.
Scene results include an SPZ Gaussian splat, a panorama and an initial batch of posed images according to Viggle’s overview. Character generation supplies an animation-ready character; motion workflows provide skeletal animation. Consult the relevant documentation for the current response schema and supported asset formats.
Separate provider credentials from studio credits
For direct integration, obtain credentials through Viggle’s developer platform and follow its authentication instructions. Keep private credentials on your server rather than in a browser bundle. Your provider account controls access and charges for requests you make directly.
The studio has separate site-credit charges: 6 for a scene, 30 for an image-to-character request and 10 for text-to-motion. Registration alone does not add free credits. Provider promotions or research inference-cost figures do not change this studio’s balance or pricing.
Treat generation and asset delivery as separate stages
Viggle’s scene overview describes asynchronous tasks polled by ID, with one task at a time per session. Build your integration around the documented lifecycle rather than treating an accepted request as a completed asset. Read the current documentation for status values and error handling.
The official scene quickstart describes signed output URLs that expire after three hours and task retention of 72 hours. Download needed assets within the documented window rather than treating a task result as permanent storage. Keep preview handling separate from spatial asset delivery.
Use official documentation for workflows beyond the studio
Viggle documents additional scene operations for generating views from a chosen camera and reconstructing a scene from image batches. Those operations are separate from this studio’s text-scene form. The release’s upcoming text-guided expansion should not be mistaken for a supported parameter today.
Start with the official quickstart for your selected task, then validate its input requirements and returned files against your application. This guide deliberately does not invent request paths or payload fields. Provider documentation is the authority for endpoint details, account limits and current pricing.
Questions & answers
Can I use my JST-2 Studio credits with the Viggle API?
No. Site credits pay for operations inside this independent studio. Direct Viggle API requests use the developer account and billing arrangement you establish with Viggle. A studio purchase does not issue provider credentials.
Does the API only generate scenes?
Viggle’s developer platform also documents JST-2 character and motion workflows. Its broader API includes other models and video products. Use the documentation for the specific JST-2 task rather than borrowing assumptions from another model’s endpoint.
Should I send API requests directly from the browser?
Do not expose private provider credentials in public browser code. Use a server-side integration and follow Viggle’s authentication guidance. The studio handles its own provider credentials server-side; it does not ask visitors to paste a direct API key.
Check the original sources.
Reviewed . Model claims are attributed to Viggle; practical suggestions are editorial guidance.