Mage.space is a browser workspace for images, video and audio, with its own model catalogue, LoRA controls and developer access. This independent SpicyAPI overview explains how its creative-freedom positioning relates to the published content rules, and what private by default actually covers.
A workspace organized around several media types
Mage's official product pages describe image, video and audio generation, reference assets, character tools and model selection. Its about page also lists custom LoRA support and queued generation. This is broader than a single Stable Diffusion interface, and a review of an old version may miss that change.
The workspace keeps several generation tools together. Evaluate whether its models and controls fit your outputs; catalogue size alone cannot establish quality.
Creative freedom still has a published boundary
Mage's marketing emphasizes creative freedom, while its published Terms and Conditions set content restrictions and describe enforcement. They also describe proactive safeguards on public discovery surfaces. Those written boundaries matter when a project's requirements go beyond a general creative workspace.
Those rules should be read directly. A third-party post showing a successful result cannot expand what a service permits, and a model being available does not mean all requests fall within the platform's rules. The current terms are the relevant production reference.
Private by default describes audience visibility
Mage states that new creations remain private until the user chooses to post them. That is valuable for unfinished concepts, personal projects and work you do not want in a public feed. It is also a more specific promise than a generic privacy badge.
The privacy policy separately describes account details, request content, generated artifacts and usage information processed to operate the service. Its terms also grant the operator a broad licence over submitted content. Private-by-default visibility therefore should not be read as a promise of no service-side access or reuse. For unpublished client work, read audience visibility, content rights and deletion terms together.
API and MCP are part of the current offering
Mage's API page advertises image, video and audio generation through one API, with REST and client tooling; its navigation also exposes MCP. It would be inaccurate to describe Mage as a browser-only option or claim that changing services is necessary simply to automate generation.
For a development project, compare the actual interfaces you need, the available task types and the cost of representative calls. An interactive workspace and an application integration can serve different parts of the same project; neither should be assumed to cover every model control automatically.
Model versions and LoRAs determine portability
Mage allows users to bring LoRAs and references into supported work. A LoRA remains tied to the base and version it was trained for, and author permissions govern its use. A broad model menu does not make every file compatible with every entry.
Where SpicyAPI offers a distinct choice
SpicyAPI's catalogue combines image and video models, Spicy editions and compatible LoRA endpoints behind its own developer interfaces. We add no platform content review or extra filter; the selected model's own limits still apply. The useful question is which available endpoint and contract fits your application.
Privacy controls include signed media links, shorter retention and content destruction. Our own systems do not use your inputs or outputs to train models. These are stated controls for a separate service, with no implied Mage account migration or shared model access.