lc.cx
for LuumenAI

lc.cx provides URL shortening, branded domains, workspaces, tags, click statistics, and QR code generation through its API.

Bring lc.cx into the same conversation as the systems behind it. LuumenAI reads campaigns, audiences, and delivery status for context, and changes them only through previewed, approved, audited actions.

The lc.cx toolbox

10 tools: 4 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet Account ContextReturn lc.cx plan and short-link quota information together with available domains and workspaces needed to create and route short links.
  • ReadGet Short LinkRetrieve one short link by its lc.cx link id from the selected workspace.
  • ReadList Short LinksReturn one page of recently created short links in the selected workspace, with an offset for the next page when one may exist.
  • ReadList TagsReturn all tags available in the selected workspace for organizing short links.
  • WriteCreate Short LinkShorten one destination URL on lc.cx, optionally choosing its path, tags, note, and workspace. Approval by default
  • WriteCreate TagsCreate one or more tags in a workspace and return their ids for attaching to short links. Approval by default
  • WriteDelete Short LinkPermanently delete one short link. Approval by default
  • WriteDelete TagPermanently delete one tag from the selected workspace. Approval by default
  • WriteUpdate Short LinkUpdate a short link's destination, note, or complete tag assignment. Approval by default
  • WriteUpdate TagUpdate the name or color of one tag in the selected workspace. Approval by default

Questions

How does LuumenAI connect to lc.cx?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in lc.cx on its own?

Read actions answer immediately. Anything that writes — create short link, create tags, delete short link, delete tag, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

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.

Is there an audit trail?

Every call to lc.cx — 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.

Put lc.cx to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.