Install Jentic One Beta

Connect the Tebex Plugin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tebex Plugin 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%2Ftebex.io%2Ftebex-plugin-api" | 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%2Ftebex.io%2Ftebex-plugin-api" | 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 Tebex Plugin API.

Get server information

Delete commands

Integrate Tebex Plugin API into automated workflows

Query and filter Tebex Plugin API records by parameters

Monitor Tebex Plugin API operational status and events

GET STARTED

Start building with Tebex Plugin API

Explore with Jentic One

View OpenAPI Document

Automated Information Management

Automate information operations by combining multiple Tebex Plugin API endpoints. Agents can get due players and then delete commands in a single workflow.

Call GET /queue to get due players, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tebex Plugin 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 apiKey tokens manually.

Search Jentic for 'get server information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

33 endpoints — the tebex plugin api enables game server plugins to interact with a tebex webstore.

METHOD

PATH

DESCRIPTION

GET

/information

Get server information

GET

/queue

Get due players

DELETE

/queue

Delete commands

GET

/queue/offline-commands

Get offline commands

GET

/queue/online-commands/{playerId}

Get online commands for a player

GET

/listing

Get listing (deprecated)

GET

/packages

Get all packages (deprecated)

GET

/package/{packageId}

Get a package (deprecated)

GET

/information

Get server information

GET

/queue

Get due players

DELETE

/queue

Delete commands

GET

/queue/offline-commands

Get offline commands

GET

/queue/online-commands/{playerId}

Get online commands for a player

GET

/listing

Get listing (deprecated)

GET

/packages

Get all packages (deprecated)

GET

/package/{packageId}

Get a package (deprecated)

Why Jentic?

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

Setup

Wiring the Tebex Plugin API by hand means setting up its secret key header, pointing calls at plugin.tebex.io, and writing the command-queue polling and retry glue yourself. Through Jentic you install once, import the Tebex Plugin API from the API Directory, store the secret key once, and your agent calls it.

Permission scoping

The Tebex Plugin API puts the package id in the URL path (/package/{packageId}) and the player id in the queue path (/queue/online-commands/{playerId}), so a rule can pin your agent to one package or player. You choose the operations it may call, so state-changing ones like deleting from the queue are not included unless you add them.

Credential isolation

Your Tebex secret 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 'list packages' or 'read the command queue', and Jentic returns the matching Tebex Plugin API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tebex Plugin API through Jentic.

What authentication does the Tebex Plugin API use?

The Tebex Plugin API uses an API key passed in the `X-Tebex-Secret` 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 get server information with the Tebex Plugin API?

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

What are the rate limits for the Tebex Plugin 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 server information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get server information'. Jentic returns the matching Tebex Plugin API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Tebex Plugin API have?

The Tebex Plugin API exposes 33 endpoints covering information, command queue, packages operations.

Can I limit what my agent is allowed to do with the Tebex Plugin API?

Yes. Because Jentic One is self-hosted, your own rules decide which Tebex Plugin API operations and credentials the agent may use, so you can grant read calls like GET /information and GET /queue while withholding state-changing ones such as DELETE /queue. Since the package id sits in the path (/package/{packageId}) and the player id sits in the queue path (/queue/online-commands/{playerId}), you can pin the agent to a single package or player. Your Tebex secret key is stored encrypted by your own instance and injected only when an allowed operation runs.

Tebex Plugin API

Name: Tebex Plugin API
Brand: Tebex Plugin API
Availability: InStock

Browse all Tebex APIs

PaymentsPayment ProcessingapiKey33 EndpointsREST

For Agents

Programmatically get server information, get due players. Covers 33 operations with apiKey authentication.

Use for: I need to server information, I want to due players, Search for commands, Find all offline commands

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

The Tebex Plugin API enables game server plugins to interact with a Tebex webstore. It provides endpoints for managing command queues, payments, packages, checkout, gift cards, coupons, bans, sales, community goals, and player data. This API is used to implement command execution on game servers for. The API exposes 33 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Tebex Plugin API to your agent

Capabilities

Start building with Tebex Plugin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tebex Plugin API