Install Jentic One Beta

Connect the Terminal API to your agent

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

Public Token Exchange

Create Connection

List All Connections

Get Current Connection

Update Current Connection

GET STARTED

Start building with Terminal API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Terminal API for, with concrete tasks.

★ CRM Operations

Use the Terminal API to perform crm operations programmatically. The API provides 29 endpoints covering core functionality including public token exchange, create connection, list all connections.

Call POST /public-token/exchange to public token exchange

Automated Vehicles Management

Automate vehicles operations by combining multiple Terminal API endpoints. Agents can create connection and then list all connections in a single workflow.

Call POST /connections to create connection, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Terminal 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 'public token exchange', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

29 endpoints — terminal is a unified api that makes it easy to integrate with the leading telematics service providers.

METHOD

PATH

DESCRIPTION

POST

/public-token/exchange

Public Token Exchange

POST

/connections

Create Connection

GET

/connections

List All Connections

GET

/connections/current

Get Current Connection

PATCH

/connections/current

Update Current Connection

POST

/syncs

Request Sync

GET

/syncs

List Sync History

GET

/syncs/{id}

Get Sync Job Status

POST

/public-token/exchange

Public Token Exchange

POST

/connections

Create Connection

GET

/connections

List All Connections

GET

/connections/current

Get Current Connection

PATCH

/connections/current

Update Current Connection

POST

/syncs

Request Sync

GET

/syncs

List Sync History

GET

/syncs/{id}

Get Sync Job Status

Why Jentic?

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

Setup

Wiring the Terminal API by hand means implementing its bearer token auth, running the public-token exchange to open connections, and polling sync status yourself. Through Jentic you install once, import the Terminal API from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

You choose which Terminal API operations your agent may call, so a rule can limit it to the operations it needs, such as starting a sync and reading sync status, while leaving out connection changes like updating the current connection. Every operation the agent runs is one you added to that allowed set.

Credential isolation

Your Terminal API bearer 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 'exchange a public token' or 'check sync status', and Jentic returns the matching Terminal API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Terminal API through Jentic.

What authentication does the Terminal API use?

The Terminal 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 public token exchange with the Terminal API?

Yes. Use the POST /public-token/exchange endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Terminal 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 public token exchange through Jentic?

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

How many endpoints does the Terminal API have?

The Terminal API exposes 29 endpoints covering vehicles, connections, data management operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Terminal API operations and credentials the agent can use. You can allow a read-and-sync agent to call only POST /syncs to start a sync and GET /syncs/{id} to read sync job status, while leaving out connection changes such as PATCH /connections/current. Every operation the agent runs is one you added to that allowed set.

Sandbox Withterminal Terminal API

Name: Terminal API
Brand: Terminal API
Availability: InStock

AI ReadinessFoundational (D+)49/100

See full scorecard

Community OpenAPI document · agent-readyCRMContact Managementbearer29 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically public token exchange, create connection. Covers 29 operations with bearer authentication.

Use for: I need to public token exchange, I want to connection, Search for all connections, Find all current connection

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Terminal is a unified API that makes it easy to integrate with the leading telematics service providers. Contact Support: Name: Terminal Email: connect@withterminal.com. The API exposes 29 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

53%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

48%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Terminal API to your agent

Capabilities

Start building with Terminal API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sandbox Withterminal Terminal API

Jentic AI Readiness Score

Terminal API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness