AI and your writing
faibl uses AI for specific authoring and review tasks. It is optional: planning, writing, saving, reviewing authored prose, and export remain available without generating text.
What a request can contain
A request can include your direction, the selected field or scene, and relevant context such as the outline, nearby prose, Story knowledge, characters, world facts, and continuity notes. Required context is not silently clipped.
What faibl stores
faibl stores generated candidates and immutable prompt snapshots with task, model route, template version, context references, revision identifiers, and output so results remain inspectable. Usage records store provider/model identity, tokens, cost, and safe provider metadata.
How OpenRouter is constrained
Hosted requests use faibl’s server-side OpenRouter key and are configured to deny data collection and require Zero Data Retention endpoints. If an eligible route is unavailable, the request fails instead of silently weakening that policy. OpenRouter still records request metadata such as token counts and latency.
How the author stays in control
Generated prose is a candidate. It does not overwrite authored or approved text until the author explicitly accepts or edits it. AI cannot approve a scene, chapter, or book.
How credits work
faibl meters use to the author’s account even though all hosted requests use one managed provider credential. The current balance, reservations, settled use, and provider cost are recorded server-side; the browser cannot grant itself credits.