LocalXpose API

Name: LocalXpose API
Brand: LocalXpose API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer14 EndpointsREST

For Agents

Create and manage local tunnels and reserved domains, start and stop tunnels, and inspect inbound requests against the LocalXpose API.

Install Jentic One Beta

Connect the LocalXpose API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LocalXpose 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 LocalXpose API.

Create a new tunnel pointing at a local address and start it remotely

List, inspect, update, and delete existing tunnels

Reserve and manage custom domains attached to tunnels

Inspect inbound HTTP requests routed through a specific tunnel

GET STARTED

Start building with LocalXpose API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use LocalXpose API for, with concrete tasks.

★ On-Demand Webhook Receiver in Development

Developers building third-party webhook handlers need a public URL pointing at their local server. LocalXpose's API creates a tunnel, starts it, and returns a public URL that the third party can call. When the developer is done, the tunnel is stopped or deleted. The whole flow can be wrapped in a CLI or IDE extension.

Call POST /tunnels with the local address, then POST /tunnels/{id}/start, return the public URL to the developer, and call POST /tunnels/{id}/stop when the session ends.

Demo Environment with Reserved Domain

Sales engineers running customer demos want a stable public URL across sessions. LocalXpose's domain endpoints reserve a domain that can be attached to a tunnel each time the demo runs. The tunnel is started before the demo and stopped after, but the URL stays the same.

Call POST /domains to reserve a domain, then POST /tunnels referencing that domain and POST /tunnels/{id}/start before the demo.

Inbound Request Inspection for Debugging

When a webhook is failing, developers need to inspect what the third party actually sent. LocalXpose exposes GET /tunnels/{id}/requests, returning recent inbound requests for the tunnel. Combined with stopping and restarting the tunnel programmatically, this gives an effective debugging loop without UI clicks.

Call GET /tunnels/{id}/requests for the failing tunnel and surface the most recent inbound request body and headers to the developer.

AI Agent Local Sharing Helper

An AI agent helping a developer share a local prototype with a teammate can use Jentic to call LocalXpose, create a tunnel, start it, and post the public URL back into chat. The bearer token stays in the Jentic vault.

Use Jentic to call POST /tunnels then POST /tunnels/{id}/start and reply with the resulting public URL when the user types 'share my local app at port 3000'.

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for localxpose api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/tunnels

Create a tunnel

POST

/tunnels/{id}/start

Start a tunnel

POST

/tunnels/{id}/stop

Stop a tunnel

GET

/tunnels/{id}/requests

Inspect inbound requests on a tunnel

POST

/domains

Reserve a custom domain

POST

/user/access-token

Generate an access token

POST

/tunnels

Create a tunnel

POST

/tunnels/{id}/start

Start a tunnel

POST

/tunnels/{id}/stop

Stop a tunnel

GET

/tunnels/{id}/requests

Inspect inbound requests on a tunnel

POST

/domains

Reserve a custom domain

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LocalXpose bearer tokens are stored encrypted in the Jentic vault. The Authorization header is injected at execution time, so the raw token never enters agent context, logs, or LLM traces.

Intent-based discovery

Agents search Jentic for intents like 'expose my local server' and Jentic returns the matching LocalXpose operations (create tunnel, start tunnel) with their input schemas, so the agent can chain them without browsing localxpose.io documentation.

Time to first call

Direct LocalXpose integration: half a day for token setup, tunnel lifecycle handling, and domain reservation logic. Through Jentic: under 30 minutes to search, load, and execute.

FAQs

Specific to using LocalXpose API through Jentic.

Why is there no official OpenAPI spec for LocalXpose API?

LocalXpose does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LocalXpose API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LocalXpose API use?

LocalXpose uses bearer-token authentication. Send the token as Authorization: Bearer {token}. Through Jentic, the bearer token is stored encrypted and injected at execution time, so the raw token never enters agent context.

Can I attach a stable custom domain to a tunnel?

Yes. Reserve a domain via POST /domains and reference it when creating the tunnel via POST /tunnels. The reserved domain remains attached across stop/start cycles, giving a stable public URL.

What are the rate limits for the LocalXpose API?

Rate limits are not declared in the spec. LocalXpose applies plan-level limits to concurrent tunnels, bandwidth, and reserved domains; the API itself is rate-limited at a level that comfortably supports normal automation.

How do I expose my local server to the internet through Jentic?

Search Jentic for 'create a tunnel to my local server'. Jentic returns the POST /tunnels operation. Load the schema, supply the local address and protocol, then call POST /tunnels/{id}/start with the returned tunnel ID. The response includes the public URL.

How do I see recent inbound requests on a tunnel?

Call GET /tunnels/{id}/requests with the tunnel ID. The response contains the most recent inbound HTTP requests routed through the tunnel, useful for debugging webhook integrations.

LocalXpose API

Connect the LocalXpose API to your agent

Capabilities

Start building with LocalXpose API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs