aka.to

Bitly is built for human marketers, with an API bolted on. aka.to inverts that: every operation is an MCP tool, and the ones that benefit from a UI return interactive cards (sparklines, tables, breakdowns) rendered by the host alongside the structured output rather than as a JSON blob. There's a normal web dashboard too, but it isn't the headline.

The analytics are privacy-respecting by construction, not by policy. No IP addresses are persisted, no persistent visitor IDs, no cross-link identifiers. Click uniqueness comes from a per-link, per-organization-day rotating fingerprint that's hashed at request time and never reversed. The honest consequence: uniques count visitor-days rather than people, and the tooling says so instead of implying otherwise.

Underneath, a link is a destination and an alias is a sharing surface that owns the slug, the UTM parameters, and the click counters. One link can carry many aliases, so per-channel attribution works without duplicating the destination. Change it once and every alias follows. Generated slugs live in a global namespace; vanity slugs live per organization, so two teams can each own spring-sale.