Tebex Plugin API

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.