Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flyn 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%2Fflyn.to%2Fflyn" | shStep 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%2Fflyn.to%2Fflyn" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Flyn API.
Shorten destination URLs into trackable short links, including bulk creation of many links to one destination
Generate a QR code for a link or encode arbitrary content as a QR image
Add, update, and verify custom branded domains for short links
Record conversions through the conversion and postback endpoints and pull a conversion report
Attach, edit, and remove retargeting pixels on your links
GET STARTED
Register webhooks for link events and send a test delivery
List the click activity for an individual short link
Patterns agents use Flyn API for, with concrete tasks.
★ Agent-Driven Link Automation
An AI agent connected through Jentic can turn any destination into a branded short link, generate its QR code, and then report on the clicks and conversions the link drives, without a developer wiring the Flyn API by hand. The agent discovers the right operation by intent and calls it with a stored credential.
Shorten a campaign landing page URL, generate a QR code for the new link, and return the short URL and QR image
Campaign Link Tracking
Marketing teams shorten every campaign URL through Flyn, attach retargeting pixels, and measure which links drive conversions. Flyn records conversions through its ingest and postback endpoints and returns a conversion report, so spend can be attributed to specific links.
Create a short link for a promotion, attach a retargeting pixel, and read the conversion report after the campaign
Branded Domain Short Links
Businesses serve short links from their own verified domain instead of a generic shortener host. Flyn adds a custom domain, verifies it, and issues short links on that domain, keeping branding consistent across QR codes and shared links.
Add a custom domain, trigger its verification, and create a branded short link once the domain is verified
29 endpoints — the flyn api creates and manages short links, qr codes, and custom branded domains, then tracks every click and conversion that flows through them.
METHOD
PATH
DESCRIPTION
/api/links
Create a short link
/api/links/{id}/clicks
List clicks for a link
/api/shorten
Quick shorten a URL
/api/qr
Encode content as a QR code
/api/domains/add
Add a custom domain
/api/conversions
Get the conversion report
/api/webhooks
Create a webhook
/api/links
Create a short link
/api/links/{id}/clicks
List clicks for a link
/api/shorten
Quick shorten a URL
/api/qr
Encode content as a QR code
/api/domains/add
Add a custom domain
/api/conversions
Get the conversion report
/api/webhooks
Create a webhook
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Flyn API by hand means handling its bearer token, learning which endpoints accept unauthenticated conversion pixels, and building retry logic yourself. Through Jentic you install once, import Flyn from the API Directory, store the token once, and your agent calls it.
Permission scoping
Flyn exposes link, domain, pixel, conversion, and webhook operations, so a rule can let your agent create links and read click reports while leaving domain and webhook changes out. You choose the operations it may call, so destructive ones like deleting a link or removing a custom domain are not included unless you add them.
Credential isolation
Your Flyn token 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 'shorten a URL' or 'read click analytics', and Jentic returns the matching Flyn operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Flyn API through Jentic.
What authentication does the Flyn API use?
The Flyn API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec. The conversion ingest endpoints accept unauthenticated calls so they can be fired from a browser or a tracking pixel. Through Jentic your token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I create QR codes with the Flyn API?
Yes. Flyn can generate a QR code for an existing short link or encode arbitrary content as a QR image through its QR operations, returning the image for download or display.
Can I limit what my agent is allowed to do with the Flyn API?
Yes. Write a rule that allows only the link-creation and click-reporting operations, so the agent can shorten URLs and read analytics but cannot delete links, remove custom domains, or change webhooks. Every call it makes is logged.
Is there a Flyn MCP server?
You do not need an MCP server to give your agent the Flyn API. Jentic connects it directly from the API Directory: import Flyn, store your token once, and your agent calls its operations by intent, so no extra server's tool definitions sit in the agent's context.
What are the rate limits for the Flyn API?
The OpenAPI spec does not specify numeric rate limits for the Flyn API. Check the Flyn documentation at https://www.flyn.to for current limits before running high-volume link creation.
How do I shorten a URL with the Flyn API through Jentic?
Search Jentic for an intent like 'shorten a URL', and it returns Flyn's link-creation operation with its input schema so your agent can call it with a destination and get back a short link. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Create and manage short links, QR codes, and branded domains, then pull per-link click and conversion reports. Record conversions, attach retargeting pixels, and register webhooks for link events.
Use for: I want to shorten a long product URL into a branded short link, Create many short links that all point to one landing page, Generate a QR code for a short link, Check how many clicks a short link received
Not supported: Does not run paid ad campaigns, send emails, or manage a CRM. Use for short link creation, QR codes, and click and conversion tracking only.
The Flyn API creates and manages short links, QR codes, and custom branded domains, then tracks every click and conversion that flows through them. It records conversions through dedicated ingest and postback endpoints, attaches retargeting pixels to links, and fires webhooks when link events occur. Bulk link creation, per-link click reporting, and domain verification support campaigns that span many destinations.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>