Getting the most from your credits

How credits work, and how to make them go further — in plain language.

Last updated: September 2026

At WritersForge we strive to provide the best assisted-writing experience on the market. We know that you not only want to put words on the page faster, but you want them to be quality words. And in doing so, we want you to get the most out of your credits. Here are a few tips on how to do that.

What a credit is

All AI-assisted writing applications must balance the cost of providing the service with the value it brings to their customers. This is fundamental to any business. But in the world of AI-assisted applications, the costs are hard to predict for one specific reason: the most important part of the service is ‘non-deterministic’.

An easy explanation is as follows:

• A deterministic system (like a web page/app) produces the same type of output based on a given input, every time. Maybe the app is a recipe finder, or a travel guide, or a car search. Regardless, based on the input you type in, it either finds a match (similar), or doesn’t.
• A non-deterministic system (like an AI-assisted plotting/writing system) reasons over what you’ve asked it, and, using its current context, constructs the best answer at that time. It will usually give you the same answer to the same question but may change how it answers from time to time. This variability is key to the question of credit usage.

A WritersForge credit does two things: it covers a small portion of the fixed cost of the deterministic system you log into (i.e. the web app), as well as the variable cost of the non-deterministic system you reason with (i.e. the AI agents).

WritersForge has four custom agents that are tuned to do very distinct but related tasks: help you construct the best story possible. To do this, they have been taught to expect, or ask for, specific things before trying to randomly write a story. Knowing what they expect and having some of the answers worked out ahead of time is the best way to maximize your credits.

But don’t worry if you don’t have all or any of these. The agents can help you figure out everything they need. They’ll just have to spend more time thinking (burning credits) to do so.

Here are the best practices for each agent.

All Agents (and the power of caching)

Caching is a form of short-term memory storage an agent uses when you work with it. It’s sort of like you reading up on a topic right before a quiz. So, when you ask it your next question, it can pull what it already remembers (e.g., your Story Bible) from cache, which requires fewer credits.

When you create new info, it writes that into cache (costing credits) in anticipation of it being used again later. It can never be sure what you’re going to ask it on the next turn, so caching isn’t guaranteed to reduce your credit usage by a certain percentage, but it’s the best chance we have of using them wisely.

The next best thing you can do is to work in one agent as long as possible. Walking away from an agent session for more than about an hour causes the cache to go ‘cold’. This means Anthropic removes the info from its cached memory. Coming back to the point in the story later means the agent has to reload everything in order to ‘remember it’, and this costs more.

StoryBeats

• Put five things in your first message: a premise of one to three sentences, the genre, the length in words (approximate is fine), the format (novel, novella, short story), and the framework you want to use. StoryBeats needs this base to get started.
• If you haven’t chosen a framework yet or are unfamiliar with them, open Framework mapping in the left rail first. It explains seven of them in a few minutes, and there’s a “No framework yet” option if you’re still deciding.
• You can use StoryBeats for brainstorming names, places and world rules too. That groundwork is part of its job, and it’s glad to brainstorm it with you. But again, it costs credits to do this, so use it wisely.
• Try to avoid asking StoryBeats for scenes, dialogue or prose. It maps your structure but doesn’t write the story, so it will point you to another agent, and you’ll have spent a turn for it to tell you this.

StoryPlotter

• Try to have several consecutive beats mapped before planning scenes in StoryPlotter. You don’t have to have the beats for the entire book, but working a section at a time is usually more efficient. (Remember the caching rule.)
• If you already have an idea of how your scenes will go, give Plotter a list all at once. You can type quite a lot into the chat window. This may prevent Plotter from having to ask another question.
• You can rearrange the order of scenes here if needed, but remember, you’re not building the final manuscript here. You’re simply building the structure of the scenes you think you’ll write. Once written, you can reorder scenes and place them into chapters with a feature called Manuscript structure. This feature is a normal part of the website and doesn’t cost any agent credits.

StoryWriter (or write it yourself)

• Set up your Voice Library before you start drafting. StoryWriter attempts to match your voice from the samples you save there. Without them, it asks for a sample of your writing in every new session.
• Write the scenes you already know how to write yourself and save StoryWriter for the ones you’re stuck on. Writing you do on your own costs nothing.
• Try to avoid asking for the same scene again when only part of it is wrong. A fresh draft of the whole scene costs about as much as the first one did.
• Flow vs Focus: If you don’t like something Writer wrote, fix a passage with Focus instead of asking for the whole scene again. Focus rewrites only the part you select, and it doesn’t reread your whole Story Bible to do it, so it costs a fraction of a full draft.

StoryEdit

• Pick the scene you want reviewed before you ask. StoryEdit reads the scene you have selected.
• Save a full developmental read for a finished draft, or at least a finished act. Each full read uses one of your monthly reads and some of your credits, and a read of a half-written book mostly tells you what you already know.
• Try to avoid asking StoryEdit to rewrite your prose or ‘fix’ anything. It diagnoses and suggests, and the prose stays yours. When you’re ready to act on its notes, write them yourself or take them back to StoryWriter.

Conclusion

Beats, Plotter, and Writer do the same thing before they answer you: they read your Story Bible, so they know your characters, your structure and the decisions you’ve already made. That is what makes the answers good, but it also affects what a message costs. The more organized you are, the more efficient the agents can be.

A few habits help with every agent. Put as much as you can into one message instead of several. Work in focused stretches: after your first message, WritersForge keeps your Story Bible in cache for about an hour, and every message in that hour reads it for a fraction of what the first one cost. Take each request to the agent whose job it is. And remember, there is a lot of functionality built into the web app that doesn’t need an agent turn: you reading and searching your own Story Bible (right-hand panel), arranging chapters in Manuscript structure, exporting your manuscript, etc. Use them.