Agent-native game assets

Agents of a
game studio.

Point your coding agent at one API + MCP server. It generates the images, meshes, textures, motion, and audio your game needs — atomic USD billing, self-hosted models, no lock-in.

agent · niua mcp
// a mossy stone golem, game-ready
warmingrunningsettled

no tokens · pay per generation, to the cent · works with any MCP client

generatingNIUA-generated samurai conceptimage · .png
image
mesh
texture
voice
motion

6 outputs · one session · nothing to click — just look

The session continues

One agent. Every asset. Same session.

Keep scrolling — the agent keeps working. Each call is another modality on the same production lane. This isn't a feature list; it's the run.

Mesh · geometry

agent ▸ niua.mesh({ from: image, res: 1024 })

Mesh · PBR texture

agent ▸ niua.texture({ mesh, style: "weathered stone" })

Motion · text-to-motion

agent ▸ niua.text2motion({ text: "heavy idle, slow breathing" })

Voice + sound effects

agent ▸ niua.sfx({ "a low granite roar" })
assembled this session:1 image1 meshPBR textureidle motionvoicesfx— a game-ready character, from one agent.

Point yours at it

Three lines in.

Your agent, raw HTTP, or the playground. The endpoints you saw above are the whole surface — documented in full at /docs.

mcpmcp add niua https://mcp.niua.ohao.tech
apicurl api.niua.ohao.tech/api/v1/generate/image -d '{"prompt":"…"}'
uiopen the playground → generate in the browser

Why it's real infrastructure

Built like a payments API, not a toy.

10
modalities behind one REST API + MCP server
USD¢
atomic per-generation billing — no tokens, seats, or lock-in
self-host
permissively-licensed models you can run yourself
/v1/models
live latency, success rate + price per model — one public catalog

Your next asset is one message away.

Pay only for what you generate. No card on file to sign up.

Questions

Things worth knowing.