Docs
Linky docs
Linky turns many URLs into one short launch link, and agents are the first-class caller. These docs cover every surface — skill, CLI, SDK, curl — and the identity-aware resolution layer on top.
What Linky is
One launch bundle, one short URL. Give POST /api/links a list of URLs and get back /l/[slug]. Share it. The recipient clicks Open All and the tabs fire — with popup-blocker fallbacks baked in.
Attach a resolution policy and the same Linky opens a different tab set per viewer. Unmatched or anonymous viewers fall through to the public bundle, so the URL stays safe to share in public channels.
Three ways to create
- Cursor skill — install the skill and let the model emit Linky URLs at the end of every task.
- CLI / SDK — linky create <url> for shells and CI;
createLinky()for scripts. - Direct API — a single
POST /api/linksworks from any HTTP-capable agent, including curl and edge functions.
Start here
- Install — skill, CLI, curl baseline.
- Quick start — create, launch, optionally claim, optionally personalize.
- Create — the canonical
POST /api/linkscontract. - Personalize — the DSL, the operators, and the dashboard editor.
Team it up
On org workspaces every Linky is team-owned. Three derived roles — admin, editor, viewer — gate who can edit, delete, and manage API keys. Owner-side insights answer whether your audience arrived and which rule they matched, with zero viewer tracking.
- Access control — the three derived roles, the Clerk mapping, and how to change them.
Reference