Mintlify
for LuumenAI
Read docs analytics and feedback, then ship doc fixes as approved deployments
Connect Mintlify and Luumen can read your docs telemetry directly: page views split by human and AI traffic, search terms and their click-through, per-page feedback, and full assistant conversation history. When the data points at a page that needs work, Luumen can start a docs agent job, trigger a preview for a branch, or queue a production update — each as a previewed, approved step. Authentication is by API key.
The Mintlify toolbox
14 tools: 9 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Agent JobRetrieve the status and details (status, PR link, model, source repo/ref) of a docs agent job.
- ReadGet Assistant Caller StatsGet assistant query counts broken down by caller type (web, api, other, total) for a date range.
- ReadGet Assistant ConversationsExport the AI assistant conversation history (question, answer, cited sources, resolution status) for a Mintlify project, optionally filtered by date.
- ReadGet FeedbackExport a project's user feedback (thumbs / contextual comments / agent feedback), optionally filtered by date, source and status.
- ReadGet Feedback By PageGet feedback counts (thumbs up/down, code, total) aggregated per documentation page path for a date range.
- ReadGet Page ViewsExport per-path and site-wide content view counts split by human vs AI traffic.
- ReadGet Search QueriesExport documentation search terms ordered by hit count (with CTR and top clicked page).
- ReadGet Unique VisitorsExport per-path and site-wide approximate distinct visitor counts split by human vs AI traffic.
- ReadGet Update StatusGet the status and details (queued / in_progress / success / failure, logs, commit, screenshot) of a triggered deployment update by its statusId.
- WriteCreate Agent JobStart a background documentation agent job from a natural-language prompt. Approval by default
- WriteSend Agent MessageSend a follow-up instruction to an existing, in-progress docs agent job (asynchronous). Approval by default
- WriteTrigger AutomationTrigger a custom-schedule automation (workflow) to run immediately. Approval by default
- WriteTrigger PreviewCreate or update a preview deployment of the docs project for a Git branch (redeploys if a preview already exists for that branch). Approval by default
- WriteTrigger UpdateQueue a production deployment of the docs project from its configured branch. Approval by default
One prompt, start to finish
What a governed Mintlify run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create agent job, send agent message, trigger automation, trigger preview, and more — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Mintlify — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Mintlify to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.