Members (traffic light: green = active now, orange = registered but idle, red = blocked)

Corporate domains (accounts from these domains get a 6-digit code on every login)

Not configured yet - add WAI_CLOUDFLARE_API_TOKEN / WAI_CLOUDFLARE_ZONE_ID to .env.

Last 24 hours (hourly)

Visitors (session + country, last 14 days)

No country data yet - either traffic hasn't come in since this was added, or the site isn't being proxied through Cloudflare (grey-cloud DNS skips the CF-IPCountry header entirely).

Recent visitors (last 50 events)

Live Data settings

Automatic for every logged-in member - a free monthly lookup quota per member, then a small automatic top-up from their W$ balance. These numbers are WAI's own safety controls on top of Tavily, not Tavily account settings.

Subscription plan cost ceiling

When a paying member's real AI/Live-Data usage in the current billing period passes this percentage of their plan price, WAI quietly caps them to cost-efficient models for the rest of the period and sends them an in-app notice explaining why. Their plan and balance are not otherwise affected, and this resets automatically each month. Free/trial and Enterprise Unlimited plans are never subject to this.

First top-up bonus

A bonus added on top of a member's very first-ever real top-up (Stripe, iyzico, an approved top-up, or a redeemed code) - never on renewals or later purchases. Comes out of WAI's own margin, same "customer acquisition cost" idea as a signup discount. Set to 0 to disable.

Pay-As-You-Go limits

Members can optionally switch to postpaid billing - real usage accrues against a monthly cap they pick, then their saved card is charged the exact amount once a month. This sets the min/max they're allowed to pick, and a kill-switch for the whole feature.

Finance accounts

Give someone access to view Accounting only - they log in with the normal email/password screen but never see anything else in WAI (no chat, no other admin tools). "Finance" and "Read-only / Auditor" currently behave identically (view-only) - the distinction is kept for future write actions.

1. Acquisition

2. Activation

3. Engagement

4. AI Performance (last 24h)

5. W$ Economy

6. Infrastructure (Cloudflare edge - see also the Cloudflare tab)

Not configured yet.

WAI never receives real money directly - this is a summary of the credit-code vouchers you generated after receiving payment through your own channel (bank transfer, PayPal, cash), plus any manually-approved top-ups. Reconciling against your actual bank/PayPal statement is still on you - this is bookkeeping visibility, not an accounting system.

Revenue ledger (real payment allocation)

Paid vs. the 25/25/50 split (user / Free Pool / company), across every top-up and code redemption ever recorded. Admin-only - this exact breakdown is never shown to end users; My Credit shows a plain-language version of the same numbers.

Redeemed vs. unused (by value)

Recent codes

🌍 Revenue by country (for your accountant - EU OSS threshold)

WAI bills directly via Stripe/iyzico (no Paddle) - your accountant is responsible for VAT/tax registration, this just surfaces the real numbers. The EU figure below (Romania excluded) is what counts toward the EU's EUR 10,000/year Union OSS registration threshold for cross-border digital-service sales - amounts are in USD, convert at the current rate when it matters. Non-EU countries (Turkey, etc.) each have their own separate rules, not covered by OSS at all.

Create a promo code members can enter at checkout for a real W$ bonus on top of what they actually pay (e.g. "SUMMER15" = +15% W$). Comes out of WAI's own margin - a genuine customer-acquisition/retention cost you control and can always see the real size of below, never a discount on the charge itself.

Campaigns & real performance

⬇️ Export report (JSON)

Real numbers only - revenue, margin, and subscriber figures below come straight from WAI's own ledgers, never an AI-generated or extrapolated forecast. The scenario calculator further down is a planning tool that uses whatever assumptions YOU type in - it is not a prediction of what will actually happen.

Real revenue trend (last 30 days)

Growth actions

Track ideas for growing revenue/subscribers (referral program, campaign, pricing test, etc.) and fill in what actually happened once you know - never a predicted outcome, only real results after the fact.

What-if scenario calculator

Hypothetical planning tool - type in your own assumptions to see the resulting MRR. This is math on numbers you provide, not a system prediction.

Alerts

Answer feedback

Recent comments

Events (last 14 days)

Daily report archive

One JSON snapshot per day (cost, visits, Cloudflare, W-ENG telemetry) - generated automatically the first time this tab is opened each day. Click a date to view the raw snapshot.

Generate a credit code

Once you've actually received payment (bank transfer, PayPal, cash - whatever channel you're using outside WAI), generate a code for that amount here and send it to the user. Redeeming is instant on their side, no further action needed from you.

Generate code

Manual top-up requests (self-declared, closed once Accounting is active)

This is the pre-billing stopgap where a member claims "I paid you outside the system" and you approve by hand - no verification, so it closes itself the moment Accounting goes active (Admin > Accounting) and every dollar has to come through a real, gateway-verified payment (Stripe/iyzico) instead. Anything still listed below is historical/unresolved from before that switch.

Credit / monetization model (live - Stripe/iyzico wired, this is the current split)

Requests submitted from the public Subscriptions page. Follow up by email to agree terms, then use "Set plan" on a member in the Users tab to actually move their account onto SMB/Enterprise pricing (see UserStore::PLAN_CATALOG) - nothing here bills anyone automatically.

Change a model's price or which customer segment (Basic/Advance/Pro) can use it - takes effect immediately, no code deploy needed. The task-type routing (which engine chain each module uses) stays code-managed to avoid accidentally breaking a module.

W-ENG telemetry (last 500 requests, real data - not simulated)

Every AI call and every deterministic tool (LCOE, ROI/NPV) run is logged with its real latency, cost, and success/failure - this is W-ENG's own lightweight, file-based monitoring, refreshed every time you open this tab.

Engine health (task #258 - auto-derived from the telemetry above)

No extra pings, no extra API cost - this reads the exact same log as the telemetry above. An engine only turns red after 3 or more failures IN A ROW; a single dropped connection never flags it. While red, W-ENG quietly tries that engine LAST in its chain instead of first, so a struggling provider costs a paying customer nothing extra in wait time - nobody has to notice or intervene for this to work.

AI Providers - Video Generation

WAI's Video Engine is provider-agnostic - Runway is the recommended default today; Sora 2, Veo 3.1, and Seedance can be added as additional providers later without changing how members use the feature. Only one provider is "active" (used for real requests) at a time.

AI Providers - Live Voice

Full-duplex, real-time voice conversation for Ask WAI Anything (subscribers only). Billed per minute of audio by the provider - leave disabled unless you've reviewed the cost per minute and the included-minutes cap below.

API Registry

Every third-party API/service WAI is aware of, in one place. Rows marked "Built-in" are informational - their real key lives in server config (.env), shown here so you can see at a glance what's actually connected. Use "Add API" below for a genuinely new service (a weather provider, an FX/stocks feed, a research API...) - its key is stored and managed right here, ready to be wired into a feature without a code deploy.

+ Add API

API name Category Finance / FX Weather Energy Research Geography Live Data / Search AI / LLM Other API key

Base URL Notes

Enabled Save API

Manual-entry ledger of AI/cloud provider startup credit and partner programs - most of these (Anthropic, OpenAI, Google Cloud, AWS Activate, etc.) don't have a public "remaining balance" API, so update the numbers here yourself whenever you check the provider's own dashboard. This never talks to a provider automatically - it's just one place to see all of them instead of several logins.

Programs

Tracker for third-party "skill" submissions to the Developer Partner Program (see /partners) - a skill is a system-prompt + worked example targeted at one task type, narrower than a full module. No self-service form exists yet, so log a submission received by email here. Field shape matches code/schemas/skill_submission.schema.json exactly - keep both in sync if you add a field. Default revenue share (15%) mirrors the published module rate on /partners.

Submissions

If you just re-uploaded files and the site still looks/behaves like the old version, there are two different causes with two different fixes: (1) PHP holding on to old compiled code (OPcache) - clear it below, or (2) the upload itself only partially finished (common with FTP clients like FileZilla on large transfers) - check "Deployment check" below, which shows exactly when each file last changed ON THE SERVER.

🔄 Clear PHP cache (OPcache)

WAI Sense

Opens sense.wht-ai.com via a fresh, short-lived SSO link - the only working way in right now, since the member-facing entry points were intentionally removed.

🧭 Open WAI Sense

Daily backup (email)

A cron job (cron/daily_backup.php) zips the entire data/ folder every day and emails it to the address in .env's WAI_BACKUP_EMAIL_TO - so even in a worst case (server wiped, hosting lost), a same-day copy of every user, credit balance, and conversation already sits in an inbox. This needs a one-time IONOS Cron Job setup - see the comment block at the top of cron/daily_backup.php for the exact steps.

External uptime monitoring

WAI cannot monitor itself being down (if the server is down, WAI's own code isn't running either) - this needs a free third-party watcher pinging the site from outside. Recommended: UptimeRobot (free tier: 50 monitors, checks every 5 minutes, email/SMS alert on downtime). Setup (~5 minutes, one time): 1) create a free account at uptimerobot.com, 2) "Add New Monitor" → type HTTP(s), URL = your homepage (e.g. https://www.wht-ai.com), 3) set the alert contact to your email, 4) save. No code or server access needed on WAI's side for this step.

Data storage location

Database (Registry / Personal OS) connection

Deployment check

Last-modified time of each file, as seen by the server right now. If one file shows a much older date than the others, that file did not actually get uploaded in your last transfer - re-upload it (or the whole zip) again.

Live endpoint check (task #261)

Unlike the file-timestamp check above, this makes 3 REAL requests from the server to itself right now: the homepage, a guest-facing API action, and an admin-gated API action called with NO session (it should be cleanly rejected, not crash) - so you can confirm the live site actually works end-to-end after a deploy, not just that the files arrived.

🔍 Run live endpoint check

🧪 Payment system test

Runs a real $1.00 Stripe Checkout charged to WAI's own admin account (refundable any time from the Stripe dashboard) and confirms the signed webhook actually credited it - the same path every real member top-up goes through.

💳 Run $1.00 Stripe test purchase

🧪 iyzico payment system test

Runs a real $1.00 iyzico Checkout Form charged to WAI's own admin account and confirms the payment actually credited W$ - the same path every real Turkish card top-up goes through. iyzico's own API requires buyer details below (sandbox/test values are fine) - this is iyzico's requirement, not WAI's.

💳 Run $1.00 iyzico test purchase

External services

PHP environment (this server, right now)

Configuration checklist

Server metrics (real, host-permitting)

Failures (last 30 days)