{"id":889,"date":"2026-04-30T00:10:46","date_gmt":"2026-04-30T07:10:46","guid":{"rendered":"https:\/\/qrchameleon.com\/blog\/?p=889"},"modified":"2026-05-28T12:15:13","modified_gmt":"2026-05-28T19:15:13","slug":"qr-code-api-ai-agents","status":"publish","type":"post","link":"https:\/\/qrchameleon.com\/blog\/qr-code-api-ai-agents\/","title":{"rendered":"QR Code API for AI Agents: Claude, ChatGPT, Gemini & Grok"},"content":{"rendered":"\n

Your AI agent can write a blog post. Generate marketing copy. Send a Slack message. Pull data from a CRM. Schedule an email.<\/p>\n\n\n\n

What it can’t do is hand someone something to scan.<\/p>\n\n\n\n

That’s the gap most agent builders hit somewhere around their fifth or sixth integration. The agent can produce text, structured data, and links \u2014 but the moment a workflow needs a printed artifact, a table tent, a business card, a refund slip, an event badge \u2014 there’s a wall. URLs don’t print well. They get shortened, mistyped, abandoned.<\/p>\n\n\n\n

A QR code API closes the gap. QR codes turn whatever your agent generates into something a phone camera can capture in 1.2 seconds, and with QR Chameleon’s API, your agent can mint them as easily as it sends an email \u2014 1,250 calls per month on the free plan, no credit card.<\/p>\n\n\n\n

This guide shows the working pattern for each major AI model: Claude, ChatGPT, Gemini, and Grok. Plus the Model Context Protocol (MCP) angle for builders who want a reusable server that any MCP-compatible agent can call. If you’ve never worked with QR generation before, our step-by-step guide on how to make a QR code for a link<\/a> walks through the fundamentals first.<\/p>\n\n\n\n

When AI Agents Need QR Codes<\/h2>\n\n\n\n

Agents don’t need QR codes. Workflows<\/em> need QR codes. The moment your agent’s job description includes “produce something a human will hold or print,” QR generation becomes a primitive \u2014 like sending an email or writing to a database.<\/p>\n\n\n\n

Here are the patterns we keep seeing:<\/p>\n\n\n\n

Customer service agents creating one-time refund or return codes<\/h3>\n\n\n\n

A support agent processing a return generates a unique tracked QR code that the customer prints, attaches to the package, and drops at any carrier. The QR encodes a short link that authenticates the return, logs the carrier scan, and updates the order status. Static QR generators can’t do this \u2014 every code is identical and untracked. With a dynamic QR API, every return gets its own code, scoped to one customer and one transaction.<\/p>\n\n\n\n

Marketing agents shipping campaign assets with tracked QRs<\/h3>\n\n\n\n

An agent that generates social posts, blog assets, or email creative attaches a unique QR code to every shipped piece. Each QR encodes a short link with UTM parameters<\/a> tagged automatically (utm_source<\/code>, utm_medium<\/code>, utm_campaign<\/code>) so attribution lands in your dashboard without anyone touching a spreadsheet. The agent that wrote the asset is the same agent that knows which campaign it belongs to \u2014 no human in the middle, no tags missed.<\/p>\n\n\n\n

Event agents generating per-guest invitations<\/h3>\n\n\n\n

An event registration agent creates a unique QR code per RSVP. The code encodes a short link to the guest’s personalized landing page (their name, their seat assignment, their badge data). Day-of, the same QR scans into the check-in app. One agent action, two production uses.<\/p>\n\n\n\n

Hospitality and onboarding agents creating WiFi access codes<\/h3>\n\n\n\n

A property management or hotel-onboarding agent generates a WiFi QR code with the network credentials baked in. Guest arrives, scans the code, joins the network \u2014 no asking the front desk, no fumbling with a passphrase. The agent can rotate credentials nightly and regenerate the code automatically; the printed display in the room never changes.<\/p>\n\n\n\n

Lead-gen agents creating personalized vCard QRs<\/h3>\n\n\n\n

A networking or trade show agent generates a unique vCard QR for each contact a sales rep wants to share. The QR encodes contact info plus a tracked redirect to a personalized landing page. Scan analytics tell the rep which conversations led to actual page visits \u2014 the bridge from “I gave them my card” to “they actually looked at my profile.”<\/p>\n\n\n\n

Inventory and asset-tagging agents generating bulk codes<\/h3>\n\n\n\n

A warehouse, fleet management, or healthcare agent provisions QR codes for every new asset entering the system. Each code is unique, tracked, and dynamically updateable \u2014 if an asset gets reassigned, the QR’s destination URL updates without reprinting. The agent that registers the asset is the same agent that mints the QR, in one transaction.<\/p>\n\n\n\n

The unifying pattern: the agent isn’t just<\/em> writing text. It’s producing something the physical world consumes. The QR code is the handoff.<\/p>\n\n\n\n

The QR Code API in 60 Seconds<\/h2>\n\n\n\n

Before we get to model-specific code, the API surface area is small enough to fit on one screen.<\/p>\n\n\n\n

Authentication:<\/strong> Bearer token in the Authorization<\/code> header. Get your key from the dashboard \u2192 Settings \u2192 API Keys.<\/p>\n\n\n\n

Base URL:<\/strong> https:\/\/qrchameleon.com\/api\/v1\/<\/code><\/p>\n\n\n\n

Core endpoint:<\/strong> POST \/urls\/bulk<\/code> \u2014 creates one or more dynamic short links, each of which automatically generates a downloadable QR code. Send up to 100 in a single request.<\/p>\n\n\n\n

curl -X POST https:\/\/qrchameleon.com\/api\/v1\/urls\/bulk \\\n  -H \"Authorization: Bearer YOUR_API_KEY\" \\\n  -H \"Content-Type: application\/json\" \\\n  -d '{\n    \"urls\": [\n      {\n        \"destination_url\": \"https:\/\/example.com\/launch\",\n        \"title\": \"Spring product launch\",\n        \"utm_source\": \"agent\",\n        \"utm_medium\": \"qr\",\n        \"utm_campaign\": \"spring-2026\"\n      }\n    ]\n  }'<\/code><\/pre>\n\n\n\n
Response:<\/strong><\/p>\n\n\n\n
{\n  \"success\": true,\n  \"data\": {\n    \"items\": [\n      {\n        \"index\": 0,\n        \"status\": \"created\",\n        \"short_url\": \"https:\/\/qrch.am\/U4im626B\",\n        \"short_code\": \"U4im626B\",\n        \"destination_url\": \"https:\/\/example.com\/launch\"\n      }\n    ]\n  }\n}<\/code><\/pre>\n\n\n\n
The short_url<\/code> is a tracked redirect. Every QR Chameleon short link automatically has a QR code generated for it \u2014 your agent can hand the short URL to a downstream tool that fetches the QR image, or the user can pull the QR from the dashboard. Because every short link is dynamic, the destination can change anytime without regenerating the printed code. That’s the static vs. dynamic QR distinction<\/a> \u2014 for AI agent workflows, dynamic is the only option that makes sense.<\/p>\n\n\n\n
That’s the entire surface area you need for 90% of agent workflows. Now let’s wire it into each major model.<\/p>\n\n\n
\n\n\n
\"Over-the-shoulder<\/figure>\n\n\n<\/p>\n\n\n
QR Code Generation from Claude (Anthropic API + Tool Use)<\/h2>\n\n\n\n
Claude generates QR codes through Anthropic’s tool use API. You define create_qr_code<\/code> as a tool, Claude decides when to call it based on the conversation, and your code executes the actual API call.<\/p>\n\n\n\n
import os\nimport requests\nimport anthropic\n\nclient = anthropic.Anthropic()\nQR_API_KEY = os.environ[\"QR_CHAMELEON_API_KEY\"]\n\n# 1. Define the tool Claude can call\nqr_tool = {\n    \"name\": \"create_qr_code\",\n    \"description\": (\n        \"Generate a dynamic, trackable QR code for any URL. \"\n        \"Returns a short URL (qrch.am\/...) whose QR pattern is \"\n        \"automatically generated. Use this whenever the user needs \"\n        \"a QR code for printed material, packaging, signage, or \"\n        \"any handoff between digital and physical.\"\n    ),\n    \"input_schema\": {\n        \"type\": \"object\",\n        \"properties\": {\n            \"destination_url\": {\n                \"type\": \"string\",\n                \"description\": \"The URL the QR code should redirect to.\"\n            },\n            \"title\": {\n                \"type\": \"string\",\n                \"description\": \"A label for finding this QR in the dashboard later.\"\n            },\n            \"utm_campaign\": {\n                \"type\": \"string\",\n                \"description\": \"Optional campaign tag for analytics attribution.\"\n            }\n        },\n        \"required\": [\"destination_url\"]\n    }\n}\n\n# 2. The function that actually calls QR Chameleon\ndef create_qr_code(destination_url: str, title: str = \"\", utm_campaign: str = \"\") -> dict:\n    payload = {\"urls\": [{\n        \"destination_url\": destination_url,\n        \"title\": title,\n        \"utm_source\": \"claude-agent\",\n        \"utm_medium\": \"qr\",\n        \"utm_campaign\": utm_campaign or \"default\"\n    }]}\n    r = requests.post(\n        \"https:\/\/qrchameleon.com\/api\/v1\/urls\/bulk\",\n        headers={\"Authorization\": f\"Bearer {QR_API_KEY}\"},\n        json=payload,\n        timeout=10\n    )\n    r.raise_for_status()\n    item = r.json()[\"data\"][\"items\"][0]\n    return {\n        \"short_url\": item[\"short_url\"],\n        \"short_code\": item[\"short_code\"]\n    }\n\n# 3. The agent loop \u2014 Claude calls the tool, you execute, return the result\nresponse = client.messages.create(\n    model=\"claude-sonnet-4-6\",\n    max_tokens=1024,\n    tools=[qr_tool],\n    messages=[{\n        \"role\": \"user\",\n        \"content\": (\n            \"We just shipped a new pricing page at \"\n            \"https:\/\/example.com\/pricing. Generate a QR code so \"\n            \"I can put it on the trade show booth banner.\"\n        )\n    }]\n)\n\n# Claude returns a tool_use block; you execute and feed the result back\nfor block in response.content:\n    if block.type == \"tool_use\" and block.name == \"create_qr_code\":\n        result = create_qr_code(**block.input)\n        print(f\"Booth banner QR: {result['short_url']}\")<\/code><\/pre>\n\n\n\n
In a real agent loop, you’d feed result<\/code> back into Claude as a tool_result<\/code> content block and continue the conversation, letting Claude format the response naturally. For full multi-turn semantics, see Anthropic’s tool use documentation<\/a>.<\/p>\n\n\n\n
The key thing to notice: Claude doesn’t generate the QR. It decides when one is needed<\/em>, and your tool produces it. That’s the right division of labor \u2014 the model handles intent, your code handles execution.<\/p>\n\n\n\n
QR Code Generation from ChatGPT (OpenAI Function Calling and Custom GPTs)<\/h2>\n\n\n\n
ChatGPT integrates with QR Chameleon two ways: function calling via the OpenAI API (for agents you build), or GPT Actions (for Custom GPTs in the ChatGPT app).<\/p>\n\n\n\n
Pattern 1: OpenAI Function Calling<\/h3>\n\n\n\n
import os\nimport json\nimport requests\nfrom openai import OpenAI\n\nclient = OpenAI()\nQR_API_KEY = os.environ[\"QR_CHAMELEON_API_KEY\"]\n\ntools = [{\n    \"type\": \"function\",\n    \"function\": {\n        \"name\": \"create_qr_code\",\n        \"description\": \"Generate a dynamic QR code that redirects to any URL. Returns a tracked short URL.\",\n        \"parameters\": {\n            \"type\": \"object\",\n            \"properties\": {\n                \"destination_url\": {\"type\": \"string\"},\n                \"title\": {\"type\": \"string\"},\n                \"utm_campaign\": {\"type\": \"string\"}\n            },\n            \"required\": [\"destination_url\"]\n        }\n    }\n}]\n\ndef create_qr_code(destination_url, title=\"\", utm_campaign=\"\"):\n    r = requests.post(\n        \"https:\/\/qrchameleon.com\/api\/v1\/urls\/bulk\",\n        headers={\"Authorization\": f\"Bearer {QR_API_KEY}\"},\n        json={\"urls\": [{\n            \"destination_url\": destination_url,\n            \"title\": title,\n            \"utm_source\": \"chatgpt-agent\",\n            \"utm_medium\": \"qr\",\n            \"utm_campaign\": utm_campaign or \"default\"\n        }]},\n        timeout=10\n    )\n    return r.json()[\"data\"][\"items\"][0]\n\nresponse = client.chat.completions.create(\n    model=\"gpt-4o\",\n    tools=tools,\n    messages=[{\n        \"role\": \"user\",\n        \"content\": \"Make a QR for our restaurant menu at https:\/\/example.com\/menu\"\n    }]\n)\n\ntool_calls = response.choices[0].message.tool_calls\nif tool_calls:\n    args = json.loads(tool_calls[0].function.arguments)\n    result = create_qr_code(**args)\n    print(f\"Menu QR: {result['short_url']}\")<\/code><\/pre>\n\n\n\n
Pattern 2: Custom GPT with GPT Actions<\/h3>\n\n\n\n
For Custom GPTs in the ChatGPT app, you don’t write Python \u2014 you upload an OpenAPI schema and ChatGPT calls QR Chameleon directly. In your Custom GPT’s “Actions” config, point at the QR Chameleon API base URL, set authentication to Bearer token, and paste an OpenAPI snippet describing the \/urls\/bulk<\/code> endpoint.<\/p>\n\n\n\n
End users of your Custom GPT then ask things like “Make me a QR for our holiday sale page”<\/em> and ChatGPT routes the call automatically. No backend code; the GPT itself becomes the agent.<\/p>\n\n\n\n
For the full OpenAI function calling spec, see the OpenAI function calling documentation<\/a>.<\/p>\n\n\n\n
QR Code Generation from Gemini (Google Function Calling)<\/h2>\n\n\n\n
Gemini’s function calling pattern mirrors OpenAI’s \u2014 define a function declaration, send it as a tool, parse the call.<\/p>\n\n\n\n
import os\nimport requests\nimport google.generativeai as genai\n\ngenai.configure(api_key=os.environ[\"GOOGLE_API_KEY\"])\nQR_API_KEY = os.environ[\"QR_CHAMELEON_API_KEY\"]\n\ncreate_qr_function = genai.protos.FunctionDeclaration(\n    name=\"create_qr_code\",\n    description=\"Generate a dynamic QR code that redirects to any URL.\",\n    parameters=genai.protos.Schema(\n        type=genai.protos.Type.OBJECT,\n        properties={\n            \"destination_url\": genai.protos.Schema(type=genai.protos.Type.STRING),\n            \"title\": genai.protos.Schema(type=genai.protos.Type.STRING),\n            \"utm_campaign\": genai.protos.Schema(type=genai.protos.Type.STRING),\n        },\n        required=[\"destination_url\"]\n    )\n)\n\ndef create_qr_code(destination_url, title=\"\", utm_campaign=\"\"):\n    r = requests.post(\n        \"https:\/\/qrchameleon.com\/api\/v1\/urls\/bulk\",\n        headers={\"Authorization\": f\"Bearer {QR_API_KEY}\"},\n        json={\"urls\": [{\n            \"destination_url\": destination_url,\n            \"title\": title,\n            \"utm_source\": \"gemini-agent\",\n            \"utm_medium\": \"qr\",\n            \"utm_campaign\": utm_campaign or \"default\"\n        }]},\n        timeout=10\n    )\n    return r.json()[\"data\"][\"items\"][0]\n\nmodel = genai.GenerativeModel(\n    model_name=\"gemini-2.5-pro\",\n    tools=[genai.protos.Tool(function_declarations=[create_qr_function])]\n)\n\nchat = model.start_chat()\nresponse = chat.send_message(\n    \"Generate a QR code for our event registration at https:\/\/example.com\/register\"\n)\n\n# Extract and execute the function call\nfor part in response.parts:\n    if part.function_call:\n        result = create_qr_code(**dict(part.function_call.args))\n        print(f\"Event QR: {result['short_url']}\")<\/code><\/pre>\n\n\n\n
Gemini’s function calling docs walk through the multi-turn pattern in detail at the Google AI function calling guide<\/a>. The schema definitions are slightly more verbose than OpenAI’s, but the pattern is identical \u2014 declare, call, execute, return.<\/p>\n\n\n\n
QR Code Generation from Grok (xAI API)<\/h2>\n\n\n\n
Grok’s API is OpenAI-compatible, which means the function calling pattern is nearly identical. You can reuse the OpenAI client with a different base URL and API key.<\/p>\n\n\n\n
import os\nimport json\nimport requests\nfrom openai import OpenAI\n\n# Grok uses an OpenAI-compatible API\nclient = OpenAI(\n    api_key=os.environ[\"XAI_API_KEY\"],\n    base_url=\"https:\/\/api.x.ai\/v1\"\n)\nQR_API_KEY = os.environ[\"QR_CHAMELEON_API_KEY\"]\n\ntools = [{\n    \"type\": \"function\",\n    \"function\": {\n        \"name\": \"create_qr_code\",\n        \"description\": \"Generate a dynamic, trackable QR code for any URL.\",\n        \"parameters\": {\n            \"type\": \"object\",\n            \"properties\": {\n                \"destination_url\": {\"type\": \"string\"},\n                \"title\": {\"type\": \"string\"},\n                \"utm_campaign\": {\"type\": \"string\"}\n            },\n            \"required\": [\"destination_url\"]\n        }\n    }\n}]\n\ndef create_qr_code(destination_url, title=\"\", utm_campaign=\"\"):\n    r = requests.post(\n        \"https:\/\/qrchameleon.com\/api\/v1\/urls\/bulk\",\n        headers={\"Authorization\": f\"Bearer {QR_API_KEY}\"},\n        json={\"urls\": [{\n            \"destination_url\": destination_url,\n            \"title\": title,\n            \"utm_source\": \"grok-agent\",\n            \"utm_medium\": \"qr\",\n            \"utm_campaign\": utm_campaign or \"default\"\n        }]},\n        timeout=10\n    )\n    return r.json()[\"data\"][\"items\"][0]\n\nresponse = client.chat.completions.create(\n    model=\"grok-4\",\n    tools=tools,\n    messages=[{\n        \"role\": \"user\",\n        \"content\": \"Make a QR code for our X profile so we can put it on a trade show booth\"\n    }]\n)\n\ntool_calls = response.choices[0].message.tool_calls\nif tool_calls:\n    args = json.loads(tool_calls[0].function.arguments)\n    result = create_qr_code(**args)\n    print(f\"Booth QR: {result['short_url']}\")<\/code><\/pre>\n\n\n\n
For Grok-specific features like the live search tool, see the xAI API documentation<\/a>. Because the API is OpenAI-compatible, anything that works with the OpenAI Python SDK works with Grok by swapping the base URL.<\/p>\n\n\n\n
MCP: Wrapping QR Chameleon as a Model Context Protocol Tool<\/h2>\n\n\n\n
Model Context Protocol (MCP) is the open standard from Anthropic for letting AI assistants connect to external tools. Build an MCP server once, and any MCP-compatible client (Claude Desktop, Claude Code, IDE integrations, third-party agents) can use it without you writing per-model integration code.<\/p>\n\n\n\n
Wrapping QR Chameleon as an MCP tool is straightforward \u2014 the protocol defines a tool schema, and the server exposes a callable handler that talks to the QR Chameleon API.<\/p>\n\n\n\n
# qr_chameleon_mcp_server.py\nimport os\nimport requests\nfrom mcp.server import Server\nfrom mcp.types import Tool, TextContent\n\nserver = Server(\"qr-chameleon\")\nQR_API_KEY = os.environ[\"QR_CHAMELEON_API_KEY\"]\n\n@server.list_tools()\nasync def list_tools() -> list[Tool]:\n    return [Tool(\n        name=\"create_qr_code\",\n        description=\"Generate a dynamic QR code that redirects to any URL.\",\n        inputSchema={\n            \"type\": \"object\",\n            \"properties\": {\n                \"destination_url\": {\"type\": \"string\"},\n                \"title\": {\"type\": \"string\"},\n                \"utm_campaign\": {\"type\": \"string\"}\n            },\n            \"required\": [\"destination_url\"]\n        }\n    )]\n\n@server.call_tool()\nasync def call_tool(name: str, arguments: dict) -> list[TextContent]:\n    if name != \"create_qr_code\":\n        raise ValueError(f\"Unknown tool: {name}\")\n\n    r = requests.post(\n        \"https:\/\/qrchameleon.com\/api\/v1\/urls\/bulk\",\n        headers={\"Authorization\": f\"Bearer {QR_API_KEY}\"},\n        json={\"urls\": [{\n            \"destination_url\": arguments[\"destination_url\"],\n            \"title\": arguments.get(\"title\", \"\"),\n            \"utm_source\": \"mcp-client\",\n            \"utm_medium\": \"qr\",\n            \"utm_campaign\": arguments.get(\"utm_campaign\", \"default\")\n        }]},\n        timeout=10\n    )\n    item = r.json()[\"data\"][\"items\"][0]\n    return [TextContent(\n        type=\"text\",\n        text=f\"Created QR code: {item['short_url']} (code: {item['short_code']})\"\n    )]\n\nif __name__ == \"__main__\":\n    import asyncio\n    from mcp.server.stdio import stdio_server\n    asyncio.run(stdio_server(server))<\/code><\/pre>\n\n\n\n
Configure Claude Desktop, Claude Code, or any MCP client to launch this server, and from that point forward the QR generation tool is available to whichever model the client routes to. One server, every agent.<\/p>\n\n\n\n
For the full MCP spec, see modelcontextprotocol.io<\/a>.<\/p>\n\n\n\n
The Free Tier \u2014 1,250 Calls\/Month, No Credit Card<\/h2>\n\n\n\n
Most QR code APIs paywall access entirely. Bitly’s free plan has zero API. TinyURL’s free tier doesn’t include programmatic generation. QR Code Generator’s API access starts at $15\/month. (For a broader comparison of free options across the QR and short link space, see our breakdown of the free QR Chameleon plan<\/a>.)<\/p>\n\n\n\n
QR Chameleon’s free tier includes:<\/p>\n\n\n\n