Install Jentic One Beta

Connect the Shorten.REST API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shorten.REST API Documentation, 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%2Fshorten.rest%2Fshorten-rest" | 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%2Fshorten.rest%2Fshorten-rest" | 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 Shorten.REST API Documentation API.

Create alias

Get alias

Update alias

Delete alias

Monitor Shorten.REST API Documentation operational status and events

GET STARTED

Start building with Shorten.REST API Documentation API

Explore with Jentic One

View OpenAPI Document

Automated Alias Management

Automate alias operations by combining multiple Shorten.REST API Documentation endpoints. Agents can get alias and then update alias in a single workflow.

Call GET /aliases to get alias, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Shorten.REST API Documentation endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'create alias', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — introduction the shorten.

METHOD

PATH

DESCRIPTION

POST

/aliases

Create alias

GET

/aliases

Get alias

PUT

/aliases

Update alias

DELETE

/aliases

Delete alias

GET

/aliases/all

Get aliases by domain

GET

/clicks

Get clicks

POST

/clicks/pg

Get clicks statistics

POST

/aliases

Create alias

GET

/aliases

Get alias

PUT

/aliases

Update alias

DELETE

/aliases

Delete alias

GET

/aliases/all

Get aliases by domain

GET

/clicks

Get clicks

POST

/clicks/pg

Get clicks statistics

Why Jentic?

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

Setup

Wiring the Shorten.REST API by hand means sending your API key on every request against api.shorten.rest and parsing its alias and click responses yourself. Through Jentic you install once, import the Shorten.REST API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Shorten.REST works on the /aliases collection with the target in the request body rather than as an owned path resource, so you limit the agent to the operations it needs, such as creating or listing aliases, and destructive ones like alias deletion stay out unless you add them.

Credential isolation

Your Shorten.REST 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 alias' or 'list click data', and Jentic returns the matching Shorten.REST operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Shorten.REST API Documentation API through Jentic.

What authentication does the Shorten.REST API Documentation use?

The Shorten.REST API Documentation uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create alias with the Shorten.REST API Documentation?

Yes. Use the POST /aliases endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Shorten.REST API Documentation?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create alias through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create alias'. Jentic returns the matching Shorten.REST API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Shorten.REST API Documentation have?

The Shorten.REST API Documentation exposes 7 endpoints covering alias, click operations.

Can I limit what my agent is allowed to do with the Shorten.REST API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Shorten.REST operations and credentials your agent may use. Shorten.REST acts on the /aliases collection with the target passed in the request body rather than as an owned path, so you can grant only the operations the agent needs, such as creating aliases, listing aliases by domain, or reading click statistics. Destructive operations like deleting an alias stay off unless you explicitly add them.

Shorten.REST API Documentation

Name: Shorten.REST API Documentation API
Brand: Shorten.REST API Documentation
Availability: InStock

Maps GeolocationGeocodingapiKey7 EndpointsREST

For Agents

Programmatically create alias, get alias. Covers 7 operations with apiKey authentication.

Use for: I need to alias, I want to alias, Search for alias, Find all alias

Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.

Introduction The Shorten.rest API allows you to programmatically create short URLs (an 'alias') for longer URL (a 'destination'). Each alias you create can be used to redirect the end user (person clicking on the link) to one or more destination URLs A default destination is always set and specific destinations can be set to redirect the end user to preferred destinations based. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Shorten.REST API Documentation to your agent

Capabilities

Start building with Shorten.REST API Documentation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Shorten.REST API Documentation