Goqr QR Code API

Name: QR Code API
Brand: QR Code API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingnone3 EndpointsREST

For Agents

Generate QR code images in PNG, SVG, or other formats and decode QR codes from uploaded images, with no authentication required.

Install Jentic One Beta

Connect the QR Code API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QR Code API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoqr.me%2Fgoqr" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoqr.me%2Fgoqr" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with QR Code API.

Generate a QR code image from arbitrary text, URL, or vCard data

Configure pixel size, margin, and quiet zone for print or web output

Customize foreground and background colors using hex or RGB

Choose error correction level L, M, Q, or H to balance density and resilience

GET STARTED

Start building with QR Code API

Explore with Jentic One

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for QR Code API, keeping it validated and agent-ready. The goQR.me QR Code API generates QR code images and decodes QR codes from uploaded image files. Code generation supports PNG, GIF, JPEG, JPG, SVG, and EPS output, configurable size, foreground and background colors, margin, quiet zone, and error correction levels L, M, Q, and H. Reading endpoints accept a single image or a multi-file batch and return the decoded payload as JSON or XML. The service is free, requires no authentication, and is rate-limited by the goQR.me terms of use.

Use Cases

Patterns agents use QR Code API for, with concrete tasks.

★ Marketing Campaign QR Generation

Bulk-generate branded QR codes for posters, flyers, and product packaging by calling /v1/create-qr-code/ with the campaign URL, brand colors, and the chosen error correction level. Output as SVG when designers need vector files, or PNG at high resolution for print runs. No authentication is required, so the service drops into a content pipeline without credential management.

Generate a 600x600 PNG QR for https://example.com/promo with foreground 1a73e8 and error correction H, then save it to the campaign assets folder.

Mobile Ticket Validation

Decode QR codes from photos uploaded by event staff at the gate. POST the image to /v1/read-qr-code/ as multipart form data, parse the JSON response, and look up the embedded ticket id in the box-office database. Multi-file mode lets staff scan multiple tickets in one round trip when network conditions are slow.

Upload ticket-photo.jpg to /v1/read-qr-code/ and verify the decoded payload matches a valid ticket id in the events table.

Inline QR for Email and PDF

Embed a freshly generated QR code into a transactional email or PDF by hot-linking the /v1/create-qr-code/ URL with the recipient-specific data parameter. Use SVG output for crisp rendering at any zoom level inside PDFs, or PNG for email clients that block SVG. Color and margin parameters keep the QR visually consistent with brand templates.

Build the URL https://api.qrserver.com/v1/create-qr-code/?data=ORDER123&size=200x200&format=svg and embed it as an img src in the order confirmation email template.

AI Agent Document Processing

An automated document agent inspects uploaded invoices and shipping labels, calls /v1/read-qr-code/ to extract embedded reference codes, and routes each document to the right downstream system. Through Jentic, the agent finds the operation by intent and uses the public endpoint without managing credentials, since the API requires none.

Read the QR from invoice-page-1.png and use the decoded value as the reference id when posting the invoice to the accounting system.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for qr code api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/create-qr-code/

Generate a QR code image from text or URL

POST

/v1/read-qr-code/

Decode QR codes from uploaded image files

GET

/v1/create-qr-code/

Generate a QR code image from text or URL

POST

/v1/read-qr-code/

Decode QR codes from uploaded image files

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

The QR Code API needs no credentials, but wiring it by hand still means matching create and read calls against the api.qrserver.com host and handling their parameters and multipart uploads yourself. Through Jentic you install once, import the QR Code API from the API Directory, and your agent calls it.

Permission scoping

The QR Code API takes no credentials and carries its content in the request query and body, so you limit the agent to the operations it needs, such as creating a QR code or decoding one from an image. You choose the operations it may call, so nothing beyond those is available unless you add it.

Credential isolation

The QR Code API requires no credentials, so there is nothing to store. Jentic still runs the calls through your own Jentic One instance so the agent works the same way it does for authenticated APIs.

Intent-based discovery

Agents search Jentic by intent such as 'decode a QR code from an image' or 'generate a QR code for a URL', and Jentic returns the matching goQR.me operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using QR Code API through Jentic.

Why is there no official OpenAPI spec for QR Code API?

goQR.me does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call QR Code API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the QR Code API use?

None. The goQR.me endpoints are public and require no API key, OAuth, or basic auth. Use is bound by the goQR.me terms of service, which include reasonable rate limits and a request to attribute commercial bulk usage.

Can I generate SVG QR codes with the QR Code API?

Yes. Pass format=svg in the query string of GET /v1/create-qr-code/ to receive a vector SVG. Other supported formats include png, gif, jpeg, jpg, and eps. SVG is the right choice for embedding in PDFs and high-resolution print.

How do I decode a QR code from an uploaded image?

POST the image as multipart form data to /v1/read-qr-code/. The response is JSON containing the decoded text or an error if no QR was found. The endpoint also accepts multiple files in one request and returns an array of per-file results.

How do I integrate the QR Code API with an AI agent through Jentic?

Run pip install jentic, search 'generate a qr code' to find GET /v1/create-qr-code/, load the schema, and execute. No credentials are required, so Jentic forwards the request directly. Get started with Jentic One, the self-hosted execution layer.

Can I limit what my agent is allowed to do with the QR Code API?

Yes. Because you run Jentic One yourself, your own rules decide which QR Code API operations the agent may call, so you can allow only creating a QR code from a URL or text and keep the decode-from-image operation off limits, or the reverse. The API takes no credentials and carries its content in the request query and body, so scoping the two available operations, create and read, is enough to bound what the agent can do. Any operation you do not grant stays unavailable to the agent.