Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KlipLink 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%2Fklipl.ink%2Fkliplink" | 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%2Fklipl.ink%2Fkliplink" | 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 KlipLink API.
Create a KlipLink short link from a destination URL
List the short links belonging to a KlipLink account
Look up a short link by its short URL identifier
Update or delete an existing KlipLink short link
List the custom domains configured for branded short links
GET STARTED
Patterns agents use KlipLink API for, with concrete tasks.
★ Bulk Campaign Link Generation
Generate dozens of trackable short links per launch by scripting POST /v1/links instead of clicking through the dashboard. The endpoint accepts a destination URL and returns the short identifier, so a campaign manager can wire it into a Google Sheet or an internal launch tool. Useful for newsletters, paid social, and influencer programs that need consistent UTM-laden links.
For each row in the campaign sheet, call POST /v1/links with the destination URL and write the returned short URL back into the row.
Link Inventory and Cleanup
Inventory existing short links and prune what has gone stale. GET /v1/links lists current links and GET /v1/links/{short_url} returns the detail for any single one. Useful for marketing leads inheriting an account that has accumulated hundreds of short links from past launches.
List all KlipLink short links via GET /v1/links and flag any pointing to URLs that return HTTP 404 for review.
Branded Custom Domain Setup
Audit and use the custom domains configured for branded short links. GET /v1/domains lists configured domains so an agent can pick the correct one when creating a new branded link. Critical for brands running multiple regional or product domains who need to route each link to the right host.
List KlipLink domains via GET /v1/domains and create a short link on the brand domain pointing to https://example.com/launch.
Agent-Driven Link Operations via Jentic
Let an AI agent generate a short link as part of a larger workflow - drafting a tweet, building a campaign brief, or composing a newsletter. The agent searches Jentic for 'create a KlipLink short link', loads the schema, and executes with the bearer token kept in your Jentic One instance. The result is a single short URL ready to drop into the surrounding content.
Through Jentic, search for 'create a KlipLink short link', load POST /v1/links, and shorten the URL https://example.com/launch.
6 endpoints — jentic publishes the only available openapi specification for kliplink api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v1/links
Create a short link
/v1/links
List short links
/v1/links/{short_url}
Retrieve a specific short link
/v1/domains
List custom domains
/v1/links
Create a short link
/v1/links
List short links
/v1/links/{short_url}
Retrieve a specific short link
/v1/domains
List custom domains
What agents get from Jentic-routed access to this vendor.
Setup
Wiring KlipLink by hand means learning its bearer token auth and handling the api.klipl.ink host and its errors yourself. Through Jentic you install once, import KlipLink from the API Directory, store the token once, and your agent calls it.
Permission scoping
KlipLink takes a short URL in the URL path only on the read endpoint (/v1/links/{short_url}), so scope by operation: limit the agent to the operations it needs, such as listing links or looking one up, and leave link creation and domain reads out unless you add them.
Credential isolation
Your KlipLink 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 'create a short link' or 'list my short links', and Jentic returns the matching KlipLink 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 KlipLink API through Jentic.
Why is there no official OpenAPI spec for KlipLink API?
KlipLink does not publish an OpenAPI specification - its public API is currently flagged as experimental. Jentic generates and maintains this spec so that AI agents and developers can call KlipLink API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the KlipLink API use?
The KlipLink API uses bearer token authentication. The token is sent as Authorization: Bearer <token> on every request. Through Jentic the bearer token is held in your Jentic One instance and never enters the agent's context.
Can I create branded short links on a custom domain through the KlipLink API?
Yes. List configured custom domains via GET /v1/domains and reference one when creating a link via POST /v1/links. Note the API is available to KlipLink paid plan users only.
What are the rate limits for the KlipLink API?
KlipLink does not publish a public rate limit and the spec does not declare one. The API is described as experimental, so treat it as best-effort and back off on errors rather than retrying tightly.
How do I shorten a URL from an AI agent through Jentic?
Search Jentic for 'create a KlipLink short link', load POST /v1/links, and execute with the destination URL. Jentic injects the bearer token from the vault and the agent receives the short URL ready to drop into outgoing content.
Is the KlipLink API free to use?
No. The KlipLink API is available to paid plan users only and is currently labelled experimental. Account credentials with API access are required.
Can I limit what my agent is allowed to do with the KlipLink API?
Yes. Because you run Jentic One yourself, your own rules decide which KlipLink operations and credentials the agent may use. You can scope the agent by operation, granting only what it needs such as listing links via GET /v1/links or looking one up via GET /v1/links/{short_url}, while leaving link creation through POST /v1/links and custom domain reads via GET /v1/domains out unless you add them. The bearer token is held by your own instance and injected at execution, so the agent never sees the credential and only ever calls the operations you allow.
Know of an official OpenAPI document? Contribute it →
For Agents
Create, list, and inspect KlipLink short links and the custom domains used to brand them.
Use for: Create a short link for a marketing campaign URL, List all KlipLink short links created this month, Find the KlipLink record for the short URL 'launch24', I want to delete a stale short link from KlipLink
Not supported: Does not handle deep link analytics dashboards, QR code rendering, or click-event streaming - use for short link creation, listing, and custom domain lookup only.
Jentic publishes the only available OpenAPI specification for KlipLink API, keeping it validated and agent-ready. KlipLink is a URL shortener and link management service available to paid users, with an experimental public API. The endpoints cover creating short links, listing and inspecting them, retrieving a short link by its short URL, and pulling the configured custom domains, so a marketing team can generate trackable links in bulk and audit their setup outside the dashboard. It is well suited for content teams that already use KlipLink and want to script their link operations.