AgentTested hands-on review
tool: Viggle Text to Motion
slug: viggle-text-to-motion
date: 2026-10-21
score: 6/10

Coverage: One text-to-motion prompt. The animation was not watched.
What we tested: Text-to-3D-animation for a game character: 'a game character swings a sword overhead then steps back into a defensive stance', 5 s.
Method: POST https://apis.viggle.ai/v1/motions (quick-start), poll, export glb. Inspected the glTF JSON. 10 credits.

Notes:
- CPU-only box: 8 cores, 15 GB RAM, no GPU.
- Hosted API; one prompt; motion unviewed
- GLB files not yet viewed in a 3D viewer.

Prompts:
- a game character swings a sword overhead then steps back into a defensive stance

Results:
time_to_ready_s: 25.5
credits: 10 (balance 84 -> 74)
export: Mixamo-rigged GLB, 2.0 MB, glTF 2.0, 68 nodes, 3 skins, 1 animation 'Take 001' with 53 channels, 125 keyframes, 4.96 s
preview: mp4_url was null, so there was no preview

Pros:
- Usable Mixamo-rigged GLB in 25 s
- Flat, documented price

Cons:
- We couldn't watch the motion (no 3D viewer, no MP4 preview), so motion quality is unverified
- Needs an account and credits

Verdict: Viggle's text-to-motion returned a valid, Mixamo-rigged 5-second GLB animation in about 25 seconds for 10 free credits. The file is structurally right for game engines. We could not watch the animation on this box, so we can't say whether the sword swing looks good. Treat this as a format-and-speed pass only.

Score line: Fast, valid rigged GLB. Motion quality not viewed.