Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shortener Links 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%2Fpo.st%2Fpo-st" | 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%2Fpo.st%2Fpo-st" | 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 Shortener Links API.
get_expand
adds an inventory item
searches inventory
Patterns agents use Shortener Links API for, with concrete tasks.
★ Developer Tools Operations
Use the Shortener Links API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including get_expand, adds an inventory item, searches inventory.
Call GET /expand to get_expand
GET STARTED
Automated admins Management
Automate admins operations by combining multiple Shortener Links API endpoints. Agents can adds an inventory item and then searches inventory in a single workflow.
Call POST /inventory to adds an inventory item, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Shortener Links 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 none tokens manually.
Search Jentic for 'get_expand', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — this is a simple api.
METHOD
PATH
DESCRIPTION
/expand
get_expand
/inventory
adds an inventory item
/inventory
searches inventory
/expand
get_expand
/inventory
adds an inventory item
/inventory
searches inventory
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Shortener Links API by hand still means coding against its po.st/api endpoints and handling expand and inventory calls yourself even though it needs no auth. Through Jentic you install once, import the Shortener Links API from the API Directory, and your agent calls it with no credential to manage.
Permission scoping
The Shortener Links API takes its link and inventory arguments in the request rather than pinning a resource in the URL path, so scope the agent to the operations it needs, such as expanding a short link or reading inventory. You choose that set, so the inventory write is included only if you add the POST /inventory operation.
Credential isolation
This API needs no credential, so there is nothing for the agent to hold; if you later add a secret, your own Jentic One instance stores it encrypted and injects it at execution time. Nothing sensitive enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'expand a shortened link' or 'read link inventory', and Jentic returns the matching Shortener Links 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 Shortener Links API through Jentic.
What authentication does the Shortener Links API use?
The Shortener Links API uses no authentication. 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 get_expand with the Shortener Links API?
Yes. Use the GET /expand endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Shortener Links 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 get_expand through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get_expand'. Jentic returns the matching Shortener Links API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Shortener Links API have?
The Shortener Links API exposes 3 endpoints covering admins, developers, admin operations operations.
Can I limit what my agent is allowed to do with the Shortener Links API?
Yes. Because Jentic One is self-hosted, you decide which of the Shortener Links API operations your agent may call, so you can grant read-only access such as GET /expand to expand a short link and GET /inventory to read inventory. The POST /inventory write is included only if you add that operation to the agent's allowed set. Since the API takes its link and inventory values in the request rather than pinning a resource in the URL, this operation-level allowlist is where you control what the agent can do.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically get_expand, adds an inventory item. Covers 3 operations.
Use for: I need to get_expand, I want to adds an inventory item, Search for searches inventory, I need to access Shortener Links API programmatically
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is a simple API. The API exposes 3 endpoints.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>