Publish files and HTML pages to public CDN URLs, and clean them up later
Drop to CDN gives your team a place to put artifacts that need a link. Upload a log bundle, a diff, or a rendered status page, and get back a public URL you can paste into a ticket or a channel. Luumen reads your file list, metadata, and account usage on its own, and holds uploads, page publishes, and deletes for your approval first. Connects with an API key.
6 tools: 3 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Drop to CDN 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.
This connection exposes write actions such as permanently delete file, publish page, upload file. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Drop to CDN — 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.