Install Jentic One Beta

Connect the QR Manager AI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QR Manager AI 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%2Fqr-manager.ai%2Fqr-manager" | 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%2Fqr-manager.ai%2Fqr-manager" | 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 Manager AI API.

Create a dynamic URL QR code with redirectUrl and utmSource, utmMedium, and utmCampaign tags

Encode vCard, WiFi, SMS, email, or phone details directly in a QR code using qrType

Style a code with fgColor, bgColor, gradientType, dotStyle, cornerStyle, and a frameStyle with frameText

Cap a code with maxScans or an expiresAt date and change its settings later by slug

GET STARTED

Start building with QR Manager AI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use QR Manager AI API for, with concrete tasks.

★ Agent-managed campaign QR codes through Jentic

A marketing agent creates tracked QR codes for each campaign and later reports on scans. Through Jentic it calls the create and analytics operations, the developer's own Jentic One instance injects the qrm_ bearer key, and a rule can pin the agent to specific code slugs so it cannot delete others.

POST /qr with qrType 'URL', title 'Summer Campaign', redirectUrl 'https://example.com/summer', utmCampaign 'summer26', then GET /qr/{slug}/analytics with range 7

Retargeting printed codes

Printed QR codes outlive the pages they point to. A dynamic URL code keeps its pattern while its redirectUrl is updated through PATCH /qr/{slug}, so posters and packaging keep working after a campaign page moves.

PATCH /qr/{slug} for the poster code with redirectUrl 'https://example.com/autumn'

Scan analytics reporting

GET /qr/{slug}/analytics and GET /analytics return scan data for one code or the whole account, filtered by range or period or by from and to dates with a timezone and granularity, so an agent can produce weekly scan reports per campaign.

GET /analytics with from '2026-11-01', to '2026-11-07', tz 'Europe/Dublin', and granularity 'day', then summarise scans per day

Usage alerts and expiry

Codes with maxScans or expiresAt limits need watching. PATCH /qr/{slug}/notifications sets thresholds such as notifyOnScansLeft and notifyOnExpiryDays, and notifyOnInactiveDays flags codes that stopped getting scans.

PATCH /qr/{slug}/notifications with notifyOnScansLeft 100 and notifyOnExpiryDays 7

Key Endpoints

12 endpoints — the qr manager ai api creates and styles qr codes and tracks how often they are scanned.

METHOD

PATH

DESCRIPTION

POST

/qr

Create a QR code

GET

/qr

List QR codes

PATCH

/qr/{slug}

Update a QR code

GET

/qr/{slug}/analytics

Get QR code analytics

GET

/analytics

Get account-wide analytics

PATCH

/qr/{slug}/notifications

Update notification settings

POST

/folders

Create a folder

POST

/qr

Create a QR code

GET

/qr

List QR codes

PATCH

/qr/{slug}

Update a QR code

GET

/qr/{slug}/analytics

Get QR code analytics

GET

/analytics

Get account-wide analytics

PATCH

/qr/{slug}/notifications

Update notification settings

POST

/folders

Create a folder

Why Jentic?

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

Setup

Wiring QR Manager AI by hand means issuing a qrm_ key, sending it as a bearer token, and mapping the long create body of style, redirect, and vCard or WiFi fields yourself. Through Jentic you install once, import QR Manager AI from the API Directory, store the key once, and your agent calls it.

Permission scoping

QR Manager AI puts the code slug in the URL path (/qr/{slug}), so a rule can pin your agent to one QR code: it can read analytics or update notifications for that code and nothing else. You choose the operations it may call, so destructive ones like QR code deletion or folder deletion are not included unless you add them.

Credential isolation

Your QR Manager AI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a dynamic QR code' or 'get QR scan analytics', and Jentic returns the matching QR Manager AI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using QR Manager AI API through Jentic.

What authentication does the QR Manager AI API use?

The QR Manager AI API declares an HTTP bearer scheme named ApiKeyAuth in its OpenAPI spec: you send an API key, prefixed with qrm_ and issued under Settings, API Keys, as a bearer token. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

Which plan do I need to create QR codes through the API?

Per the plan table in the spec, the Free tier has no API access, Starter covers listing, reading, analytics, notifications, and folders, and the Pro tier and above add creating, updating, and deleting QR codes.

What are the rate limits for the QR Manager AI API?

The OpenAPI spec does not state a request rate; its 429 response signals that a plan limit was reached. Check https://qr-manager.ai for the limits attached to your plan.

How do I create a tracked QR code with QR Manager AI through Jentic?

Install Jentic One, import the QR Manager AI API from the Jentic API Directory, and store your qrm_ key. Your agent searches for 'create a dynamic QR code', Jentic returns POST /qr with its schema, and the agent calls it with qrType, redirectUrl, and UTM fields. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a QR Manager AI MCP server?

You don't need an MCP server to give your agent QR Manager AI. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context.

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

Yes. For a reporting agent, write a rule that allows only GET /analytics and GET /qr/{slug}/analytics for the slug 'abc12345', so it can report scans for that one code while creating, retargeting, or deleting codes stays out of reach. Every call it makes is logged.

QR Manager AI API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage Processingbearer12 EndpointsREST

For Agents

Create, restyle, and retarget QR codes in QR Manager AI, read per-code and account scan analytics, set scan and expiry notifications, and file codes into folders.

Use for: Create a QR code for our summer campaign landing page, I want to change where the poster QR code redirects to, How many times was the menu QR code scanned last week?, Make a WiFi QR code for the office guest network

Not supported: Does not print materials, shorten links outside QR Manager AI, or run ad campaigns. Use for creating, styling, tracking, and organising QR codes only.

The QR Manager AI API creates and styles QR codes and tracks how often they are scanned. A code can be a dynamic URL redirect whose destination changes after printing, a short link, or a static vCard, WiFi, SMS, email, or phone code, styled with colours, gradients, dot and corner styles, frames, and logo sizing. It also returns per-code and account-wide scan analytics, sets scan and expiry alerts, and organises codes into folders.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

75%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

35%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

62%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

76%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the QR Manager AI API to your agent

Capabilities

Start building with QR Manager AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

QR Manager AI API

Jentic AI Readiness Score

QR Manager AI API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness