Install Jentic One Beta

Connect the Cutt.ly URL Shortener API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cutt.ly URL Shortener 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%2Fhelp.cutt.ly%2Fcutt-ly" | 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%2Fhelp.cutt.ly%2Fcutt-ly" | 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 Cutt.ly URL Shortener API.

Shorten any long URL into a cutt.ly short link via GET /api.php

Request a custom slug for branded short links

Attach a name to a shortened link for later identification

Retrieve click statistics for an existing cutt.ly short link

Generate trackable links inline from an outbound email or SMS workflow

GET STARTED

Start building with Cutt.ly URL Shortener API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cutt.ly URL Shortener API for, with concrete tasks.

★ Trackable Links in Outbound Email

Marketing teams sending broadcast emails can call the Cutt.ly API at send time to convert each long destination URL into a short trackable link. The shortened link is dropped into the email body, and click counts are pulled back later for reporting. This avoids the need for a self-hosted link tracker and keeps the email payload small.

GET /api.php?key={apiKey}&short={longUrl}&name=campaign-2026-q2 and substitute the returned short link into the email body.

SMS Campaign Link Compression

SMS messages have a 160-character soft limit, so long marketing URLs eat into the message body and reduce conversion. Calling Cutt.ly before sending replaces the long URL with a short cutt.ly link that fits comfortably and remains trackable. The same call can request a branded slug so the recipient sees a consistent campaign code.

GET /api.php?key={apiKey}&short={longUrl}&user_domain=1 and use the response in the SMS body.

Click Reporting for a Campaign

After a campaign runs, the same /api.php endpoint can be called with the previously created short link reference to retrieve total clicks. Reporting jobs can iterate every named link from a campaign and roll the counts into a dashboard. This keeps marketing reporting honest without paying for an enterprise-tier tracker.

GET /api.php?key={apiKey}&stats={shortLinkId} for each campaign link and aggregate the click counts.

AI Agent Generating Short Links Inline

An AI agent drafting marketing emails, social posts, or SMS messages can call Cutt.ly through Jentic to produce a trackable short URL before the message is dispatched. Jentic isolates the API key so the agent never holds it in context and discovers the operation by intent. This is a small but useful tool for content-generating agents that need consistent tracking.

Search Jentic for 'shorten a url with cutt.ly', load the GET /api.php schema, and execute with the long URL and an optional name.

Why Jentic?

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

Setup

Wiring the Cutt.ly API by hand means learning its single /api.php endpoint, appending your key as a query parameter on every request, and switching on the action you want. Through Jentic you install once, import the Cutt.ly URL Shortener API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Cutt.ly exposes one operation at /api.php that shortens a URL and reads its click counts, and the target URL travels in the request parameters rather than a path id, so limit the agent to the operations it needs, such as shortening a link. Every operation you credit the agent with is in the allowed set you describe.

Credential isolation

Your Cutt.ly API key is stored once, encrypted, by your own Jentic One instance and added as the key query parameter 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 'get click counts for a short link', and Jentic returns the matching Cutt.ly operation with its input schema so the agent calls the right endpoint without reading the docs.

FAQs

Specific to using Cutt.ly URL Shortener API through Jentic.

Why is there no official OpenAPI spec for Cutt.ly URL Shortener API?

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

Cutt.ly uses an API key passed as the key query parameter on GET /api.php. There is no header-based auth and no OAuth flow. When called through Jentic, the API key is held in the vault and added to the request at execution time.

Can I request a custom slug with the Cutt.ly API?

Yes. Pass the optional name parameter on GET /api.php with the desired slug. If the slug is already in use, Cutt.ly returns an error code in the JSON response, so the integration should retry with an alternative.

What are the rate limits for the Cutt.ly API?

Cutt.ly does not document a strict public rate limit. Free accounts are subject to soft limits that scale with the plan tier. For bulk shortening jobs, batch calls and back off on error responses rather than retrying tightly.

How do I shorten a URL through Jentic?

Search Jentic for 'shorten a url with cutt.ly', load the GET /api.php schema, and execute with the long URL in the short parameter. Jentic appends the API key from the vault.

Can I retrieve click statistics for a cutt.ly link?

Yes. The same /api.php endpoint accepts a stats parameter that returns click counts and metadata for a previously created short link. Pair this with the name you set at shorten time so reporting jobs can correlate links to campaigns.

Can I limit what my agent is allowed to do with the Cutt.ly API?

Yes. Because Cutt.ly exposes a single operation at GET /api.php that both shortens a URL and reads its click counts, you decide in your self-hosted Jentic One instance whether the agent may call it at all, and the rules you set govern which operations and credentials it can use. You can, for example, allow the agent to shorten links while keeping the API key out of its prompt and context. Since the target URL travels in the request parameters rather than a path id, the operation you credit the agent with is the only one it can run.

Help Cutt Ly Cutt.ly URL Shortener API

AI ReadinessFoundational (D+)49/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMarketingMarketing AutomationapiKey1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Shorten a URL into a cutt.ly link and retrieve click statistics for it via a single GET endpoint.

Use for: I need to shorten a long landing page URL into a cutt.ly link, I want a branded short link with a custom slug, Get click statistics for a previously created cutt.ly link, Generate a trackable short URL before sending an email

Not supported: Does not host links on a custom domain, manage UTM tagging, or run campaign attribution - use for converting long URLs into cutt.ly short links and pulling their click counts only.

Jentic publishes the only available OpenAPI specification for Cutt.ly URL Shortener API, keeping it validated and agent-ready. Cutt.ly is a URL shortening service whose public API converts long URLs into short cutt.ly links and exposes click statistics for those links. The single endpoint is keyed by an account-level API key and accepts optional parameters for custom slugs and link names. It suits marketers and growth teams that want short branded links inside outbound emails, SMS, and social posts without standing up a self-hosted shortener.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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

62%

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.

50%

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

15%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Cutt.ly URL Shortener API to your agent

Capabilities

Start building with Cutt.ly URL Shortener API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Help Cutt Ly Cutt.ly URL Shortener API

Jentic AI Readiness Score

Cutt.ly URL Shortener 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