Read your Ragie corpus, then ingest and retag documents with approval
Ragie holds the documents your retrieval stack answers from. Connect it and Luumen can list partitions, read documents and chunks, and check summaries before it changes anything. Ingestion, metadata patches, partition limits, and deletions run as previewed steps you approve, with an audit record. Luumen authenticates with an API key.
31 tools: 17 read, 14 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Ragie run looks like inside Luumen.
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 document, create document from url, create document raw, create instruction, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. 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 Ragie — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.