Spaces
A Space opens by link; visitors need neither a wallet nor a key — requests go through the platform server.
Templates
Three templates: chat-llm (chat for LLMs), diffusion-image (text → image), diffusion-video (text → video). The template follows from the task type — you cannot put a chat on a diffusion task: their request shapes differ, and a mismatch would be an unexecutable request, not a cosmetic issue.
Visibility
Public — a card in the shared Spaces catalog, the page is open to search engines. Link-only — opens for anyone with the direct link; never listed, closed to indexing, and the link itself is unguessable. Private — owner preview only: the page is not served to visitors and no inference runs through it.
System prompt
The prompt is stored on the platform and mixed in on the server for requests arriving the normal way — a Space visitor never sees it. Mind the boundary: a client that sends its own system message or a ready-made request envelope replaces the owner’s prompt. For chat it is the assistant’s persona; for images and video it is a permanent style prefix to the generation prompt.
The Space key
Each Space has its own service key — it never reaches the browser. Its default daily budget is stricter than a user key’s: 1 000 requests. The key is revoked together with the Space.
Generation parameters
The parameter panel is built from the task model’s manifest: every model has its own knobs and ranges. The owner can set defaults — they apply to every visitor request until the visitor changes a value.
Limit
The number of Spaces per neuronet is set by the platform: 3 by default, raised to 10 on this testnet; a plan can set its own value. At the limit, creation returns a space-limit error; deleting an unused Space frees a slot.