Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TrailBase 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%2Ftrailbase.io%2Ftrailbase" | shStep 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%2Ftrailbase.io%2Ftrailbase" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with TrailBase API.
Login with email and password
Logout (POST)
Register a new user
Refresh authentication token
Monitor TrailBase API operational status and events
GET STARTED
Patterns agents use TrailBase API for, with concrete tasks.
★ Identity and Authentication Operations
Use the TrailBase API to perform identity auth operations programmatically. The API provides 36 endpoints covering core functionality including login with email and password, login with mfa totp code, login with one-time password.
Call POST /api/auth/v1/login to login with email and password
Automated Auth Management
Automate auth operations by combining multiple TrailBase API endpoints. Agents can login with mfa totp code and then login with one-time password in a single workflow.
Call POST /api/auth/v1/login/mfa to login with mfa totp code, then verify the result
AI Agent Integration via Jentic
AI agents discover and call TrailBase 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 bearer tokens manually.
Search Jentic for 'login with email and password', load the operation schema, and execute with Jentic-managed credentials
36 endpoints — trailbase is a fast, single-executable firebase alternative.
METHOD
PATH
DESCRIPTION
/api/auth/v1/login
Login with email and password
/api/auth/v1/login/mfa
Login with MFA TOTP code
/api/auth/v1/login/otp
Login with one-time password
/api/auth/v1/logout
Logout (POST)
/api/auth/v1/logout
Logout (GET)
/api/auth/v1/register
Register a new user
/api/auth/v1/refresh
Refresh authentication token
/api/auth/v1/status
Get current auth status
/api/auth/v1/login
Login with email and password
/api/auth/v1/login/mfa
Login with MFA TOTP code
/api/auth/v1/login/otp
Login with one-time password
/api/auth/v1/logout
Logout (POST)
/api/auth/v1/logout
Logout (GET)
/api/auth/v1/register
Register a new user
/api/auth/v1/refresh
Refresh authentication token
/api/auth/v1/status
Get current auth status
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the TrailBase API by hand means handling its JWT bearer auth and pointing at your own self-hosted host, since the server URL is a host you supply. Through Jentic you install once, import the TrailBase API from the API Directory, store the token once, and your agent calls it.
Permission scoping
TrailBase auth targets travel in the request body rather than the URL path, so scope the agent to the operations it needs, such as checking login status or refreshing a token, and leave out operations like logout or register unless the workflow requires them. Every operation you allow is one you have chosen.
Credential isolation
Your TrailBase 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 'log in with email and password' or 'check auth status', and Jentic returns the matching TrailBase API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using TrailBase API through Jentic.
What authentication does the TrailBase API use?
The TrailBase API 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 login with email and password with the TrailBase API?
Yes. Use the POST /api/auth/v1/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the TrailBase 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 login with email and password through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login with email and password'. Jentic returns the matching TrailBase API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the TrailBase API have?
The TrailBase API exposes 36 endpoints covering auth, oauth, records operations.
Can I limit what my agent is allowed to do with the TrailBase API?
Yes. Because you run Jentic One yourself, your own rules decide which TrailBase operations the agent can call and which stored credentials it may use. You can allow read-only actions such as checking auth status with GET /api/auth/v1/status or refreshing a token with POST /api/auth/v1/refresh, while leaving out operations like logout or register unless a workflow needs them. Every operation the agent can reach is one you have explicitly chosen to allow.
For Agents
Programmatically login with email and password, login with mfa totp code. Covers 36 operations with bearer authentication.
Use for: I need to login with email and password, I want to login with mfa totp code, Search for login with one-time password, Find all logout (post)
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
TrailBase is a fast, single-executable Firebase alternative. Provides type-safe REST and realtime APIs for database records, authentication, OAuth, and file management, built on Rust/SQLite. The API exposes 36 endpoints secured with bearer authentication.