canonical: https://jentic.com/apis/po.st/po-st

# Po St Shortener Links API

This is a simple API. The API exposes 3 endpoints.

## For AI agents

Programmatically get_expand, adds an inventory item. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- get_expand
- adds an inventory item
- searches inventory

## Use cases

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

Example prompt: Call GET /expand to get_expand

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

Example prompt: 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.

Example prompt: Search Jentic for 'get_expand', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/expand` | get_expand |
| POST | `/inventory` | adds an inventory item |
| GET | `/inventory` | searches inventory |

## Key resources

- **admins** — Secured Admin-only calls
- **developers** — Operations available to regular developers
- **admin operations** — Operations related to admin operations
- **expand** — Operations related to expand
- **public operations** — Operations related to public operations

## AI readiness

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.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 38 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/po.st/po-st/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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