Cli Clico API

Name: Clico API
Brand: Clico API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey7 EndpointsREST

For Agents

Mint and manage short links via Clico - create trackable URLs, read click statistics, and inspect the calling account, all behind a simple API key.

Install Jentic One Beta

Connect the Clico API to your agent

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

Create a short link from a destination URL with optional custom alias

List the short links owned by the authenticated account

Update the destination of an existing short link

Delete a short link that is no longer needed

GET STARTED

Start building with Clico API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Clico API for, with concrete tasks.

★ Trackable Links in Outbound Messages

Mint a short URL programmatically every time a backend system sends a marketing email, SMS, or notification, then read /links/{id}/stats later to attribute engagement. The /links POST endpoint accepts a destination URL and optional alias and returns the short URL ready to embed. Wiring this in usually takes under a day.

Create a short link for 'https://example.com/landing' via POST /links and return the resulting short URL

Click Attribution Reporting

Pull per-link click statistics from Clico into a daily report or BI dashboard to attribute engagement back to the campaign or message that minted the link. The /links/{id}/stats endpoint returns total click counts for each short link, which is enough to drive a campaign-level dashboard. A simple sync job takes a few hours.

Fetch /links/{id}/stats for short link id 'abc123' and return the click count for the last 7 days

Lifecycle Management of Short Links

Keep the short link estate clean by listing existing links, updating destinations when a target page moves, and deleting links that are no longer needed. The /links collection plus /links/{id} endpoints are sufficient for a maintenance script that runs on a schedule. Setup is typically under a day.

List all links, find any pointing at the legacy /old-page destination, and update each to the new /new-page URL

Agent-Driven Short Link Operations via Jentic

Expose Clico to an AI agent through Jentic so a marketer or operator can ask the agent to mint a trackable link or read its stats in natural language. Jentic isolates the API key and surfaces only the relevant Clico operations for the intent. A working integration takes well under an hour.

Search Jentic for 'create a short link', load POST /links, and execute it for destination 'https://example.com/promo'

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for clico api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/links

Create a new short link

GET

/links

List short links for the account

GET

/links/{id}

Read a single short link

DELETE

/links/{id}

Delete a short link

GET

/links/{id}/stats

Read click statistics for a short link

GET

/account

Read account metadata for the API key

POST

/links

Create a new short link

GET

/links

List short links for the account

GET

/links/{id}

Read a single short link

DELETE

/links/{id}

Delete a short link

GET

/links/{id}/stats

Read click statistics for a short link

GET

Why Jentic?

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

Setup

Wiring the Clico API by hand means sending your key in the X-API-Key header on every call to cli.com/api/v1 across its link and account operations. Through Jentic you install once, import Clico from the API Directory, store the key once, and your agent calls it.

Permission scoping

Clico puts the link id in the URL path (/links/{id}), so a rule can pin your agent to one link: it can read that link and its stats and nothing else. You choose the operations it may call, so deleting a link is not included unless you add it.

Credential isolation

Your Clico 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 short link' or 'get link stats in Clico', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Clico API through Jentic.

Why is there no official OpenAPI spec for Clico API?

Clico does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clico 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 Clico API use?

Clico uses a simple API key passed in the X-API-Key header on every request to https://cli.com/api/v1. When called through Jentic, the key is held in your Jentic One instance and injected into outgoing requests - it never enters the agent context.

Can I create short links with a custom alias?

Yes. POST /links accepts a destination URL and optional alias. If the alias is omitted, Clico returns a randomly generated short id; otherwise it uses your alias as the short slug.

Can I read click statistics for a short link?

Yes. GET /links/{id}/stats returns the click counters for a single short link, which is enough to attribute engagement back to the message that minted it.

What are the rate limits for the Clico API?

Clico does not document fixed numeric rate limits in the public spec. In practice, treat /links creation as a low-rate operation (a few per second per key) and prefer batched listing via GET /links over per-id fetches.

How do I mint a short link through Jentic?

Run pip install jentic, search for 'create a short link', load POST /links, and execute with the destination URL. Jentic injects the X-API-Key header from the vault and returns the created short URL.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Clico operations and credentials the agent may use. Because Clico puts the link id in the URL path (/links/{id}), you can pin the agent to a single link so it only reads that link and its click stats via GET /links/{id} and GET /links/{id}/stats. You choose the operations it may call, so higher-impact actions like DELETE /links/{id} or POST /links stay out of reach unless you explicitly allow them.

Cli Clico API

Connect the Clico API to your agent

Capabilities

Start building with Clico API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs