URL Shortener

lc.cx, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your lc.cx account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • URL Shortener
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What lc.cx is

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

You paste in a key from your own lc.cx account. It is kept encrypted, and you can withdraw it from inside lc.cx whenever you like.

How a run works

One message in, the work done in lc.cx.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in lc.cx. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own lc.cx account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in lc.cx

These are the ready-made tools your AI employee already has in lc.cx. It is not limited to them, but it never has to be taught these.

  • Create Short LinkShorten one destination URL on lc.cx, optionally choosing its path, tags, note, and workspace. Warning: each successful creation permanently consumes one unit of the current monthl
  • Create TagsCreate one or more tags in a workspace and return their ids for attaching to short links.
  • Delete Short LinkPermanently delete one short link. Deletion does not restore the monthly creation quota.
  • Delete TagPermanently delete one tag from the selected workspace.
  • Get Account ContextReturn lc.cx plan and short-link quota information together with available domains and workspaces needed to create and route short links.
  • Get Short LinkRetrieve one short link by its lc.cx link id from the selected workspace.
  • List Short LinksReturn one page of recently created short links in the selected workspace, with an offset for the next page when one may exist.
  • List TagsReturn all tags available in the selected workspace for organizing short links.
  • Update Short LinkUpdate a short link's destination, note, or complete tag assignment. tagids is the full replacement list; resend current ids to preserve them or [] to clear.
  • Update TagUpdate the name or color of one tag in the selected workspace.
Access, and who is in charge of it

You stay the boss of your lc.cx account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own lc.cx account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in lc.cx is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in lc.cx and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about lc.cx

Can an AI employee really work inside lc.cx?
Yes. It signs in to your own lc.cx account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of lc.cx?
No. Nothing moves and nothing is replaced. Your records stay in lc.cx, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my lc.cx account?
You paste in a key from your own lc.cx account. It is kept encrypted, and you can withdraw it from inside lc.cx whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in lc.cx?
It has 10 ready-made tools in lc.cx today, among them Create Short Link, Create Tags and Delete Short Link. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use lc.cx and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in lc.cx and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in lc.cx?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in lc.cx is written down with what it did and when.