Install Jentic One Beta

Connect the Terminal49 API Reference to your agent

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

List shipments

Get a shipment

Edit a shipment

Stop tracking a shipment

Resume tracking a shipment

GET STARTED

Start building with Terminal49 API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Terminal49 API Reference API for, with concrete tasks.

★ Communications Operations

Use the Terminal49 API Reference to perform communications operations programmatically. The API provides 77 endpoints covering core functionality including list shipments, get a shipment, edit a shipment.

Call GET /shipments to list shipments

Automated Containers Management

Automate containers operations by combining multiple Terminal49 API Reference endpoints. Agents can get a shipment and then edit a shipment in a single workflow.

Call GET /shipments/{id} to get a shipment, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Terminal49 API Reference 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 apiKey tokens manually.

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

Key Endpoints

77 endpoints — the terminal 49 api offers a convenient way to programmatically track your shipments from origin to destination.

METHOD

PATH

DESCRIPTION

GET

/shipments

List shipments

GET

/shipments/{id}

Get a shipment

PATCH

/shipments/{id}

Edit a shipment

PATCH

/shipments/{id}/stop_tracking

Stop tracking a shipment

PATCH

/shipments/{id}/resume_tracking

Resume tracking a shipment

POST

/tracking_requests

Create a tracking request

GET

/tracking_requests

List tracking requests

POST

/tracking_requests/infer_number

Infer Tracking Number

GET

/shipments

List shipments

GET

/shipments/{id}

Get a shipment

PATCH

/shipments/{id}

Edit a shipment

PATCH

/shipments/{id}/stop_tracking

Stop tracking a shipment

PATCH

/shipments/{id}/resume_tracking

Resume tracking a shipment

POST

/tracking_requests

Create a tracking request

GET

/tracking_requests

List tracking requests

POST

/tracking_requests/infer_number

Infer Tracking Number

Why Jentic?

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

Setup

Wiring the Terminal49 API by hand means learning its token-based Authorization header auth against the api.terminal49.com/v2 host and handling shipment and tracking-request calls yourself. Through Jentic you install once, import the Terminal49 API from the API Directory, store the API token once, and your agent calls it.

Permission scoping

Terminal49 puts the shipment id in the URL path (/shipments/{id}), so a rule can pin your agent to one shipment: it can read and update that shipment and nothing else. You choose the operations it may call, so stopping or resuming tracking is not included unless you add it.

Credential isolation

Your Terminal49 API 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 'list shipments' or 'create a tracking request', and Jentic returns the matching Terminal49 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Terminal49 API Reference API through Jentic.

What authentication does the Terminal49 API Reference use?

The Terminal49 API Reference uses an API key passed 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 list shipments with the Terminal49 API Reference?

Yes. Use the GET /shipments endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Terminal49 API Reference?

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 list shipments through Jentic?

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

How many endpoints does the Terminal49 API Reference have?

The Terminal49 API Reference exposes 77 endpoints covering containers, custom field definitions, custom field options operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Terminal49 operations and credentials the agent may use. Because Terminal49 puts the shipment id in the URL path (/shipments/{id}), you can pin the agent to a single shipment and let it only read and edit that one. You also choose the exact operations it may call, so actions like stopping or resuming tracking stay off limits unless you explicitly grant them.

Terminal49 API Reference

Name: Terminal49 API Reference API
Brand: Terminal49 API Reference
Availability: InStock

Community OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey77 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically list shipments, get a shipment. Covers 77 operations with apiKey authentication.

Use for: I need to shipments, I want to a shipment, Search for edit a shipment, Find all stop tracking a shipment

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

The Terminal 49 API offers a convenient way to programmatically track your shipments from origin to destination. Please enter your API key into the "Variables" tab before using these endpoints within Postman. The API exposes 77 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Terminal49 API Reference to your agent

Capabilities

Start building with Terminal49 API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Terminal49 API Reference