credits account reports the effective Free/Paid plan, the monthly credit with its next expiry, the one-time credit that never expires, reservations and available_micros. credits balance reports only the balance: available_micros, reserved_micros and the seven-day credit-grace deadline; what the credit was spent on is in credits usage. credits usage takes no month or cursor: it reports the billed charges of the last up to 14 UTC days (today included), grouped by day, project and meter, and what each project has used so far in the current UTC month. Older days are not kept, so save a report you need later. MCP organization_usage_get takes only the organization. Reading credits and usage needs CLI and MCP 0.1.41 or later: older clients send the removed month and cursor inputs and expect credit totals that no longer exist (changelog).
Ask your agent for a credit report
You can ask your ohmyho.st agent for your available balance and settled usage over the last 14 UTC days. The report covers the entire workspace, including usage from other projects, members and background jobs. Settlement lag varies by meter. Billing records are grouped by workspace, project and meter, so they cannot attribute charges to an individual chat or task. Before a build, ask for the deployment plan’sestimated_cost.credits when available. It is the credit reservation quoted for the build. Measured build time determines the final charge, and unused reserved credits are released.
What contributes to consumption
Builds, active database compute, storage and supported service operations are measured through their actual meters. Published credit prices list each quantity and rate. Quiet databases sleep and stop active-RAM charges, and database disk and seven-day backups are included; customer files and retained deployed scripts still cost credits at their own rates. A query may wake a suspended database. Shared Dev/Prod use one data area; isolated areas are metered separately. Change data assignments explains the four confirmed actions without copying data or changing rates. Database usage is selected RAM multiplied by active time. Do not multiply the complete bill or already valued usage again. The AI gateway reports settled calls underai.cost with unit
usd_micro. It needs active Paid access and available credit for each hold; the
ordinary hosting credit-grace period does not admit AI calls without enough credit.
Recorded cost, including zero, takes priority. From release 0.1.48, only chat and
Responses calls without a usable cost use the USD 0.01 fallback before the
unchanged rate-card factor; other unmeasured AI routes settle at zero. See
AI billing rules for scope and reconciliation.
Read the balance correctly
available_micros is the monthly credit plus the one-time credit minus reservations. Monthly credits (200 on Free, 1,000 on Paid) expire on the date shown in Billing (next_expiry) and are spent before one-time credits. One-time credits never expire: top-ups, auto-recharges, and signup, referral and bonus credits stay until used, also after a downgrade to Free. Only effective Paid workspaces can buy top-ups or enable auto-recharge, but bought credit stays usable after a downgrade. An unpaid Stripe renewal keeps Paid features for up to fourteen days after period end; paid_until in credits account is the end of the paid coverage and includes those days. Otherwise the workspace returns to Free, and cancellation ends Paid at the paid period end. In-flight reservations appear as reserved_micros in credits account and credits balance; the portal does not show them.
When the credit is used up, services keep running for seven days (grace_expires_at); the next monthly renewal ends the exhaustion.
Some measurements arrive later than the original operation. A low current total is not a guarantee that all running work has settled. Optional project budgets default to Continue: the project keeps running after the tracking threshold. A project pauses at its budget only when the workspace Owner explicitly selects Stop.
Billing and recharge · Database sizes.