Billing & plan
The org's platform subscription on the record: plan, status, current billing period, and the last three invoices with per-line L-MONEY amounts (plan / extra seats / AI credits / total). Read surface — plan changes run through the platform's processor flows, not template forms.
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: GET /api/v1/fin/subscription.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Settings tile; part of the 'settings' surface.
- Who can use it
- RBAC: fin.subscription.read.
- The API behind it
GET /api/v1/fin/subscription- Where it lives
- /settings/billing
See it in context
One login, many businesses — the full walkthrough, step by step: Agencies and multi-brand operators: every business, one account, real separation.
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.