API · CLI · MCP

Let your agents make the codes.

Create and re-point QR redirects from a script, a CI job, or an AI agent. A clean REST API, a one-line CLI, and an MCP server — same rules and quotas as the dashboard.

REST API

One call, one code

A single POST returns a live hopp.qr-redirects.be link and its PNG/SVG. Idempotent, paginated, typed.

CLI

hopp create

One static binary. Auth with an env var, human output by default, --json for machines.

MCP SERVER

Drop it into an agent

Exposes create_code, point_code, list_codes, get_stats as tools any LLM agent can call.

Command line

# create a code — the destination can change later
hopp create --url https://example.com/launch \
     --name "Launch poster"
→ hopp.qr-redirects.be/NHDGYUJKK
  wrote qr.png, qr.svg

# re-point it after the campaign — no reprint
hopp point NHDGYUJKK --url https://example.com/v2
→ updated. next scan goes to /v2

# list every redirect you own
hopp list
→ NHDGYUJKK  active  https://example.com/v2

# pull stats as JSON for your dashboard
hopp stats NHDGYUJKK --since 30d --json

REST / agent tool call

POST /v1/codes
Authorization: Bearer hopp_live_•••
{
  "url": "https://example.com/launch",
  "name": "Launch poster"
}

// 201 Created
{
  "id": "qr_8KZ2…",
  "slug": "NHDGYUJKK",
  "short_url": "https://hopp.qr-redirects.be/NHDGYUJKK",
  "png": "https://…/qr.png",
  "svg": "https://…/qr.svg"
}

# list your redirects
GET /v1/codes
// { "data": [ {"slug":"NHDGYUJKK","status":"active","short_url":"…"} ] }

Create a code, re-point it later — that's the whole loop.

Quotas and the daily cap apply exactly as in the UI. Scope keys to specific codes.

Get an API key Read the docs