Feed agents structured data.

Every rii.link answers machines as cleanly as it routes humans — agents create, route, analyze and audit links with nothing but HTTP.

One example conversation with an assistant, told in four connected HTTP calls around a single link, links.acme.com/webinar. First: asked to create a webinar signup link — POST /api/links creates it, answered live at links.acme.com/webinar, then the assistant asks whether to add German routing. Second: asked to route German visitors to /de — PATCH /api/links/webinar adds the rule, answered done, everyone else unchanged, then the assistant offers to generate a QR code for print. Third: asked how the webinar link is doing — GET /api/links/webinar/analytics returns the numbers, answered 4,812 clicks, 38% from Instagram, top geo Germany, the geo rule earning its keep, then the assistant offers to re-check the full setup before the next campaign. Fourth: asked to confirm the link is still set up right — GET links.acme.com/webinar resolves it, answered all healthy, active, the DE rule in place, SSL fine, 4,812 clicks and counting, then the assistant offers to set up the next campaign's links.

The payload

Everything an agent needs.
One response.

One stable JSON contract per link: destination, the full routing map, live analytics and preview metadata — documented and versioned.

GET rii.link/sale — application/json
{
  "status": "active",  "destination": "https://myshop.com",
  "routing": {
    "ios":     "apps.apple.com/app/id123",
    "android": "play.google.com/store/id123",
    "default": "myshop.com/web"  },
  "meta": {    "title": "Summer Sale 2026",
    "og_image": "cdn.rii.link/og/sale.png",    "clicks": 18423  },  "llm_ready": true}
routing

The whole device & geo map — not just one URL.

meta.clicks

Live numbers at resolve time, not a snapshot.

meta.title / og_image

Preview content without fetching the target.

llm_ready

A stable, documented contract agents can rely on.

Read the developer docs
Model Context Protocol

Let agents create, update & analyze links for you.

Connect rii.link as an MCP server and your AI assistant manages links the way it manages files — natural language in, real link operations out, analytics on demand.

Example conversation: the user asks the assistant to create a branded link for the summer sale that routes iPhone users to the App Store, and to show last week's clicks. The assistant calls the create_link tool to create rii.link/summer-sale with iOS traffic routed to the App Store, then calls get_analytics, which returns 18,423 clicks over the last 7 days with Germany as the top geography, and confirms the link is live with those results. MCP link management is in progress, planned for September 2026.

Links from a sentence

"Shorten this and route DE traffic to /de" becomes a real, live link — no dashboard clicks.

Update & route in place

Agents repoint destinations, add rules and rotate QR targets through typed tool calls.

Analytics on demand

Ask for clicks, geos or top links and get structured results back into the conversation.

create_linkupdate_linkadd_routing_ruleget_analyticslist_linksgenerate_qr

Ready to build smarter connections?

Branded links, visual routing and LLM-ready responses — start free, no credit card needed.

No credit cardFree forever tierGDPR / DSGVO compliantExport & leave anytime