> ## Documentation Index > Fetch the complete documentation index at: https://docs.utmkit.co/llms.txt > Use this file to discover all available pages before exploring further. # UTMKit documentation > What UTMKit is, and where to start whether you use the console or integrate with the API and the MCP. UTMKit makes **governed short links**. A short link is a short address that sends a visitor to a longer one, with the UTM parameters (`utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`) already applied to the destination. A *governed* short link is one whose UTM values passed your workspace's rules before it was created: the casing and separator you chose, the parameters you made mandatory, the values you approved, and the pairings you allowed. A value that breaks a rule is refused, and the refusal says why and what would have been accepted. The result is a set of links whose reports add up, because nobody could coin `Facebook`, `facebook` and `FB` for the same channel. Everything happens inside a **workspace**, one per client or team, and the first way to talk to a workspace is a conversation: you ask the assistant for a link and it creates it, under the same rules the pages enforce. Sign up, get your first workspace and create your first governed link — no code involved. The REST API and the MCP server, the tokens that open them, and the reference for every operation. The guides follow roughly the order of the console: links, QR codes, campaigns, rules, analytics and reports, workspaces and organizations, billing, security. The developer material sits apart in its own section, so a page in the guides never asks you to read a command.