canonical: https://jentic.com/apis/litport.net/litport

# Litport API

The Litport API retrieves public free proxies and manages a proxy account, including tokens, packages, and pay-per-GB usage. Account operations read a token's usage, saved location, and effective location, set a movable token's region, change a rotating token's interval, and request a new IP in the same location. Package operations manage allowed-IP lists, and pay-per-GB operations list pools, geo targeting, and account balance.

## For AI agents

List public free proxies, read and manage proxy tokens and their locations, manage package allowed-IP lists, and check pay-per-GB balance.

## Scope

Does not create or delete proxy tokens, host content, or scrape target sites. Use for proxy retrieval and account management only.

## Capabilities

- List public free proxies and retrieve a consistent fresh snapshot
- Read a token's usage, saved location, and effective location
- Change a movable token's location or a rotating token's rotation interval
- Manage a package's allowed-IP list, adding or removing individual IPs
- List pay-per-GB pools and geo targeting values and read account balance

## Use cases

### AI Agent Proxy Retrieval

An AI agent connected through Jentic pulls a working proxy for a task by listing the public free proxies and retrieving a consistent fresh snapshot. Because the free-proxy endpoints are open, the agent can get a usable proxy without a credential and only authenticates when it needs account operations.

Example prompt: List the public free proxies and retrieve a fresh snapshot for the agent to use

### Proxy Token Location Management

An agent managing a proxy pool reads a token's effective location and moves a movable token to a new datacenter or ISP region when a task needs different geo coverage. It can also request a new IP in the same location for a static token without recreating anything.

Example prompt: Read a token's effective location and move a movable token to a new region

### Allowed-IP Management for Packages

To authorize a new server, an agent adds its IP to a package's allowed-IP list and reads back the updated list to confirm. Individual IPs can be added or removed, or the whole list set at once.

Example prompt: Add a new server IP to a package's allowed-IP list and read back the updated list

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/free-proxy` | List public free proxies |
| GET | `/api/v1/tokens` | List the caller's tokens |
| GET | `/api/v1/tokens/{tokenId}/usage` | Read usage for one token |
| PUT | `/api/v1/tokens/{tokenId}/location` | Set a movable token's location |
| GET | `/api/v1/packages` | List owned proxy packages |
| PUT | `/api/v1/packages/{packageId}/allowed-ips/{ip}` | Add one IP to a package allow-list |
| GET | `/api/v1/pay-per-gb/balance` | Read account balance and plan |

## Key resources

- **Free Proxy** — List public free proxies and fresh snapshots
- **Tokens** — Read and manage proxy tokens, locations, and rotation
- **Packages** — Read packages and manage allowed-IP lists
- **Pay-per-GB** — List pools and geo targeting and read account balance

## 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:** 60 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 59 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 52 / 100
- **View full report:** https://jentic.com/apis/litport.net/litport/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 Litport API by hand means managing its bearer API key with the `lit_` prefix, separating the open free-proxy endpoints from the authenticated account ones, and handling token location and rotation calls yourself. Through Jentic you install once, import Litport from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Litport puts the token id and package id in the URL path (`/api/v1/tokens/{tokenId}/...`, `/api/v1/packages/{packageId}/...`), so a rule can pin your agent to one token or package. You choose the operations it may call, so changing a token's location or editing a package's allowed IPs is not included unless you add it.
- **Credential handling:** Your Litport API 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.
- **Discovery method:** Agents search Jentic by intent such as 'get a fresh free proxy' or 'read my proxy usage', and Jentic returns the matching Litport operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Bright Data** — Bright Data offers residential and datacenter proxy networks via API.
- **Oxylabs** — Oxylabs provides proxy networks and scraping infrastructure via API.
- **ZenRows** — ZenRows handles the actual page fetch and rendering behind a proxy.

## FAQ

### What authentication does the Litport API use?

The account endpoints authenticate with a bearer API key, a key with a `lit_` prefix created in your Litport settings, as declared in its OpenAPI spec. The free-proxy endpoints are open and need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

### Can I change a proxy token's location with the Litport API?

Yes. For a movable token the location operation sets a datacenter or ISP region and city, you can read the current and effective location, and a rotating token's interval can be changed. No endpoint creates or deletes the tokens themselves.

### What are the rate limits for the Litport API?

The OpenAPI spec does not specify rate limits for the Litport API. See the Litport documentation at https://litport.net/docs for the current limits that apply to your plan.

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

Yes. Write a rule that allows only the read operations such as listing proxies, reading token usage, and checking balance, so the agent can inspect your account but cannot change a token's location or edit allowed-IP lists, and every call it makes is logged.

### How do I get a fresh proxy with the Litport API through Jentic?

Search Jentic for 'get a fresh free proxy', add the Litport API from the directory, and store your API key once for the account endpoints. Your agent lists the free proxies or reads your tokens and packages. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Litport API MCP server?

You don't need an MCP server to give your agent the Litport API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the free-proxy, token, package, and pay-per-GB operations. That keeps extra tool definitions out of the agent's context.