Xmax's platform at platform.xmax.ai is built for developers integrating the X2.0 model into their own products — it centers on API keys, an SDK, and code. If what you actually want is to try X2.0's real-time video transformation capabilities yourself, without writing an integration, this page covers what that requires on the official platform versus a no-code alternative.
Most searches for an Xmax playground alternative come from one of two places. Either you're a non-developer who saw an X2.0 face swap or style transfer clip and want to try it on your own footage, or you're an engineer scoping X2.0 for a product and you'd rather see real output before writing integration code. In both cases the friction is the same: the official platform is an API surface, not a click-and-try demo. There's no hosted sandbox where you paste a photo and watch the transform run on your webcam.
That gap is exactly why a no-code path is useful. You want an Xmax demo you can run in a browser tab in under a minute — the same X2.0 modes, minus the account setup, key management, and SDK wiring. The rest of this page lays out what the official developer route involves, and how to try Xmax without an API key through LiveGen.
To experience X2.0's capabilities through the official developer path, you need to:
uk- prefix)tk- prefix) — since the permanent key should never go to a browser, this typically means writing a small backend@xmaxai/sdk-global JavaScript SDK in a frontend project<video> elementNone of this is unreasonable for a developer building a product feature — it's a normal API integration. But it's a lot of setup if your goal is simply to see what CharX face swap or VibeX style transfer looks like on your own footage.
Both paths run the same X2.0 model. The difference is entirely in what you have to build and manage to reach it.
| What it takes | Official Xmax platform | LiveGen |
|---|---|---|
| Account and key | Permanent uk- key, plus a backend to mint tk- keys | None — nothing to register to start |
| Code | @xmaxai/sdk-global and your own WebRTC wiring | None — it's a finished web app |
| Backend | Needed to keep the permanent key server-side | None on your side |
| Reference images | Upload through the SDK to Tencent COS yourself | Built in — drag and drop in the browser |
| Billing | 1 credit = 1 second, tracked in your own account | 1 credit = 1 second, handled for you; free to start |
| Best for | Building X2.0 into your own product | Trying X2.0 right now |
If your goal sits in the right column, the developer path is more work than the task deserves. If you're building the left column, LiveGen is still a fast way to preview output before you commit engineering time.
Regardless of how you access it, X2.0 offers the same six modes. On LiveGen these carry consumer-facing names, linked below:
These are presets on the same underlying model, so the output quality and latency characteristics are consistent across modes — what changes is the transformation applied. For a plain-language rundown of the model itself, see what is Xmax X2.0.
Understanding the data flow makes it clear why a playground has to be either a coded integration or a hosted app — there's no in-between on the raw platform. X2.0 is a real-time WebRTC pipeline, not batch upload-then-render video generation. In the SDK, the sequence is: create a client, request a getUserMedia camera stream (or convert a video file to a stream), call connect() to open the RTC session and bind an output <video> element, then call set() with a prompt and/or a reference image to start generation. The transform then streams frame by frame into that element until you disconnect().
Authentication is two-tier for a reason. The permanent key stays on your server and is used only to mint short-lived tk- keys through the temporary-key endpoint; those tk- keys carry a TTL and a points limit, reach the browser, and cannot mint further keys. Reference images are uploaded through the SDK's client.files.uploadAndCheckImage helper, which sends them directly to Tencent COS and returns a URL you pass into set(). Billing is metered at 1 credit per second of generation, and new accounts get free credits to evaluate with. A no-code alternative simply performs every one of those steps for you behind the interface. If you do want the full developer walkthrough, the Xmax X2.0 API guide covers it, and how to use Xmax explains the platform end to end.
LiveGen (livegen.ai) is a consumer web app built on Xmax's X2.0 model, made specifically for the case above: you want to use the real-time video capabilities, not integrate them. There's no account-and-API-key flow, no SDK to install, no backend to build for key issuance, and no WebRTC code to write. It's an independent application layer on top of the model, not Xmax's own product.
The flow is: open livegen.ai, allow camera access or upload a video, choose a mode, and the transformation happens live in your browser. It's functionally a playground for X2.0's capabilities, minus the developer setup — which makes it a reasonable first stop whether you're a non-developer who just wants to try it, or a developer scoping out output quality before committing to a full integration.
Note that swapping a real person's face requires their consent, uploads are moderated, and a Content Policy applies — the same responsible-use rules hold whichever path you take.
The developer platform is the right choice when X2.0 is going to live inside something you ship: a product feature, an internal tool, or a workflow where you need programmatic control over sessions, keys, and billing. You accept the setup because you need the control.
The no-code alternative is the right choice when the model is the destination, not a dependency. That covers creators making TikTok video effects or face swap for live streaming, anyone evaluating whether X2.0's quality fits their idea, and developers who want a fast, honest preview before they estimate a build. Trying it first through a hosted app costs nothing and answers the questions that documentation can't.
Xmax's platform at platform.xmax.ai is a developer platform centered on API keys and SDK integration, not a no-code demo tool. LiveGen, built on X2.0, provides the no-code browser experience.
No. LiveGen handles the X2.0 integration on its end — you don't need your own uk-/tk- key pair to use the app.
LiveGen is built on the X2.0 model and exposes its real-time transformation capabilities through a browser interface; check livegen.ai for the current set of available modes.
LiveGen is powered by / built on Xmax's X2.0 model as the underlying technology — it's a consumer application layer on top of the model, not Xmax's own product.
Seeing actual output quality, latency, and mode behavior firsthand is faster than estimating from documentation alone — useful for scoping a project before writing integration code.
The platform is an API and SDK you build against; a playground is somewhere you run the model directly to see what it does. Xmax ships the former, so a no-code app like LiveGen fills the playground role.
Yes. LiveGen runs the X2.0 modes as a finished web app, so you can transform your camera feed or an uploaded video without touching the SDK, keys, or a backend.
It's a practical way to preview X2.0's real-time output and mode behavior on your own footage first, then move to the developer platform once you know the quality fits.
Open your camera and become anyone — free to start, no sign-up for your first try.
Start generating free