Crossdeck Prism
Ask which paying customer an error hit and what they're worth — Prism crosses your revenue, errors, identity and cost in one question.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- List Projects: List every app (project) in your Crossdeck portfolio that this connector can read — the same set your Pulse dashboard shows. Returns an array of { id, name } per app. Call this FIRST: e
- Get Revenue: Get an app's recurring revenue from its maintained revenue ledger (a point-read, never a scan). Returns MRR in cents, the paying-customer count, and the per-rail split across Stripe, Appl
- Get Read Cost: Get an app's database read-cost, split into per-user reads vs un-attributed overhead, with a breakdown by operation. Per-user attribution works because Crossdeck joins read-cost to the
What data it sees
Do you need an account
No: the server works without sign-in
Ask which paying customer an error hit and what they're worth — Prism crosses your revenue, errors, identity and cost in one question.
Server tool list (10)
Raw names from tools/list. Only developers need these.
| list_projects | List every app (project) in your Crossdeck portfolio that this connector can read — the same set your Pulse dashboard shows. Returns an array of { id, name } per app. Call this FIRST: every other tool needs a project id. Read-only; takes no arguments. |
| get_revenue | Get an app's recurring revenue from its maintained revenue ledger (a point-read, never a scan). Returns MRR in cents, the paying-customer count, and the per-rail split across Stripe, Apple, and Google. Use for 'what's our MRR' or 'how many paying customers'. An app with no revenue yet returns zeros, not an error. |
| get_read_cost | Get an app's database read-cost, split into per-user reads vs un-attributed overhead, with a breakdown by operation. Per-user attribution works because Crossdeck joins read-cost to the SDK's identity. Returns the per-user-vs-overhead totals and the by-operation breakdown. Use for 'what's driving our database reads' or 'which operation costs the most'. |
| get_error_impact | Get one error's blast radius joined to identity. Returns distinct users affected, how many of those are PAYING customers, and the error's type, status, occurrence count, and first/last-seen — counts only. Use to size an error's impact. For the NAMED paying users behind the counts, call get_error_affected_users. |
| get_error_affected_users | For one error, get the PAYING users it actually hit — the row-level moat answer: which paying customer broke, and how much are they worth. Returns a list sorted by revenue at risk, each row with your own user id, monthly revenue in cents, and when they last hit it. Returns your own identifiers only — never emails/names you didn't provide. Use when you need the actual customers, not just counts. |
| get_customer | Cross-match one customer across every layer Crossdeck joins by identity. Returns what they pay (monthly cents), their active entitlement count, and their database read-cost — in one view. Use for 'how much does this user pay and what do they cost us?'. Returns a no-match result (not an error) if no customer resolves. |
| get_host_analytics | Get headless web analytics for one host/subdomain the app owns (e.g. a tenant's subdomain). Returns page views and unique visitors with totals, from the maintained rollup ledger. The host MUST be a verified origin of the project, or the request is rejected (403). Use for per-tenant traffic questions. |
| get_host_top_pages | Get the top pages for one host the app owns, ranked highest-first. Returns rows of { page, views } from the rollup ledger. The host must belong to the selected app. Use for 'most-viewed pages on this subdomain'. |
| draw_user_growth | Render an interactive line chart of unique visitors and page views over time for a host you own. Use when asked to chart, graph, draw, or visualize growth or traffic for a subdomain. The host must be a verified origin of your project. |
| open_moat_dashboard | Render a customer's cross-layer dashboard — what they pay, their active entitlements, and their database read-cost, joined by identity. Identify the customer by any of userId, anonymousId, customerId, or a rail transaction id. This is the moat, rendered. |