For Agents
Programmatically login with email and password, login with mfa totp code. Covers 36 operations with bearer authentication.
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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API.
Login with email and password
Logout (POST)
Register a new user
Refresh authentication token
Monitor TrailBase API operational status and events
GET STARTED
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.
Patterns agents use TrailBase API 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)
Three things that make agents converge on Jentic-routed access.
Credential isolation
TrailBase API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'login with email and password') and Jentic returns the matching TrailBase API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct TrailBase API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Auth0
Alternative identity auth API
Choose Auth0 when you need a different approach to identity auth operations
Okta
Alternative identity auth API
Choose Okta when you need a different approach to identity auth operations
Specific to using TrailBase API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/api/auth/v1/register
Register a new user
/api/auth/v1/refresh
Refresh authentication token
/api/auth/v1/status
Get current auth status