Install Jentic One Beta

Connect the Link Center API to your agent

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

Create a short link and QR code from a destinationUrl with optional name, tags, slug, and note

Change a link's destinationUrl or deactivate it with the active flag, so printed QR codes keep working

Set link expiry with expiresAt or expiresIn and choose an expiredBehavior such as redirect_fallback

Pull 30-day scan analytics with totalScans, a daily series, and byCountry and byDevice breakdowns

GET STARTED

Start building with Link Center API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Link Center API for, with concrete tasks.

★ Agent-managed campaign QR codes through Jentic

A developer's agent, connected through Jentic, creates a QR code for each printed campaign asset by calling the link-create operation with a destinationUrl, a name, and campaign tags. When the landing page moves, the agent patches the destinationUrl on the existing link, and every printed code follows it, because the QR encodes the stable short URL.

Call POST /api/v1/links with destinationUrl='https://example.com/spring-menu', name='Spring menu poster', and tags=['spring-2027'], then later PATCH /api/v1/links/{id} with destinationUrl='https://example.com/summer-menu'

Scan reporting for print campaigns

To see which posters or packaging codes are working, an agent pulls the 30-day analytics for each link. The response holds totalScans for all time, total30d, a daily series of date and count, and byCountry and byDevice arrays, which the agent turns into a short report comparing assets.

Call GET /api/v1/links to find the links tagged 'spring-2027', then GET /api/v1/links/{id}/stats for each and rank them by total30d

Time-limited promotional links

A promotion that ends on a set date needs its link to stop pointing at the offer. The link can carry expiresIn such as 30d or an expiresAt timestamp, with expiredBehavior set to redirect_fallback and an expiredRedirectUrl, so visitors who scan after the offer ends land on a useful page instead of an error.

Call POST /api/v1/links with destinationUrl='https://example.com/black-friday', expiresIn='30d', expiredBehavior='redirect_fallback', and expiredRedirectUrl='https://example.com'

Branded QR images for print and web

Design teams want every code to match the brand. A branding template stores a style such as dot colour plus a logoUrl, and links reference it through brandingTemplateId. The QR image endpoint then returns the styled code as png or svg, and needs no credential, so the URL can be embedded directly in an img tag.

Call POST /api/v1/branding-templates with name='Brand default' and a logoUrl, then GET /api/v1/links/{id}/qr with format='svg' for a link that uses that brandingTemplateId

Key Endpoints

13 endpoints — the link center api creates dynamic qr codes and short links whose destination can be changed at any time, because each qr encodes a stable short url rather than the final address.

METHOD

PATH

DESCRIPTION

POST

/api/v1/links

Create a link

PATCH

/api/v1/links/{id}

Update a link

GET

/api/v1/links

List links

GET

/api/v1/links/{id}/stats

Get 30-day scan analytics

GET

/api/v1/links/{id}/qr

Render the link's QR image

POST

/api/v1/qr

Render an ad-hoc QR

POST

/api/v1/branding-templates

Create a branding template

POST

/api/v1/links

Create a link

PATCH

/api/v1/links/{id}

Update a link

GET

/api/v1/links

List links

GET

/api/v1/links/{id}/stats

Get 30-day scan analytics

GET

/api/v1/links/{id}/qr

Render the link's QR image

POST

/api/v1/qr

Render an ad-hoc QR

POST

/api/v1/branding-templates

Create a branding template

Why Jentic?

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

Setup

Wiring Link Center by hand means sending a bearer key on most calls but not the public QR image route, choosing between expiresAt and expiresIn, and knowing which link fields need a Pro plan. Through Jentic you install once, import Link Center from the API Directory, store the key once, and your agent calls it.

Permission scoping

Link Center puts the link id in the URL path, as in /api/v1/links/{id}, so a rule can pin your agent to specific links and the operations you pick. You choose the operations it may call, so destructive ones like deleteLink or deleteBrandingTemplate are not included unless you add them.

Credential isolation

Your Link Center API 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 QR code' or 'get scan analytics for a link', and Jentic returns the matching Link Center operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Link Center API through Jentic.

What authentication does the Link Center API use?

Per its OpenAPI spec, the Link Center API uses a bearer token: the API key from Settings, API keys, sent as Authorization: Bearer. One operation needs no credential: GET /api/v1/links/{id}/qr is public so the QR image can be opened in a browser or embedded in an img tag. Through Jentic, the key is stored once by your own Jentic One instance and injected at call time.

Can I change where a QR code points after it is printed?

Yes. The QR encodes the link's stable short URL, so PATCH /api/v1/links/{id} with a new destinationUrl redirects every existing scan. You can also set active to false to switch a link off without deleting it.

What scan analytics does the Link Center API return?

GET /api/v1/links/{id}/stats returns linkId, totalScans for all time, total30d for the last 30 days, a days array of date and count, and byCountry and byDevice breakdowns. The window is fixed at the last 30 days.

What are the rate limits for the Link Center API?

The OpenAPI spec does not specify rate limits. Several link fields, such as slug, password, logoUrl, and routing rules, are marked as Pro features in the spec, so plan limits may apply; see https://mylink.center for current terms.

How do I create a QR code through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Link Center API from the API Directory, and store your API key once. Your agent searches for 'create a dynamic QR code', gets createLink with its input schema, and calls it with a destinationUrl. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For a reporting agent, write a rule that allows listLinks and getLinkStats, so it can read links and scan numbers but cannot create, repoint, or delete anything. To let it repoint one campaign link, add updateLink restricted to that link's id in the path.

Mylink Center Link Center API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer13 EndpointsREST

For Agents

Create and edit dynamic QR codes and short links, change their destination without reprinting, pull 30-day scan analytics, and render branded PNG or SVG QR images.

Use for: Create a QR code that points to our spring menu page, Change where the conference poster QR code sends people, Get the scan count for the flyer QR code this month, Find all links tagged with the campaign name

Not supported: Does not send emails or SMS, host landing pages, or report analytics beyond the last 30 days. Use for dynamic QR codes, short links, and scan stats only.

The Link Center API creates dynamic QR codes and short links whose destination can be changed at any time, because each QR encodes a stable short URL rather than the final address. Links carry tags, notes, expiry settings with a choice of post-expiry behaviour, optional password protection, custom social previews, and ordered routing rules. The API returns 30-day scan analytics per link with daily counts and country and device breakdowns, and renders branded QR images as PNG or SVG using saved branding templates or inline styles.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

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).

14%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

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

58%

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.

62%

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

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Link Center API to your agent

Capabilities

Start building with Link Center API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mylink Center Link Center API

Jentic AI Readiness Score

Link Center 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