Read, convert, and assemble PDFs and scans from the terminal
Operations teams end up with PDFs everywhere: vendor invoices, scanned change forms, signed runbooks, exported reports. PDF Munk lets Luumen read those files for context — text, layout, tables, OCR from scans — and then produce new ones. Generating, merging, converting, and watermarking are approved steps by default, with the resulting hosted URL and its deletion date shown when the service returns them. Connect with an API key.
9 tools: 3 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed PDF Munk 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 — convert images to pdf, convert pdf to images, generate image, generate pdf, 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 PDF Munk — 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.