Last verified: October 5, 2026
What You Can Now Do
Context Memo now resumes your paused brands in the simulator automatically when OpenRouter auto top-up refills your funds, and the simulator shows you which brands are currently paused. Before this, a refilled OpenRouter balance did not change anything inside Context Memo on its own: the brand stayed in a funds-paused state until someone opened the product and resumed it by hand. Now the pause clears itself once the funds land, and the paused state is visible on screen instead of inferred from scans that stopped returning results. The task this removes is the recovery step. You no longer have to remember which brands went quiet, confirm the top-up, and switch each one back on.
Where It Is in Context Memo
This change is in the simulator. The simulator screen now surfaces which of your brands are in a paused state, so pause status is readable at a glance rather than something you discover when a scan comes back empty. Auto top-up itself is configured in your OpenRouter account, not in Context Memo; the simulator reacts to the refill. Nothing changed in memo generation, citation tracking, or publishing.
How to Use It
- Turn on auto top-up in your OpenRouter account and set the trigger balance and refill amount. OpenRouter will refill the account without a person in the loop, which is the condition this feature depends on.
- Open the simulator in Context Memo. Any brand currently paused for funds is shown as paused, so you can tell the difference between a brand with no recent scan activity and a brand that is blocked.
- Leave it alone when a pause appears. Once OpenRouter posts the auto top-up, the simulator clears the funds-pause state on the affected brands and they resume. No manual resume action is required.
- Reload the simulator to confirm. The brands that were listed as paused are no longer flagged, which is your signal that scanning has picked back up.
- If a brand stays paused after a confirmed OpenRouter refill, treat that as a funding configuration issue first: check that the top-up actually posted to the account tied to your workspace, then check the refill amount against what your scan volume consumes.
- Set your auto top-up trigger high enough that the refill fires before the balance reaches zero. A higher trigger balance shortens or avoids the pause window entirely, which matters most if you run multi-model scans on a schedule across several brands.
Why We Built It
Customers told us the same thing in plain terms: their OpenRouter account had already been topped up automatically, but their brands in the simulator were still paused, and someone had to go in and resume them one by one. That is a manual step attached to an event that was already automated, and it is easy to miss. The cost was time spent reconstructing which brands were affected, plus the lag between the refill and the moment scanning actually restarted. For teams tracking how models describe their brand over time, that lag shows up as gaps in the record, and gaps are the one thing that makes a visibility trend line hard to defend internally.
The second half of the problem was visibility into the pause itself. A paused brand looked like a brand that simply had nothing new to report. Showing pause state directly in the simulator removes that ambiguity, so you can act on a funding problem as a funding problem.
What It Does Not Do Yet
Context Memo does not configure auto top-up for you and does not add funds to your OpenRouter account. That setup stays on the OpenRouter side, including the trigger balance, the refill amount, and the payment method behind it. If auto top-up is not enabled, or if the card on file fails, brands will remain paused until funds are available; the automatic resume only triggers on an actual refill.
This also applies to the funds-pause state specifically. Brands paused for other reasons are unaffected by the top-up and are not resumed by it.
Finally, the simulator reports pause state; it does not forecast it. There is no projection yet of when your current balance will run out at your present scan volume, so sizing the refill against your scan cadence is still a judgment call you make in your OpenRouter settings.