Install Jentic One Beta

Connect the D-QR REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the D-QR REST 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%2Fgetdynamicqr.com%2Fgetdynamicqr" | 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%2Fgetdynamicqr.com%2Fgetdynamicqr" | 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 D-QR REST API.

Create a dynamic QR code whose target you can change after printing

Render a QR code image as SVG with an embedded logo

Read time-series scan analytics and paginated scan history for a QR code

Organise QR codes into folders and move codes between them

Create QR codes in bulk in a single request

GET STARTED

Start building with D-QR REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use D-QR REST API for, with concrete tasks.

★ Agent-Managed Dynamic QR Codes

An AI agent running a print or packaging campaign can call the D-QR REST API through Jentic to create a dynamic QR code, point it at a destination, and repoint it later without reprinting. The agent creates and updates the code and renders its image without the developer wiring the X-Client-ID and bearer auth by hand. Jentic returns the matching operation and its input schema so the agent manages the code inline.

Create a dynamic QR code pointing to a landing page, render its image, and later update the destination

Campaign Scan Analytics

A dashboard can report how a campaign's codes are performing by reading each code's time-series scan analytics and its paginated scan history. D-QR returns scan counts over a chosen range and a per-scan history, so a workflow can show when and how often each code was scanned and spot the best-performing placements.

Pull a QR code's scan analytics over a date range and list its most recent scans

Bulk QR Generation and Organisation

A team producing many codes at once can create them in bulk and sort them into folders rather than one at a time. D-QR creates QR codes in a single bulk request and moves codes into folders, so a workflow can generate a batch of codes for a product line and keep them grouped for reporting.

Create a batch of QR codes in bulk and move them all into a named folder

Key Endpoints

88 endpoints — the d-qr rest api creates and manages dynamic qr codes whose target you can change after the code is printed, and tracks every scan.

METHOD

PATH

DESCRIPTION

POST

/qrcodes

Create a QR code

PATCH

/qrcodes/{id}

Update a QR code's target

GET

/qrcodes/{id}/analytics

Get time-series scan analytics

GET

/qrcodes/{id}/scans

Get paginated scan history

POST

/qrcodes/render

Render a QR code image

POST

/qrcodes/bulk

Create QR codes in bulk

POST

/link-pages

Create a link page

POST

/qrcodes

Create a QR code

PATCH

/qrcodes/{id}

Update a QR code's target

GET

/qrcodes/{id}/analytics

Get time-series scan analytics

GET

/qrcodes/{id}/scans

Get paginated scan history

POST

/qrcodes/render

Render a QR code image

POST

/qrcodes/bulk

Create QR codes in bulk

POST

/link-pages

Create a link page

Why Jentic?

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

Setup

Wiring D-QR by hand means supplying both its X-Client-ID header and a bearer client secret, handling plan feature flags that return a 403 on otherwise valid tokens, and staying within its request rate limits. Through Jentic you install once, import D-QR from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

D-QR puts the resource id in the URL path, so a rule can bound your agent to the QR operations it needs and even to one code. You choose which operations it may call, so the admin operations and destructive ones like deleting a QR code are not included unless you add them.

Credential isolation

Your D-QR client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter 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 D-QR operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using D-QR REST API through Jentic.

What authentication does the D-QR REST API use?

The D-QR REST API authenticates API clients with an X-Client-ID header and a bearer client secret, while its mobile tokens use a bearer token alone, per its OpenAPI spec. Through Jentic the credentials are stored once, encrypted, by your own Jentic One instance and injected at call time, so they never reach the agent's prompt or logs.

Is there a D-QR MCP server?

You don't need an MCP server to give your agent the D-QR REST API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent can create and track QR codes straight away.

Can I limit what my agent is allowed to do with the D-QR REST API?

Yes. Write a rule that allows just the QR operations your agent needs, such as creating codes, rendering them, and reading scan analytics, so it cannot reach the admin operations like changing a user's plan or delete a QR code. Every call it makes is logged.

Can I change where a QR code points after it is printed with the D-QR REST API?

Yes. The codes are dynamic, so an agent updates a QR code to point at a new destination without reprinting it, and the code keeps accumulating scans against the same analytics record.

What are the rate limits for the D-QR REST API?

Its OpenAPI spec states that authenticated endpoints allow 60 requests per minute keyed by client id, and the auth endpoints allow 10 per minute. Responses carry X-RateLimit headers and a 429 response includes a Retry-After value.

How do I create a dynamic QR code with the D-QR REST API through Jentic?

Search Jentic for an intent like 'create a dynamic QR code' and it returns the D-QR create operation with its input schema, so your agent sends the destination and reads back the code and its image. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getdynamicqr D-QR REST API

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey, bearer88 EndpointsREST

For Agents

Create and manage dynamic QR codes whose targets you can change after printing, render them as images, and track scans with time-series analytics and scan history. Also builds link pages, folders, and business cards. Authenticates with an X-Client-ID header and a bearer client secret.

Use for: Create a dynamic QR code pointing to a URL, Change where an existing QR code redirects, Get the scan analytics for a QR code, Render a QR code image with my logo

Not supported: Does not handle payment processing, email campaigns, or SMS delivery. Use for creating and tracking dynamic QR codes only.

The D-QR REST API creates and manages dynamic QR codes whose target you can change after the code is printed, and tracks every scan. An agent creates a QR code, updates where it points, renders it as an image with an embedded logo, and reads time-series scan analytics and paginated scan history. It also organises codes into folders, creates codes in bulk, builds link pages and digital business cards, and verifies custom domains for the short links. Responses are JSON, and API clients authenticate with an X-Client-ID header plus a bearer client secret.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

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: BSignals: 4

32%

Example Density

How richly the API is illustrated with examples.

71%

Example Validity

Percentage of examples that conform to their schemas.

51%

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

77%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

87%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

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: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the D-QR REST API to your agent

Capabilities

Start building with D-QR REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getdynamicqr D-QR REST API

Jentic AI Readiness Score

D-QR REST 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