Tabbyml Tabby Server

Name: Tabby Server API
Brand: Tabby Server
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbearer4 EndpointsREST

For Agents

Programmatically chat_completions, completion. Covers 4 operations with bearer authentication.

I need to chat_completions, I want to completion, Search for event, Find all health

Install Jentic One Beta

Connect the Tabby Server to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tabby Server, 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%2Ftabbyml.com%2Ftabbyml" | 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%2Ftabbyml.com%2Ftabbyml" | 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 Tabby Server API.

chat_completions

completion

event

health

GET STARTED

Start building with Tabby Server API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Tabby Server API for, with concrete tasks.

★ E-Commerce Operations

Use the Tabby Server to perform e commerce operations programmatically. The API provides 4 endpoints covering core functionality including chat_completions, completion, event.

Call POST /v1/chat/completions to chat_completions

Automated Chat Management

Automate chat operations by combining multiple Tabby Server endpoints. Agents can completion and then event in a single workflow.

Call POST /v1/completions to completion, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tabby Server 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 bearer tokens manually.

Search Jentic for 'chat_completions', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — [![tabby stars](https://img.

METHOD

PATH

DESCRIPTION

POST

/v1/chat/completions

chat_completions

POST

/v1/completions

completion

POST

/v1/events

event

GET

/v1/health

health

POST

/v1/chat/completions

chat_completions

POST

/v1/completions

completion

POST

/v1/events

event

GET

/v1/health

health

Why Jentic?

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

Setup

Wiring Tabby Server by hand means learning its bearer token auth, pointing at the right host, and shaping completion and event requests yourself. Through Jentic you install once, import Tabby Server from the API Directory, store the token once, and your agent calls it.

Permission scoping

Tabby's completion and event calls carry their target in the request body, so limit the agent to the operations it needs, such as chat completions or health checks, rather than to any one resource. Every operation the agent can run is one you chose to allow.

Credential isolation

Your Tabby Server token 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 'complete a chat prompt' or 'check server health', and Jentic returns the matching Tabby Server operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Tabby Server API through Jentic.

What authentication does the Tabby Server use?

The Tabby Server uses a Bearer token in the Authorization 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 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.