Account and workspace / Article
Understand reply credits and read Usage
Check requests, credits, and the monthly balance, and distinguish SiloBox limits from OpenAI charges.
Before you start
Open the correct workspace. Its members share the plan allowances. SiloBox credits measure SiloBox usage; OpenAI API processing is billed separately to the connected OpenAI project. Paying one does not fund the other.
Read your usage
- Open Usage and choose This month, Last 7 days, or Last 30 days. For custom dates, enter Start date and End date, then choose Apply dates. The range must end today or earlier and span no more than 366 days.
- Compare Requests in selected dates and Credits in selected dates. A request is not necessarily one credit. Requests include charged prompt retrievals and AI response attempts, including failures; replayed responses and human replies are not counted again.
- Choose requests or credits in the daily chart. Use View daily values for the table and group the breakdown Per prompt, Per bot, or by Request type. Sort requests or credits to find the largest contributors.
- Check Monthly plan balance separately. It covers the current UTC month regardless of the dates selected above. Open Billing to review your plan's actual allowance and enforcement.
How reply credits work
Replies start at two credits. Web or file search adds one credit per reply when used, even when that search is repeated. Each custom-tool round adds two credits. Each processed audio, image, or PDF adds two credits on top of the reply cost. Unused tools add nothing. A plain reply without tools or media therefore starts at two credits; one processed image adds another two.
Before generation, SiloBox reserves the maximum required for the selected tools and media. Available credits must cover that reservation even when the final reply might cost less. After completion, actual usage is charged and the remainder released. Failed or incomplete generation uses no SiloBox credits. A completed reply is charged even if delivery fails. OpenAI may still charge for processing separately.
Troubleshooting totals and limits
Usage dates and the monthly balance use UTC; Metrics uses its selected timezone. Selected dates may cover another period. Retrieval details sync periodically and can lag behind the plan balance; older retrieval details may be unavailable. The page cannot identify the exact cause or reconcile a difference, so keep the range and coverage notices when asking support.
For a plan with an enforced monthly limit, reaching it stops service; upgrade or wait for the monthly reset. A reservation can also fail before the displayed balance reaches zero. If generation succeeds but delivery fails, investigate delivery rather than assuming the credit charge is an error. If the monthly balance is unavailable, refresh rather than treating it as zero.