Can I chat_completions with the Tabby Server?

Yes. Use the POST /v1/chat/completions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Tabby Server?

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 chat_completions through Jentic?

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

How many endpoints does the Tabby Server have?

The Tabby Server exposes 4 endpoints covering chat, completions, events operations.

Can I limit what my agent is allowed to do with the Tabby Server API?

Yes. Because you run Jentic One yourself, your own rules decide which Tabby Server operations the agent may call, so you can allow only chat completions and health checks while withholding completions or event writes. Tabby's completion and event requests carry their target in the request body rather than in a single resource path, so you scope access by operation rather than by resource. Every operation the agent can run is one you chose to allow, and the stored bearer token is injected at execution time without ever entering the agent's context.