Linqr App LinQR

Name: LinQR API
Brand: LinQR
Availability: InStock

✓ Official Vendor SpecMediaImage Processingoauth2, apiKey14 EndpointsREST

For Agents

Generate branded QR codes for text, contact, WiFi, payment, geo, and SMS payloads, with batch generation and custom embedded images for marketing and operations use cases.

Install Jentic One Beta

Connect the LinQR to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LinQR, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 LinQR API.

Generate QR codes for text, email, WiFi, contact, crypto, phone, SMS, geo, or arbitrary payloads via /qrcode/* endpoints

Produce QR codes in batches via POST /batch/qrcode for catalogue or campaign rollouts

Upload, list, and delete custom embedded images via /images endpoints to brand QR codes with logos

GET STARTED

Start building with LinQR API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use LinQR API for, with concrete tasks.

★ Branded Marketing QR Codes

Generate branded QR codes for marketing collateral, packaging, and print campaigns by uploading a logo image and embedding it in every code. The /images endpoints manage the logo library and the /qrcode endpoints reference an image id when creating each code. Suitable for marketing teams producing thousands of codes per campaign with consistent branding.

POST /images with the brand logo, then POST /qrcode with content=https://example.com/promo and the image id to produce a branded code.

WiFi and Contact Sharing

Produce QR codes that join a WiFi network or save a contact card on scan, useful for event venues, hotels, and conference badges. POST /qrcode/wifi accepts SSID, password, and security type, while POST /qrcode/contact accepts vCard fields. Both return ready-to-print images sized for badges or signage.

POST /qrcode/wifi with ssid=GuestNet, password=hello123, encryption=WPA2 and download the returned image for printing on event signage.

Bulk QR Generation for Catalogues

Generate hundreds or thousands of QR codes in a single call for product catalogues, asset tags, or ticketing systems. POST /batch/qrcode accepts a list of payloads and returns all generated images in one response, removing the need to orchestrate per-item requests. Best for one-off catalogue rollouts or seasonal campaign drops.

POST /batch/qrcode with an array of product URLs and persist each returned image with its product SKU.

AI Agent Code Generation

Let an AI agent produce a QR code on demand inside a chat, document, or workflow without surfacing OAuth client credentials. Through Jentic, the agent searches for the LinQR generate operation, loads the schema, and executes the right /qrcode/* endpoint while credentials stay isolated in the MAXsystem vault. The returned image can be inlined in chat or attached to a generated document.

Search Jentic for 'generate a QR code for a URL', load the schema, execute POST /qrcode with content=<user URL>, and return the image.

Key Endpoints

14 endpoints — linqr is a qr code generation api that produces visually customised codes for text, email, wifi credentials, contact cards, cryptocurrency payments, phone numbers, sms, and geolocation.

METHOD

PATH

DESCRIPTION

POST

/qrcode

Generate a QR code for arbitrary content

POST

/qrcode/wifi

Generate a WiFi QR code

POST

/qrcode/contact

Generate a contact (vCard) QR code

POST

/batch/qrcode

Batch generate multiple QR codes

POST

/images

Upload an embedded brand image

GET

/images

List embedded images

POST

/qrcode

Generate a QR code for arbitrary content

POST

/qrcode/wifi

Generate a WiFi QR code

POST

/qrcode/contact

Generate a contact (vCard) QR code

POST

/batch/qrcode

Batch generate multiple QR codes

POST

/images

Upload an embedded brand image

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LinQR OAuth2 client credentials and RapidAPI keys are stored encrypted in the Jentic MAXsystem vault and exchanged for short-lived tokens at execution time — agents never see the raw client secret or API key.

Intent-based discovery

Agents search by intent (e.g., 'generate a WiFi QR code') and Jentic returns the matching /qrcode/* operation with its input schema, removing manual navigation of LinQR docs.

Time to first call

Direct LinQR integration: 3-6 hours for OAuth2 setup and per-payload schema reading. Through Jentic: under 20 minutes — search, load schema, execute.

FAQs

Specific to using LinQR API through Jentic.

What authentication does the LinQR API use?

LinQR supports two schemes. OAuth2 client credentials are the recommended path for direct access via api.linqr.app. The RapidAPI proxy at qrcode3.p.rapidapi.com accepts an X-RapidAPI-Key header instead. Through Jentic, either credential set is stored in the MAXsystem vault and injected at execution time.

Can I generate QR codes for WiFi or contact cards with LinQR?

Yes. POST /qrcode/wifi accepts SSID, password, and security type. POST /qrcode/contact accepts vCard-style fields (name, phone, email). Both return image bytes ready to print, no client-side composition needed.

What are the request size and timeout limits for the LinQR API?

Maximum request size is 32MB and request timeout is fixed at 180 seconds. These limits matter most for /batch/qrcode jobs and for /images uploads when embedding large brand logos in codes.

How do I generate a branded QR code through Jentic?

Run pip install jentic, then upload a brand image once via POST /images. Search Jentic for 'generate a branded QR code', load the POST /qrcode schema, supply the image id with the QR payload, and execute. The returned image bytes can be saved or inlined directly.

Can LinQR produce QR codes in bulk?

Yes. POST /batch/qrcode accepts an array of payloads in one call and returns the generated images together, which avoids per-item HTTP overhead. Keep total request size under 32MB and the job under 180 seconds — split very large catalogues into multiple batches.

Linqr App LinQR

Connect the LinQR to your agent

Capabilities

Start building with LinQR API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs