Skip to content

Set Up Billing

Use this guide when an organization is new, blocked by setup_required, or changing the billing foundation.

If Pharaoh has routed you into Organization Onboarding, complete billing from there. Onboarding may send you to the same billing setup surface, but it remains the page that decides whether you can enter the main console after billing is active.

You need a role that can manage billing for the current organization. Confirm the active organization from the user menu before changing billing.

Decide whether the organization will use:

  • BYO Anthropic key, where provider usage is paid through your Anthropic account.
  • Managed usage, where Pharaoh provides provider access and bills provider usage through Stripe.

Pilot, Production, and Enterprise / MSP packages use different setup paths. The in-app self-service billing setup defaults to the current Production package. Pilot and Enterprise / MSP packages are sales-assisted and can be assigned without changing an existing organization’s stored package snapshot.

  1. Open Billing from the administration area or go directly to /billing/setup. If you are in onboarding, select Continue to billing setup from the Billing step instead.
  2. Review the package summary: Production is $49/month with 20 active endpoints included, plus $2/month per additional active endpoint, prorated by active endpoint intervals.
  3. Choose the billing currency while setup is still pre-Stripe. The selected currency locks after Stripe setup starts.
  4. Choose the usage mode.
  5. For BYO mode, create an Anthropic API key and add it in Pharaoh. See Use your own Anthropic API key.
  6. Set the monthly usage spend limit. New organizations default to $100/month unless changed by an authorized billing operator.
  7. Continue through the Stripe-hosted payment or subscription step when the UI sends you there.
  8. Return to Billing or onboarding and confirm the status is active before starting billable sessions or provider-backed work. In onboarding, select Check billing status after setup returns.

The monthly spend limit is a hard stop for usage only. It applies to BYO and managed usage, but it does not include the base subscription fee or endpoint overage fees. Managed AI usage is billed separately as actual provider cost plus the package management fee.

When the limit is reached, Pharaoh blocks expensive LLM work immediately. Web billing recovery, non-expensive operational reads, endpoint heartbeats, and setup/recovery paths should remain available.

Select the organization’s billing currency before opening Stripe setup. Pharaoh blocks post-setup currency edits because subscription Prices, endpoint invoice items, and managed usage meter records must remain in one account currency. Contact support if an already-configured organization needs a currency migration.

Some billing setup states are currently documented from contracts, fixture-backed visual review, live billing API integration proof, clean Stripe sandbox lifecycle proof, and seeded docs capture routes. Do not treat trace screenshots as mock-free browser E2E proof. The Stripe sandbox lane has proved subscription setup, webhook forwarding, test-clock advance, and internal payment/subscription projection, and focused docs capture/verify has passed for the committed setup-required and active-dashboard billing screenshots. Onboarding-specific billing screenshots still need seeded capture helper support. Stripe-hosted browser pages still need a safe external-surface proof lane.