Omny.link is a link platform built to be driven by AI agents. Over a single MCP connection, an assistant can create tracked short links and QR codes, route each click to the right destination for the visitor's device, and answer attribution questions in plain English. It is in private beta.

Which AI assistants can use it?

Any client that speaks the Model Context Protocol. That includes Claude Desktop, Claude Code, ChatGPT, and Cursor. You connect once per workspace rather than writing integration code per client.

What does MCP-native actually mean here?

The agent can complete the whole task, not just read data. It mints links, applies attribution, sets per-device routing rules, and queries analytics with write-back — over one connection, without per-client integration code.

How does one short link send iPhone and Android users to different places?

Routing happens at the edge on each click. iOS goes to the App Store, Android to Google Play, and desktop to the web, with optional country, region, and time-of-day rules. There is no JavaScript on the destination page, and every redirect is attributed back to the originating link.

Can QR codes carry our brand colours and logo?

Yes — module style, colour, and a centre logo are all configurable. Colour choices are contrast-checked when the code is created, because scanning depends on the difference between the module colour and its background. A palette too light to scan reliably is rejected before it reaches a print run.

Omny.link is invite-only during private beta and onboarding is done by hand. Submit a request from the home page with what you are running, and you will get a reply by email. Operators managing five or more clients are prioritised.

private beta · MCP for Claude · ChatGPT · Cursor

Tracked links your AI can actually create, route, and report on.

Q: Can I change where a printed QR code points after it ships?

Yes. The printed code is permanent but its destination is not. You can repoint the same code to a new campaign at any time, and every scan since the first print stays in one attribution history. This also covers recalls: a code already on packaging can be repointed to a safety notice the same day, with no reprinting.

One MCP connection turns your AI assistant into your link manager, QR generator, and analytics analyst — across every client you run.

Request access See how it works

invite-only · we reply to every request

mcp clientomny.link

Create 12 QR codes for the Q3 retail rollout — one per store. Route mobile traffic to the app, desktop to the web. Tag campaign.

Created campaign Q3 Retail Rollout. Generating 11/12 placements with device routing.

omny.linkq3-retail-rolloutlive · 11/12

device routing · per scan

iPhoneapp store · com.brand.retail62%

Androidplay store · com.brand.retail28%

Desktopbrand.com/locations10%

02What Omny.link does

Three verbs, one MCP connection.

Other shorteners stop at the redirect. Omny.link is built so an agent can run the whole loop — create the link, route the click, and answer the question your client just asked you on Slack.

01create

Tracked links your agent mints, not you.

Ask in plain English — UTMs, campaign, device rules, QR codes are inferred from context. Twelve at a time, twelve hundred at a time.

02route

One short link. Right destination. Every device.

iPhone goes to the App Store. Android to Play. Laptop to the web. Country, region, time-of-day rules optional. No JavaScript on the page.

03report

Plain-English answers from your link data.

Your agent has full write-back to analytics. Ask about conversion, cohort, channel, post — get the answer, not a dashboard you have to read.

03Why Omny.link

Every link tool can take an order now. Ours takes a hint.

Wiring an agent to an API is the easy half, and by now everyone has done it. The half that still lands on a person is attribution: which campaign this belongs to, which UTMs it should carry, which of the fourteen things named “may launch” you actually meant.

Omny.link treats that as the product. Say what the link is for in the words you'd use to a colleague; the tagging resolves itself, and shows you what it decided.

01You give it a hint, not a spec.: “The may newsletter blast” is enough. The campaign, the UTM set, and the workspace get resolved from it — you don't dictate them field by field.
02Most calls never reach a model.: Exact match first, fuzzy match second, model call only when the first two are genuinely ambiguous. Attribution stays fast and cheap at volume.
03Every guess shows its work.: You get the chosen campaign, a confidence score, and the runners-up it rejected — so a wrong guess is visible before it pollutes a quarter of reporting.

embed_tracking_linkcascade

destination: beautybox.com/may-launch

hint: “may newsletter blast”

tier 1

Rule lookup

Exact host + path match against the workspace's last 30 days of campaigns.

<50ms

tier 2

Fuzzy match

Edit-distance on slug + UTM bigrams. Picks the right “may launch” out of fourteen May campaigns.

<200ms

tier 3

Model fallback

One model call with workspace context. Returns a campaign plus one or two alternatives, confidence-scored.

✓ ~900ms

returns

url: omny.link/bb/may-news

campaign: May Launch · 92%

utms: utm_source=email · utm_medium=newsletter

alternatives: May Beauty · May 2026 newsletter

04What agents do with it

Three asks that used to take all morning.

Same chat window you already use. The work just stops bouncing back to a person.

agency operatorFriday morning

“Send Friday reports to all 12 retainers.”

Twelve drafts, one per client, in their brand voice — built from last week's scans, conversions, and top-performing posts.

9 hrsrecovered each Friday

in-house growthlaunch week

“Mint links + QRs for the Q3 retail rollout.”

One per store. Mobile to the app, desktop to the web. UTMs and store IDs inferred. Live in 11 seconds.

12 storeslive in 11 seconds

solo consultantmid-pitch

“Which IG post drove the BeautyBox upsell on May 4?”

IG Reel from May 4 — 312 clicks, 18 conversions, $2,340 attributed. Answer in the chat, not a dashboard.

$2,340attributed in 1 sentence

illustrative workflows · figures are examples, not customer results

05How it works

It's just a chat window. With teeth.

Twelve tracked links, twelve QR codes, device routing, attribution — all from one prompt. The chat below is the entire interface for that workflow.

mcp clientMCP · omny.link ✓

Make 12 QR codes for the spring-conference tables — one per table, all routing to greenleaf.com/menu. Tag the campaign correctly.

On it. Created campaign Spring Conference in GreenLeaf workspace. Generating 12/12 placements…

Done. Live and scannable. iPhones land on the menu in your iOS app, Pixels in the Android app, laptops at greenleaf.com — all attributed to the right table.

embed_tracking_link · 12create_campaign · 1

Live · QR factory

GreenLeaf · Spring Conference

style● dots▢ rounded■ squarecolorlogo✓ greenleaf.svg

table-01

table-02

table-03

table-04

table-05

table-06

table-07

table-08

table-09

table-10

table-11

table-12

scans tonight0iPhone · Pixel · Laptop

One workspace per client. Their colour, their mark.

contrast-checked at creation

GreenLeaf9.6:1 · scannable

BeautyBox6.0:1 · scannable

Northwind10.0:1 · scannable

Sparkfield6.6:1 · scannable

Rejected1.7:1 · won't scan

Brand colours get checked against the background before a code is issued. A palette too light to read is caught at creation — not after sixty thousand units are already printed.

device routing · live

One short link. Right destination. Every device.

One link · routed at the edgep95 · 18ms

omny.link/gl/menuincoming click

iPhoneiOS 18 · Safari

Mozilla/5.0 (iPhone; CPU iPhone OS 18_2…)

edge router · gl/menu

platform == ios → ios_url

platform == android → android_url

platform == web → web_url

✓ 302· logged · attributed

landed at

apps.apple.com/us/app/greenleaf

● App Store · attributed to gl/menu

● AASA hosted● assetlinks.json

06Print once

The packaging ships once. The campaign behind it doesn't.

A printed QR code is permanent — the label is already on the shelf. What it resolves to doesn't have to be. Point the same code at a new destination whenever the campaign changes, and every scan since the first print stays in one attribution history.

printed · march 2026 · 60k units

omny.link/gl/pack

Same code, every campaign below. Reprinting is what this replaces.

Mar 2026Spring menu→ greenleaf.com/spring-menuSeasonal dishes, table booking18,402scans
Jun 2026Summer giveaway→ greenleaf.com/summer-compEntry form, one scan per pack42,118scans
Sep 2026Loyalty signup→ greenleaf.com/rewardsAccount creation, repeat purchase27,655scans
Jan 2027Recall noticesame-day repoint→ greenleaf.com/safety/batch-11Batch 11 only, routed by GTIN3,904scans

resolving now

Recall notice

destination

greenleaf.com/safety/batch-11

reprints required

The recall row is the one that pays for the rest. When a batch has to be pulled, the code already on the shelf becomes the notice — repointed the same day, scoped by GTIN, without a single label being reprinted.

07Roadmap · public

What's shipping next.

nowMCP server · Claude · ChatGPT · Cursorin build
nowTracked short links · QR codes · device routingin build
nowWorkspace per client · brand voice · scoped tokensin build
nextGmail integration · send report drafts directlynext
nextSlack integration · “@omny what drove this?”next
laterCanva connector · QRs in your design filesplanned
laterSelf-host · agency-owned data planeplanned

08Questions

The things people ask first.

What is Omny.link?: Omny.link is a link platform built to be driven by AI agents. Over a single MCP connection, an assistant can create tracked short links and QR codes, route each click to the right destination for the visitor's device, and answer attribution questions in plain English. It is in private beta.
Which AI assistants can use it?: Any client that speaks the Model Context Protocol. That includes Claude Desktop, Claude Code, ChatGPT, and Cursor. You connect once per workspace rather than writing integration code per client.
What does MCP-native actually mean here?: The agent can complete the whole task, not just read data. It mints links, applies attribution, sets per-device routing rules, and queries analytics with write-back — over one connection, without per-client integration code.
Can I change where a printed QR code points after it ships?: Yes. The printed code is permanent but its destination is not. You can repoint the same code to a new campaign at any time, and every scan since the first print stays in one attribution history. This also covers recalls: a code already on packaging can be repointed to a safety notice the same day, with no reprinting.
How does one short link send iPhone and Android users to different places?: Routing happens at the edge on each click. iOS goes to the App Store, Android to Google Play, and desktop to the web, with optional country, region, and time-of-day rules. There is no JavaScript on the destination page, and every redirect is attributed back to the originating link.
Can QR codes carry our brand colours and logo?: Yes — module style, colour, and a centre logo are all configurable. Colour choices are contrast-checked when the code is created, because scanning depends on the difference between the module colour and its background. A palette too light to scan reliably is rejected before it reaches a print run.
How do I get access?: Omny.link is invite-only during private beta and onboarding is done by hand. Submit a request from the home page with what you are running, and you will get a reply by email. Operators managing five or more clients are prioritised.

Give your AI a link platform.

Omny.link is in private beta and we onboard by hand. Tell us what you're running and we'll get back to you — operators managing 5+ clients move first.