Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the T2M 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%2Ft2mio.com%2Ft2m-url-shortener-api" | 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%2Ft2mio.com%2Ft2m-url-shortener-api" | 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 T2M URL Shortener API.
Create URL
List URLs
Get URL
Update URL
Delete URL
Patterns agents use T2M URL Shortener API for, with concrete tasks.
GET STARTED
★ Analytics Operations
Use the T2M URL Shortener API to perform analytics operations programmatically. The API provides 16 endpoints covering core functionality including create url, list urls, get url.
Call POST /urls to create url
Automated stats Management
Automate stats operations by combining multiple T2M URL Shortener API endpoints. Agents can list urls and then get url in a single workflow.
Call GET /urls to list urls, then verify the result
AI Agent Integration via Jentic
AI agents discover and call T2M URL Shortener API 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 url', load the operation schema, and execute with Jentic-managed credentials
16 endpoints — api for managing shortened urls, tags, and analytics with the t2m url shortener service.
METHOD
PATH
DESCRIPTION
/urls
Create URL
/urls
List URLs
/urls/{id}
Get URL
/urls/{id}
Update URL
/urls/{id}
Delete URL
/tags
Create tag
/tags
List tags
/tags/{id}
Get tag
/urls
Create URL
/urls
List URLs
/urls/{id}
Get URL
/urls/{id}
Update URL
/urls/{id}
Delete URL
/tags
Create tag
/tags
List tags
/tags/{id}
Get tag
What agents get from Jentic-routed access to this vendor.
Setup
Wiring T2M URL Shortener by hand means sending two header credentials (X-API-Key and X-API-Secret) on every call and building your own CRUD handling for links and tags. Through Jentic you install once, import T2M URL Shortener from the API Directory, store the key and secret once, and your agent calls it.
Permission scoping
T2M puts the link id in the URL path (/urls/{id}), so a rule can pin your agent to one short link: it can read or update that link and nothing else. You choose the operations it may call, so destructive ones like deleting a URL or a tag are not included unless you add them.
Credential isolation
Your T2M API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a short URL' or 'list tags', and Jentic returns the matching T2M 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 T2M URL Shortener API through Jentic.
What authentication does the T2M URL Shortener API use?
The T2M URL Shortener API 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 url with the T2M URL Shortener API?
Yes. Use the POST /urls endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the T2M URL Shortener API?
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 url through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create url'. Jentic returns the matching T2M URL Shortener API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the T2M URL Shortener API have?
The T2M URL Shortener API exposes 16 endpoints covering stats, tags, urls operations.
Can I limit what my agent is allowed to do with the T2M URL Shortener API?
Yes. Because you run Jentic One yourself, your own rules decide which T2M operations and credentials the agent may use. Since T2M puts the link id in the path (/urls/{id}), you can pin the agent to a single short link so it only reads or updates that one and touches nothing else. You choose the operations it can call, so destructive ones like deleting a URL or a tag stay off the list until you explicitly add them.
For Agents
Programmatically create url, list urls. Covers 16 operations with apiKey authentication.
Use for: I need to url, I want to urls, Search for url, Find all url
Not supported: Does not handle payments, communications, or crm - use for analytics only.
API for managing shortened URLs, tags, and analytics with the T2M URL shortener service. The API exposes 16 endpoints secured with apiKey authentication.