# Lumro

Lumro is a sales and support system for paid communities. It detects buying signals and support questions in Discord, answers from the business's approved product knowledge and retained staff answers, links the right offer when the evidence supports one, and sends uncertain questions back to the team instead of guessing.

Members can receive help in Discord or through the general-purpose AI they already use. Lumro gives that AI a narrow, ask-only business interface; it does not replace the member's agent. An authenticated operator agent gets separate support-operation tools.

## Current product boundary

Live today:
- A free, private Discord sales and support audit built from channels the Discord role can read.
- Identification of support and buying questions that the public capture could not confidently connect to a staff response.
- A report-level opportunity calculator that multiplies audited buying signals by an owner-selected order value. This is a scenario, not attributed revenue.
- Grounded product and support answers from retained staff messages and facts explicitly taught by the operator.
- Honest refusal when the available evidence does not support an answer.
- An ask-only member MCP scope.
- An operator MCP scope for status, queue review, draft approval/rejection, teaching, channel and reach controls, activity, testing, and report retrieval.
- Human-only Discord consent, billing, and deletion.

Not yet claimed:
- Whop identity or entitlement verification.
- Individually verified member credentials. The current member credential is ask-only and issued by the operator.
- A complete per-tool-call audit ledger.
- Server-enforced approval for every high-impact operator mutation. Operator agents must request explicit human direction before widening reach or enabling channels.

## Access model

Public access can explain Lumro and start/check/redeem a setup. It cannot read a community or operate one.

Member access exposes exactly one tool: ask_understudy. It can ask the community's Lumro a question and receive a grounded answer or an honest stop. It cannot inspect queues, other users, operational state, or change the business.

Operator access exposes sales-and-support operation tools. Possession of the operator credential is authority; keep it private and revoke it from the dashboard if compromised. Billing and deletion remain human-only.

## Agent-driven onboarding

Endpoint: https://lumro.ai/api/mcp (Streamable HTTP, stateless)

Start with no Authorization header and call about. Explain to the human:
1. The audit reads only channels visible to the Discord role.
2. Discord requires the human to choose and authorize the server.
3. The audit is private and does not post messages.
4. A later rollout starts with drafts and a narrow audience.

If the human approves, call start_setup. Give them the returned install_url and retain the setup_code. Poll check_setup until the audit completes. The connection can use Authorization: Bearer <setup_code>; after binding it resolves to the connected operator.

Before any rollout:
1. Review get_status and the private report.
2. Test known and unknown questions with ask_understudy.
3. Teach only facts the operator confirms.
4. Propose a staff-only test.
5. Do not widen member reach or enable additional channels unless the operator explicitly asks.

## Private report verification

A report URL looks like https://lumro.ai/report/<slug>. Treat the slug as a credential.

- GET https://lumro.ai/api/wrapped/<slug> returns the report data as JSON.
- methodology.verified_reply describes the captured source platform's explicit reply metadata; it never treats timing or proximity as reply proof.
- methodology.audit exposes startedAt, finishedAt, and reportBuiltAt as separate UTC timestamps. builtAt is a deprecated compatibility alias for finishedAt.
- https://lumro.ai/try/<slug> is the grounded test chat.
- POST https://lumro.ai/api/chat with {"slug":"<slug>","messages":[{"role":"user","content":"..."}]} returns a streamed plain-text answer.

Verify both sides of the boundary: ask one question supported by retained evidence, then one the community never answered. A trustworthy result answers the first from evidence and stops on the second.

Report wording is deliberately conservative. An unmatched public response does not prove nobody answered in a DM, ticket, thread, voice call, deleted message, or uncaptured channel.

## Operator tools

An authenticated operator connection currently includes:
- get_status
- list_queue
- approve_draft / reject_draft
- teach
- set_reach
- set_channel
- remove_rule
- recent_activity
- ask_understudy
- get_wrapped

Use the least authority necessary. Read before mutating. For risk-increasing changes, summarize the exact proposed change, audience, and rollback and wait for explicit human direction.

## Commercial terms

- Audit: free.
- Controlled sales and support trial: seven days from completed audit.
- Then: $40/month at the current founding rate.
- Trial lapse pauses member posting; it does not silently delete the dashboard or retained data.
- The operator can pause, revoke credentials, remove the Discord bot, or request deletion.