vCard QR Code Generator

Developer API Docs, OpenAPI, and MCP Server

Use these resources when an AI agent, automation, or internal workflow needs to understand vCard QR Code Generator programmatically. The free browser generator remains privacy-first: contact data can stay on the user's device.

Predictable Agent URLs

REST API

The first public API supports discovery and vCard payload generation. It returns standard vCard text for QR encoding instead of storing contact details on a server.

All API errors use structured JSON with error.code, error.message, error.hint, error.docsUrl, and error.status. Agents can call either /v1/* or the common /api/v1/* aliases.

Mutation requests accept an optional Idempotency-Key header for retry correlation. API responses include RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers so agents can self-throttle.

Pagination is available at GET /api/v1/templates with limit, cursor, next_cursor, and has_more. Async job flows are available at POST /api/v1/jobs/vcard with a pollable Location URL.

Create a vCard payload
curl -X POST https://vcardqrcodegenerator.com/v1/vcard \
  -H "Content-Type: application/json" \
  -d "{\"fullName\":\"Asha Rao\",\"organization\":\"Northstar Studio\",\"title\":\"Founder\",\"phone\":\"+1 555 0100\",\"email\":\"asha@example.com\",\"website\":\"https://example.com\"}"

Streaming Support

Long-running agent workflows can use Server-Sent Events for progress feedback at GET https://vcardqrcodegenerator.com/v1/stream or GET https://vcardqrcodegenerator.com/api/v1/stream.

Stream progress events
curl -N "https://vcardqrcodegenerator.com/v1/stream?operation=create_vcard_payload"

MCP Tools

get_product_context

Returns product positioning, privacy notes, use cases, and integration URLs for agents evaluating QR code generator options.

create_vcard_payload

Accepts contact fields and returns vCard text suitable for QR encoding. The tool does not create an account or store the contact.

Auth and Access

Public discovery and vCard payload tools do not require authentication. Future account, dynamic QR, analytics, billing, or webhook endpoints should use the app subdomain and documented authenticated flows before agents are allowed to modify user-owned QR codes.

Integration Guides