Start from a real format
You do not start from a blank page. You start from a template that already matches the kind of artifact you need to make.
Docs
How iterFact works.
Start from a template, preview select formats before account creation, then create an account only when you want to publish, save, and own the artifact. This page explains the real workflow in plain language.
Try select templates freeAccount required only to publishPrivate until you publishOne credit wallet across site + ClaudeUse Atlas as public proofKeep the artifact alive after v1
The short version: AI can help with a first draft. iterFact is where that useful output becomes something you can preview, own, revise, and publish.
What iterFact is
iterFact turns strong first drafts, source files, and structured data into interactive artifacts you can preview, keep, and publish instead of rebuilding from scratch.
Keep one artifact alive
The goal is not disposable AI output. The goal is one artifact that can survive revisions, feedback, and publishing inside the same line of work.
Use AI where it helps
AI can help with extraction, cleanup, and synthesis. iterFact matters after that, when you need control instead of another full rebuild.
What you can try free
Select templates can be previewed before account creation. That is the easiest way to see the real product before you decide to pay or sign in.
Free preview templates
These templates are safe to run before auth because the preview path has no paid inference, no OAuth, and no connected-account requirement.
Real hosted preview
The preview is not a fake image. It is a real hosted artifact with the preview watermark still on it.
Account only at the publish step
You create an account when you want to remove the watermark, save the artifact to your library, and publish it to a clean URL.
What requires an account
Not every template should be anonymous. Some flows need saved state, uploads, paid inference, or connected data from the start.
Uploads and paid inference
If the template needs model work, document parsing, or an uploaded source package, the signed-in workflow starts immediately.
Connected accounts and live data
Templates that depend on APIs, OAuth, or account-linked data stay behind auth because they need real ownership and permissions.
Saved private workspace state
The library is where versions, branches, sharing, and publishing live. If the work starts there, auth happens first.
What happens when you publish
The artifact becomes truly yours at the publish step. That is when iterFact turns from proof into ownership.
The artifact enters your library
Once claimed, the artifact appears in your library as owned work instead of a temporary preview.
The watermark comes off
Publishing removes the preview treatment and turns the artifact into something you can actually send to someone else.
You get a real URL
Published artifacts get a clean hosted URL so the output can be shared, embedded, and revisited like a real product surface.
How credits work
Credits are the single meter across the site, Claude, and the API. The point is to pay for owned creation, not for browsing.
Browse and preview first
Atlas browsing is free. Eligible templates can be previewed free. Credits start when the artifact becomes owned or when a workflow uses paid inference.
One wallet across surfaces
The same credit balance follows you whether you run a template on the site, save from Claude, or use the runtime through the API.
Private until you publish
Credit spend should feel tied to real work: generating owned artifacts, revising them, or publishing them when they are ready.
Where Atlas fits
Atlas is the public proof layer. It shows what the formats feel like before someone commits to their own workflow.
Public proof
Atlas exists so visitors can open real artifacts and understand the format before they ever start building their own.
A discovery surface
Every strong public artifact becomes a discovery point for templates, publishing, and the wider iterFact workflow.
A bridge into owned creation
The best Atlas experience makes the next step obvious: use the format yourself, with your own inputs, and keep the result.
Common questions
The public docs should answer the practical questions quickly: what starts free, what requires an account, and why the product works this way.
Do I need an account before I can see value?
Not always. Select templates let you build and preview first. Account creation happens at the publish step or when the template needs saved/private state.
Why not just regenerate with AI each time?
Because whole-output regeneration is expensive, unstable, and often destructive. iterFact exists so a good first version can improve without starting over.
Is the site the real product or is Claude?
The site is home. Claude, MCP, and the API are useful ways in, but the site is where people browse templates, manage the library, and publish finished work.