Install Jentic One Beta

Connect the Thirdlane API to your agent

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

Add admin

Delete admin

Integrate Thirdlane API into automated workflows

Query and filter Thirdlane API records by parameters

Monitor Thirdlane API operational status and events

GET STARTED

Start building with Thirdlane API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query Thirdlane API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Thirdlane API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Thirdlane 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 basic tokens manually.

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

Key Endpoints

2 endpoints — thirdlane communications platform rest api for managing admins, agents, ivr, queues, tenants, extensions, schedules, inbound routes, and dids.

METHOD

PATH

DESCRIPTION

POST

/api/admin/{tenant}

Add admin

DELETE

/api/admin/{tenant}/{name}

Delete admin

POST

/api/admin/{tenant}

Add admin

DELETE

/api/admin/{tenant}/{name}

Delete admin

Why Jentic?

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

Setup

Wiring the Thirdlane API by hand means encoding your username and password for basic auth, sending that header on each call, and handling your own retries. Through Jentic you install once, import the Thirdlane API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Thirdlane API puts the tenant in the URL path (/api/admin/{tenant}), so a rule can pin your agent to one tenant: it acts only within that tenant. You choose the operations it may call, so destructive actions like deleting an admin are not included unless you add them.

Credential isolation

Your Thirdlane credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'add an admin to a tenant', and Jentic returns the matching Thirdlane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Thirdlane API through Jentic.

What authentication does the Thirdlane API use?

The Thirdlane API uses HTTP Basic authentication with username and password. 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 add admin with the Thirdlane API?

Yes. Use the POST /api/admin/{tenant} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Thirdlane 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 add admin through Jentic?

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

How many endpoints does the Thirdlane API have?

The Thirdlane API exposes 2 endpoints covering admin operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Thirdlane operations and credentials the agent may use. Since the tenant sits in the URL path (/api/admin/{tenant}), a rule can pin the agent to a single tenant so it acts only within that tenant. You also choose which operations it may call, so you can grant POST /api/admin/{tenant} to add an admin while withholding DELETE /api/admin/{tenant}/{name} unless you explicitly add it.

Thirdlane API

Name: Thirdlane API
Brand: Thirdlane API
Availability: InStock

Official vendor OpenAPI document · agent-readyProductivityCalendar Schedulingbasic2 EndpointsREST

For Agents

Programmatically add admin, delete admin. Covers 2 operations with basic authentication.

Use for: I need to add admin, I want to admin, Get the current status of Thirdlane API resources, List all records from Thirdlane API

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

Thirdlane communications platform REST API for managing admins, agents, IVR, queues, tenants, extensions, schedules, inbound routes, and DIDs. The API exposes 2 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Thirdlane API to your agent

Capabilities

Start building with Thirdlane API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Thirdlane API