Cutt.ly Team API

Name: Cutt.ly Team API
Brand: Cutt.ly Team API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey1 EndpointsREST

For Agents

Shorten URLs on a Cutt.ly team account with optional custom slugs, branded domains, and tracking metadata in a single call.

Install Jentic One Beta

Connect the Cutt.ly Team API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cutt.ly Team 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Team API.

Shorten a long URL into a Cutt.ly short link via GET /index.php

Apply a custom slug to make the short link memorable for campaigns

Route the short link through a branded custom domain attached to the team

GET STARTED

Start building with Cutt.ly Team API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Branded short links for marketing campaigns

Turn a long campaign destination URL into a short, branded link routed through your custom domain. Marketing teams use the Cutt.ly Team API to mass-generate links for paid ads, newsletters, and social posts so click data rolls up to the team workspace and reports can be filtered by campaign tag.

Shorten https://example.com/landing/spring-sale on the team's custom domain with the slug 'spring2026'.

Outbound email link tracking

Generate a unique trackable short URL per recipient or per email batch before send. The single GET endpoint accepts the destination URL plus team API key and returns a Cutt.ly short link, which downstream tooling can stamp into the email body to attribute clicks back to a campaign.

Create one short URL per row in the recipient CSV by calling GET /index.php for each long URL.

Bulk migration to a new short-link domain

Re-shorten an existing list of campaign URLs onto a freshly attached custom domain. The Team API processes one URL per call, so a script iterates the source list, calls the endpoint, and writes the new short link back to the campaign record.

Iterate 500 campaign URLs, call GET /index.php for each, and store the returned short URL keyed by source URL.

AI agent link shortener via Jentic

Give an AI agent a tool to produce short, trackable links inside its workflow. The agent searches Jentic for 'shorten a URL', loads the schema, and executes the call without holding the API key. This avoids stuffing the team key into prompt context.

Through Jentic, call GET /index.php with the destination URL and return the short URL plus tracking slug.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for cutt.

METHOD

PATH

DESCRIPTION

GET

/index.php

Shorten a URL on the authenticated team account

GET

/index.php

Shorten a URL on the authenticated team account

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Cutt.ly Team API key is stored encrypted in the Jentic vault. Agents receive a scoped execution token - the raw key never appears in prompt or log output.

Intent-based discovery

Agents search by intent (e.g. 'shorten a URL') and Jentic returns the Cutt.ly Team operation with its parameter schema, so the call is one step from intent to execution.

Time to first call

Direct Cutt.ly integration: a couple of hours for HTTP plumbing and key management. Through Jentic: under 10 minutes - search, load, execute.

FAQs

Specific to using Cutt.ly Team API through Jentic.

Why is there no official OpenAPI spec for Cutt.ly Team 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 Team via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cutt.ly Team API use?

An API key passed in the X-API-Key header. Through Jentic, the key is stored in the encrypted vault and injected at execution time so it never enters the agent's prompt or log output.

Can I shorten a URL with a custom slug on Cutt.ly Team?

Yes. GET /index.php accepts a custom name parameter alongside the destination URL, and Cutt.ly returns the short link on the team's account, optionally routed through a branded domain attached to the team.

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

Rate limits depend on your Cutt.ly Team plan rather than being declared in the spec. Handle 429 responses with backoff and check the Cutt.ly dashboard for your tier's per-minute quota before running bulk shortening jobs.

Can I use a custom branded domain with this API?

Yes - if the team has a branded domain attached in the Cutt.ly dashboard, the shortening call can route the new short link through that domain rather than cutt.ly.

How do I shorten a URL through Jentic?

Run pip install jentic, search for 'shorten a URL', load the GET /index.php schema, and execute with the destination URL. Jentic returns the short URL without exposing your team API key to the agent.