---
title: "Owner Business Status"
method: GET
path: "/owner/business-status"
---

# Owner Business Status

`GET /owner/business-status`

## Request

- Base URL: `https://mcp.physea.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.physea.ai/owner/business-status`
- Auth: none declared

OWNER plane (Live Status — be-user-activity-20260624): ONE business-status
payload answering Jay's five questions with real current numbers + traffic:
who's using it (real-external vs internal/test/demo callers), what they're
doing (top flows/paths), what they're asking (distinct question hashes; raw
text only on the admin user_activity rows that legitimately carry it),
signups + purchases (minted keys / accounts / fulfilled Stripe sessions), and
revenue (local fulfillment total; live Stripe is a surfaced gap with a one-step
connect). COMPOSES the existing builders (telemetry.rollups, savings.rollup,
user_activity.users) + the net-new money layer — it does not re-implement them.
LAZY + EMPTY-SAFE: a missing store yields zeros + a note, never a 500.
Admin-gated via the /owner/ prefix in metering.AUTH_PATHS.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/physea/apis/liminality-router-service.md) · [All operations](https://skmtc.dev/physea/apis/liminality-router-service/llms.txt) · [OpenAPI document](https://skmtc.dev/physea/apis/liminality-router-service/revisions/5f60ddd97544?raw)