product

missionsagent-driven promotion campaigns with adjustable autonomycontent & draftsAI-generated content reviewed before it shipsinbox & engagementsunified inbox for mentions, drafts, and AI decisionsCRM & contactsrelationship management with AI-powered outreachresearch & recordsstructured data gathering on autopilotworkflowsvisual automation graphs — no code requiredprojects & docswork planning, docs, and standups — all native

solutions

for startupsyour marketing team is an agentfor agenciesscale clients, not headcountfor creatorsgrow your audience while you createfor enterpriseautonomous marketing with full controlview all solutions
platformmodelspricing>docs

Billing

Nihmbus does not bill you directly for AI usage. All model inference (chat, knowledge ingestion, voice derivation, content generation) runs through Hypery, and Hypery bills the team that owns the work.

The one rule

Nihmbus organizations are 1:1 with Hypery teams — same id, same slug. The organization you have active in the Nihmbus workspace switcher is the Hypery team that pays for that work.

  • Switch organization → a different Hypery team is billed.
  • Your personal organization maps to your personal Hypery team.
  • Team members share the org's Hypery billing; you do not each pay separately.

Every request Nihmbus sends to Hypery carries your OAuth token, so Hypery bills your active org's team — never a shared Nihmbus key, and never the Nihmbus developer. (Background/durable runs reuse the same user's token, stored encrypted on the run, so a resumed job bills the same team.)

How the team is charged

That's decided on the Hypery side by the team's billing mode. There are three, and they change where the money is charged, not which team pays:

  • VAG passthrough (default) — Vercel AI Gateway meters each request and Stripe bills the team's customer directly. No credit balance to hold, no top-up. Usage is priced by the team's Stripe meter configuration.
  • Metered — an internal Hypery credit wallet; a saved card is auto-charged to keep a small buffer funded.
  • Prepaid — the same wallet, but you top it up manually; requests are rejected when it hits zero.

See Hypery's Billing & Credits for the full comparison. You manage all of it (payment method, credits, invoices) on Hypery, linked directly from Settings → Billing in Nihmbus.

Spending limits

Two independent caps can stop a request before it costs anything:

  1. Per-app OAuth limit — when you first authorize Nihmbus on Hypery it gets a default daily cap (~10 credits/day ≈ $0.10). If chat returns "Daily spending limit exceeded," this is it — raise it under Authorized Apps on Hypery.
  2. Team spending limits — daily/monthly caps a manager sets on the Hypery team (per provider, model, or member). Managed under Spending Limits on Hypery.

Why the Vercel AI Gateway dashboard looks different

Nihmbus bills through Hypery, not through your own Vercel AI Gateway dashboard. Numbers you see on the Vercel AI Gateway dashboard are Hypery's upstream provider cost or unrelated traffic — not your Nihmbus usage. Your actual bill lives on the linked Hypery team.

Use in the UI

Open Settings → Billing (/settings/billing). It shows the linked Hypery team for your active organization and deep-links to Hypery to:

  • Billing & payment methods — hypery.ai/settings/{slug}/billing
  • Add credits (metered/prepaid) — hypery.ai/settings/{slug}/billing/topup
  • Spending limits — hypery.ai/settings/{slug}/limits

Owners, admins, and billing-role members can manage; everyone else sees which team is linked, read-only.

Browser automation (Browserbase)

Hosted browser sessions (login, browser.do, publish) run on Browserbase. Nihmbus pays Browserbase with the platform key, then charges your Hypery team for the minutes used:

  • Metered / prepaid Hypery teams — credits are deducted from the team wallet.
  • VAG passthrough teams — a Stripe invoice item is added to the team's customer (Browserbase is not covered by Vercel AI Gateway token meters).

LOCAL Chromium (dev fallback) is not billed. Rate defaults to $0.004 per billed minute (1-minute minimum per session); override with BROWSERBASE_USD_PER_MINUTE. Usage also appears in Nihmbus Expenses as integration-fee / Browserbase.

Verifying it works

After a chat message, model usage appears in Models → Usage in Nihmbus and in Analytics on the linked Hypery team. If Hypery is routing correctly, llm_traces.via is hypery. After a Browserbase session closes, look for an integration-fee row in Expenses and a matching Hypery usage charge / Stripe invoice item.