Install Jentic One Beta

Connect the KuikCode API to your agent

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

Create a dynamic QR code with a name, destination, folderId, tags, UTM parameters, design or templateId, and optional accessCode password

Change where an already printed code points by updating its destination, singly or across many codes with the bulk update

Bulk-create codes from rows or CSV with a dryRun preview confirmed by previewHash

Read scans for a code, folder, or tag and pull scan totals and time series for a date range

GET STARTED

Start building with KuikCode API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use KuikCode API for, with concrete tasks.

★ Repointing Printed QR Codes

A restaurant or retailer prints codes once and changes what they open over time. The agent finds the code by tag or search query, updates its destination to the new menu or offer URL, and the printed code keeps working. For a whole campaign, the bulk update applies a new destination, folder, or tags to a list of code ids in one call.

Call GET /codes with tag 'spring' to find the menu codes, then PATCH /codes/bulk with their ids and a destination of type 'url' pointing to 'https://example.com/summer-menu'

Campaign Scan Reporting

Marketers want to know which printed placements work. The agent reads scan totals and a time series for a date range, filtered by folder or tag, and drills into the raw scans of one code, then summarises which placements drove the most scans. UTM parameters set on each code carry the campaign through to web analytics.

Call GET /analytics/summary and GET /analytics/timeseries with from '2026-10-01', to '2026-10-31', and tag 'trade-show', then GET /codes/{id}/scans for the top code

Bulk Code Generation for Locations

A chain with many stores needs one code per location. The agent sends rows or a CSV to the bulk-create operation with dryRun to get a preview and a previewHash, checks the preview, then confirms with that previewHash so the codes are created in a new or existing folder with a shared design or template.

Call POST /codes/bulk with a CSV of store URLs, dryRun true, and newFolderName 'Store doors', then repeat the call with the returned previewHash to create the codes

AI Agent QR Campaign Management via Jentic

An AI agent runs KuikCode through Jentic without handling the kc_live_ key. It searches by intent, receives the matching code, scan, or webhook operation with its input schema, and executes with the bearer key injected at run time, so repointing a code or pulling scan numbers is one step in a larger marketing workflow.

Search Jentic for 'change where a QR code points', load the PATCH /codes/{id} schema, and execute it with the code id and a new destination

Key Endpoints

53 endpoints — the kuikcode api creates dynamic qr codes whose destination can be changed after the code is printed, and reports every scan.

METHOD

PATH

DESCRIPTION

POST

/codes

Create a code

PATCH

/codes/{id}

Update a code

PATCH

/codes/bulk

Update many codes

POST

/codes/bulk

Create many codes

GET

/codes/{id}/image

Download the code's artwork

GET

/scans

List scans

GET

/analytics/timeseries

Scans over time

POST

/webhooks

Create a webhook

POST

/codes

Create a code

PATCH

/codes/{id}

Update a code

PATCH

/codes/bulk

Update many codes

POST

/codes/bulk

Create many codes

GET

/codes/{id}/image

Download the code's artwork

GET

/scans

List scans

GET

/analytics/timeseries

Scans over time

POST

/webhooks

Create a webhook

Why Jentic?

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

Setup

Wiring KuikCode by hand means sending a kc_live_ bearer key with the right read or write scope, following next_cursor through every list, sending Idempotency-Key on posts, and backing off on Retry-After. Through Jentic you install once, import KuikCode from the API Directory, store the key once, and your agent calls it.

Permission scoping

KuikCode puts the code id in the URL path (/codes/{id}), so a rule can pin your agent to one code and the operations you pick. You choose that set, so destructive ones like code deletion or webhook secret rotation are not included unless you add them.

Credential isolation

Your KuikCode 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 'QR code scans over time', and Jentic returns the matching KuikCode operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using KuikCode API through Jentic.

What authentication does the KuikCode API use?

Per its OpenAPI spec, the KuikCode API uses a scheme named apiKey that is sent as a bearer token: Authorization: Bearer kc_live_... with a key created under Settings, Developers. Keys belong to a workspace and are either read-only or read and write, and a read-only key on a write returns insufficient_scope. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

Can I change where a printed QR code points with the KuikCode API?

Yes. PATCH /codes/{id} accepts a new destination, and PATCH /codes/bulk applies a destination, folderId, tags, or archived flag to a list of ids at once. The printed code itself does not change, so the new destination takes effect on the next scan.

What are the rate limits for the KuikCode API?

The API docs in the OpenAPI spec say limits are per key and per minute, with writes drawing from a budget a third the size of reads. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, and a 429 includes Retry-After. The spec does not state the numeric budget, which depends on your plan.

How do I read scan analytics through Jentic with the KuikCode API?

Search Jentic for 'QR code scans over time' and it returns the time series operation with its input schema. Execute GET /analytics/timeseries with from, to, and an optional codeId, folderId, or tag, and use GET /analytics/summary for totals. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a KuikCode MCP server?

You don't need an MCP server to give your agent the KuikCode API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered by intent on demand, so no extra server's tool definitions are loaded into the agent's context.

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

Yes. A reporting agent can be given only the scan and analytics reads, so it can summarise campaign performance but cannot touch any code. If it should maintain a single code, allow GET and PATCH on that one code id and nothing else, and every call it makes is logged by your own instance.

KuikCode API

AI ReadinessFoundational (D+)50/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer53 EndpointsREST

For Agents

Create and restyle dynamic KuikCodes, repoint a printed code to a new destination, read scan analytics, and manage the folders, landing pages, and webhooks around them.

Use for: Create a QR code for the spring menu that points to our new page, Change the destination of the code printed on our table tents, How many scans did the trade show codes get last week?, List all codes tagged print in the Events folder

Not supported: Does not handle email campaigns, paid ad buying, or general web analytics beyond code scans. Use for creating dynamic QR codes, reading their scans, and managing the KuikPages and webhooks around them only.

The KuikCode API creates dynamic QR codes whose destination can be changed after the code is printed, and reports every scan. It files codes in folders with tags, applies designs, templates, and logos, adds UTM parameters, and can bulk-create or bulk-update codes, then exposes scan lists, totals, and time series filtered by code, folder, or tag. The same key also builds and publishes KuikPage landing pages, deploys hosted sites from a ZIP, collects form submissions, and sends scan events to signed webhooks.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

42%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

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

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the KuikCode API to your agent

Capabilities

Start building with KuikCode API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

KuikCode API

Jentic AI Readiness Score

KuikCode 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