canonical: https://jentic.com/apis/pxl.to/pxl

# Pxl To Pxl API

URL shortener and analytics API. Create, manage, and track short links with detailed analytics. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a short link, list all short links. Covers 6 operations with bearer authentication.

## Scope

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

## Capabilities

- Create a short link
- List all short links
- Get a short link
- Update a short link
- Delete a short link

## Use cases

### Analytics Operations

Use the Pxl API to perform analytics operations programmatically. The API provides 6 endpoints covering core functionality including create a short link, list all short links, get a short link.

Example prompt: Call POST /short to create a short link

### Automated Analytics Management

Automate analytics operations by combining multiple Pxl API endpoints. Agents can list all short links and then get a short link in a single workflow.

Example prompt: Call GET /short to list all short links, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pxl 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 bearer tokens manually.

Example prompt: Search Jentic for 'create a short link', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/short` | Create a short link |
| GET | `/short` | List all short links |
| GET | `/short/{id}` | Get a short link |
| PUT | `/short/{id}` | Update a short link |
| DELETE | `/short/{id}` | Delete a short link |
| GET | `/insight` | Get analytics data |

## Key resources

- **Analytics** — Operations related to Analytics
- **Short Links** — Operations related to Short Links

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/pxl.to/pxl/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 Pxl API by hand means setting up its bearer auth and handling short-link create, update, and insight calls yourself. Through Jentic you install once, import the Pxl API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pxl puts the short-link id in the URL path (`/short/{id}`), so a rule can pin your agent to one link: it can read or update that link and nothing else. You choose the operations it may call, so link deletion is not included unless you add it.
- **Credential handling:** Your Pxl token 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a short link' or 'get link insights', and Jentic returns the matching Pxl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Pxl API use?

The Pxl API uses a Bearer token in the Authorization 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 a short link with the Pxl API?

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

### What are the rate limits for the Pxl 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 a short link through Jentic?

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

### How many endpoints does the Pxl API have?

The Pxl API exposes 6 endpoints covering analytics, short links operations.

### Can I limit what my agent is allowed to do with the Pxl API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Pxl operations and credentials the agent may use. Because Pxl puts the short-link id in the URL path (`/short/{id}`), you can pin the agent to a single link, letting it read (GET `/short/{id}`) or update (PUT `/short/{id}`) that one link and nothing else. You choose which operations are exposed, so link deletion (DELETE `/short/{id}`) and analytics reads (GET /insight) stay off unless you add them.