Install Jentic One Beta

Connect the Litport API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Litport 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%2Flitport.net%2Flitport" | sh

Step 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%2Flitport.net%2Flitport" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Litport API.

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

GET STARTED

Start building with Litport API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Litport API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

19 endpoints — the litport api retrieves public free proxies and manages a proxy account, including tokens, packages, and pay-per-gb usage.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Litport API through Jentic.

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.

Litport API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingbearer19 EndpointsREST

For Agents

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

Use for: List the public free proxies available right now, Get a fresh free-proxy snapshot, Read the usage for one of my proxy tokens, Change the location of a movable token

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

72%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Litport API to your agent

Capabilities

Start building with Litport API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Litport API

Jentic AI Readiness Score

Litport API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness