A QR code API. And an MCP server.

1. Get a key

On your account page, under API & MCP. Send it as a Bearer token. The secret is shown once; revoke and re-create any time.

2. Make a code

Generation runs the same engine and the same verification as the site. By default the code is activated on your plan and comes back ready to print.

curl -X POST https://ariaqr.com/api/v1/codes \
  -H "Authorization: Bearer aq_…" \
  -H "Content-Type: application/json" \
  -d '{
    "image_url": "https://example.com/artwork.png",
    "url": "https://example.com/menu",
    "edge": "soft"
  }'

{
  "job_id": "…",
  "verified": true,
  "activated": true,
  "code": "a7Bx9Q",
  "short_url": "ariaqr.com/r/a7Bx9Q",
  "preview_url": "https://ariaqr.com/api/preview/…",
  "download_url": "https://ariaqr.com/api/download/…",
  "stats_url": "https://ariaqr.com/stats/a7Bx9Q?k=…"
}

Other kinds use kind and fields, with the same field names as the generator: whatsapp, vcard, wifi, upi, email, phone, sms, maps, event, text. Send image_base64 instead of image_url if the image is not online. Set activate: false to generate without spending an activation; the response then carries a pay_url.

3. Read and change

# your codes
GET  https://ariaqr.com/api/v1/codes

# one code with its analytics
GET  https://ariaqr.com/api/v1/codes/a7Bx9Q

# point it somewhere else, no reprint
PATCH https://ariaqr.com/api/v1/codes/a7Bx9Q
      { "destination": "https://example.com/spring-menu" }

MCP server

Streamable HTTP at https://ariaqr.com/api/mcp, same Bearer key. Tools: create_code, list_codes, get_code_stats, set_destination.

// Claude Desktop / Cursor / any MCP client
{
  "mcpServers": {
    "ariaqr": {
      "url": "https://ariaqr.com/api/mcp",
      "headers": { "Authorization": "Bearer aq_…" }
    }
  }
}

# Claude Code
claude mcp add --transport http ariaqr https://ariaqr.com/api/mcp \
  --header "Authorization: Bearer aq_…"

Then ask: “Make an AriaQR code from this product photo that opens our booking page, and tell me how many scans it got this week.”

Limits and errors

• 60 requests a minute per key. 429 with a retry hint when exceeded.
• Images up to 10 MB, PNG, JPEG or WebP. Non-square images are centre-cropped; use the site for hand placement.
• Each activation counts against the plan’s 45 per quarter. 402 when none are left or the plan is not active.
• Errors are JSON: { "error": "…" } with the matching HTTP status.