Update to ohmyho.st

{
  "description": "Explain ohmyho.st measured usage, remaining credits and project spending limits, and buy credits or Paid when the owner asks. Use for cost reports, low-credit questions, an app paused with HTTP 402, budget changes, top-ups, Paid, auto-recharge, invoices, referral links or powered-by flag credits.",
  "included_files": [],
  "name": "ohmyhost-usage-and-budgets",
  "skill_md_contents": "---\nname: ohmyhost-usage-and-budgets\ndescription: Explain ohmyho.st measured usage, remaining credits and project spending limits, and buy credits or Paid when the owner asks. Use for cost reports, low-credit questions, an app paused with HTTP 402, budget changes, top-ups, Paid, auto-recharge, invoices, referral links or powered-by flag credits.\n---\n\n# Explain usage and spending\n\nUse `identity_get` to select the organization, then `organization_credits_get` and `organization_usage_get`, which lists the billed charges of the last up to 14 UTC days by day, project and meter and each project's use so far this month. Older days are not kept. Read `project_budget_get` for a project-specific limit and `project_context_get` for current project actions.\n\nReport the available balance, reserved credits, the days covered and the largest project/environment/meter costs. Distinguish billed consumption from reservations; charges arrive up to an hour after the usage, so recent measurements are not zero usage. Explain quantities and credits together, for example database RAM and active time versus separately metered customer files. Reporting remains available at zero credits.\n\nA wallet is shared across the organization. A new workspace starts Free. Paid feature access may come from a Stripe subscription or a granted entitlement; a grant does not create a subscription or another monthly Paid allowance. A referral grant adds 1,000 credits once and thirty days of Paid; read its `paid_until`. When a finite grant ends, the workspace returns to Free, managed mail and AI calls stop, and its custom domain needs the powered-by flag to keep serving.\n\nMonthly credits expire when their period ends and renew with the next period: 200 credits on Free, 1,000 credits on Paid. Monthly credits are spent before top-ups. Top-up, bonus and referral credits never expire. `available_micros` is the monthly plus the one-time credit minus the credit that open builds and AI calls have reserved. When the credit is used up, services keep running for seven days (`grace_expires_at`); the next monthly renewal ends the exhaustion. Only effective Paid workspaces buy top-ups or enable recharge. An unpaid Stripe renewal keeps Paid features for up to fourteen days after the period end (`paid_until` includes them); otherwise the workspace returns to Free.\n\nUse `organization_account_get` or `ohmyhost credits account --organization \"$ORGANIZATION_ID\" --json` for the effective plan/source and the monthly, one-time and reserved credit. A project that shows the opt-in \"Powered by ohmyho.st\" flag (`powered_by_flag_get`) pays no custom-hostname credits and may use its own domain on Free. Each Paid period actually bought through Stripe adds 250 credits once per workspace, however many projects show the flag; granted/referral days add none. Switch with `powered_by_flag_set` only within the customer's explicit choice; hiding it is refused while a Free domain depends on it.\n\nFor the referral link use `referral_link_get` / `ohmyhost referral link --organization \"$ORGANIZATION_ID\" --json`, also the portal's \"Refer and earn\" chip. This is a recommendation link, not an invitation to join the existing workspace. A new user's first workspace receives 1,000 non-expiring credits and thirty Paid days; its first payment gives the referrer the same credit reward plus thirty granted days unless a Stripe subscription or an unbounded grant already covers it. Do not infer extra rewards from retries or additional workspaces.\n\nA project budget is a limit, not another balance. Mode `stop` pauses both Dev and Prod when measured usage plus reservations reach it: HTTP 402 begins `Project execution paused`. Mode `continue` does not pause. The same serving pause applies after the organization's seven-day zero-credit grace; a custom domain also pauses without Paid/flag eligibility. Serving resumes within about five minutes after resolving the relevant cause: raise/remove the limit, choose continue, reach a new UTC month, add credits or restore domain eligibility. Explain Stop's effect before an authorized `project_budget_set`, then read the result back. Do not change a budget merely to explain a report.\n\nFor database savings, use [the database Skill](../ohmyhost-manage-database/SKILL.md): the five RAM sizes cost 10, 20, 40, 80 or 160 credits per active hour, prorated. The 256 MiB size includes 500 MiB total disk and is available on Free; larger sizes require Paid. Disk and seven-day backups are included, with no separate database CPU, network or connection charges. Databases sleep after 300 idle seconds and then accrue no active-RAM charge. Customer files and application Workers remain separately metered. AI gateway calls reserve credit before forwarding and use the active AI rate card. Reported orq cost, including zero, always takes priority. Only chat completions and Responses with no usable cost after bounded retries use a USD 0.01 cost fallback before the card factor; smaller measured costs are never raised to that amount. Other routes with unavailable cost settle at zero. Fallback settlements carry the numeric `fallback_nano_usd` counter in operator credit-log detail. There is no automatic later correction. AI counts toward the project's Stop budget. Read current terms on https://ohmyho.st/pricing and [the AI reference](../ohmyhost-build-portable-app/references/ai.md). Retained published scripts accrue `wfp.script` charges for their lifetime even without traffic; each deployment/promotion can add one rollback script. Failed private candidates are drained. Scripts remain until their cleanup or project deletion; reset/share also remove the Dev deployment and retained rollback scripts, while append-only deployment metadata remains listable. A custom hostname accrues `domain.custom_hostname` charges except while its project shows the flag. Read the wallet's grace expiry when credits are exhausted; do not promise that unfunded services run indefinitely. New work still needs the credits quoted by its plan.\n\nDatabase schedules and webhook deliveries have no meter and no price of their own. Their counts are readable per hour or day (`database_execution_usage_get`), but what they cost is the awake time of the database, which the database RAM charge already includes. A report must not show an execution charge.\n\n## Purchases and invoices\n\nOnly start `billing_checkout_create` when the owner requested or approved that purchase. `paid` starts a USD 10/month subscription granting 1,000 credits per paid period. `topup` (Paid only; otherwise `paid_plan_required`) buys 1–100 USD 10 packs and does not extend Paid. In one checkout, dollars up to USD 100 buy 100 credits each, and dollars above buy 125 each: 25% more credits for that portion. Ten packs give 10,000 credits and twenty give 22,500. Prices exclude tax. Complete the returned checkout, then verify `billing_checkout_get` and the wallet. A browser return is not payment confirmation.\n\nUse `billing_portal_create` for invoice history, payment methods and subscription management. Every successful purchase, including a one-time top-up, has an invoice. If checkout is unavailable for the selected platform, report that response; never call a test payment a real purchase.\n\nReturn a concise cost explanation and the requested next action. For a suspected incorrect charge, use `feedback_submit` with the period and safe receipt/error identifiers, without payment details or raw records.\n\nThe portal project card's **$** button opens **Usage & limits**, using the same `project_budget_set` contract: no limit, or credits per UTC calendar month with continue/stop. Preserve the selected mode and read back changes. Existing work and delayed measurements may settle after reaching a limit. IDs in a copied project prompt identify context only; authenticate and check current scope before retrieving details.\n\n## Auto-recharge\n\nRead `billing_recharge_get` before changing auto-recharge. It is off by default and can be enabled only with active Paid access: each refill adds 1,000 top-up credits for USD 9 plus tax when available credits fall below 100. Without Paid access no refill starts; the saved consent stays until the Owner turns it off, and refills resume with Paid. The monthly limit is USD 10–1,000 including tax and uses UTC calendar months; it does not override project stop budgets or enable Paid features.\n\nOnly enable after the Owner explicitly approves these recurring off-session charges and a gross monthly limit. Call `billing_recharge_configure` with the current `revision`, the approved `monthly_limit_minor` in USD cents, `enabled: true`, `consent: \"off_session_v1\"` and a saved `idempotency_key`. Return `setup_url` to the human to save a card at Stripe, then read again. Never reuse approval for a one-off purchase as recurring-payment consent.\n\nTo turn it off, use the current revision, `enabled: false` and `consent: null`; already initiated payments may complete. Replay the same key and payload after uncertainty. `payment_required` pauses further attempts: return the private `invoice_url` when present, or ask the human to review Billing. Do not repeatedly re-enable or create another purchase to bypass a decline. `monthly_limit` resumes next UTC month; `needs_reconciliation` requires checking the original attempt rather than a new charge. Every paid refill has an invoice. Refunds/chargebacks adjust only their original credit lot and pause further automatic refills.\n\nCLI read: `ohmyhost billing recharge get --organization \"$ORGANIZATION_ID\" --json`. Authorized change: `ohmyhost billing recharge set --organization \"$ORGANIZATION_ID\" --enabled true --monthly-limit-minor 10000 --revision 0 --consent off_session_v1 --idempotency-key \"$REQUEST_KEY\" --json`; replace the example revision and USD 100 cap with the current read and approved amount. When disabling, use the latest revision and current saved limit, omit `--consent` and use `--enabled false`. Out-of-range limits or consent with disabled state answer `invalid_command`. If billing is unavailable for the chosen platform, report that result; do not switch the customer's environment.\n\n## Resolve an existing billing issue\n\nRead `billing_issue` from `billing_checkout_get` or `billing_recharge_get`; retain its `invoice_id`, `code`, observation time and `required_action`. An authorized project context may also surface that next action. `billing_tax_location_required` / `open_billing_portal` means call `billing_portal_create` and give the human a fresh private URL to correct billing details. `billing_tax_calculation_failed` or `billing_tax_configuration_required` / `contact_support` means use https://ohmyho.st/contact about the original invoice.\n\nAfter correction, inspect that same checkout/recharge policy and the actual credit account again. Reading does not authorize or initiate another charge. Keep the original invoice: never disable tax, create a second subscription/top-up, discard the invoice or repeatedly re-enable automatic refills to repair the issue. `tax_required` is a paused attempt, not a successful payment. Historical payment confirmation does not establish current Paid coverage or available credits. Preserve the approved gross monthly cap and recurring-payment consent.\n"
}