Install Jentic One Beta

Connect the Tidio API to your agent

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

Create a new contact

Retrieve all contacts

Update multiple contacts

Remove a contact

Monitor Tidio API operational status and events

Use Cases

GET STARTED

Start building with Tidio API

Explore with Jentic One

View OpenAPI Document

Automated Contact Properties Management

Automate contact properties operations by combining multiple Tidio API endpoints. Agents can retrieve all contacts and then create multiple contacts in a single workflow.

Call GET /contacts to retrieve all contacts, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'create a new contact', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

19 endpoints — tidio api provides programmatic access to manage contacts, conversations, tickets, operators, departments, and project settings for the tidio live chat platform.

METHOD

PATH

DESCRIPTION

POST

/contacts

Create a new contact

GET

/contacts

Retrieve all contacts

POST

/contacts/batch

Create multiple contacts

PATCH

/contacts/batch

Update multiple contacts

GET

/contacts/{contactId}

Retrieve a single contact

PATCH

/contacts/{contactId}

Update contact properties

DELETE

/contacts/{contactId}

Remove a contact

GET

/contacts/{contactId}/viewed-pages

Access page history for a contact

POST

/contacts

Create a new contact

GET

/contacts

Retrieve all contacts

POST

/contacts/batch

Create multiple contacts

PATCH

/contacts/batch

Update multiple contacts

GET

/contacts/{contactId}

Retrieve a single contact

PATCH

/contacts/{contactId}

Update contact properties

DELETE

/contacts/{contactId}

Remove a contact

GET

/contacts/{contactId}/viewed-pages

Access page history for a contact

Why Jentic?

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

Setup

Wiring the Tidio API by hand means setting up its two key headers, the client id and client secret, and building the contact create, batch, and lookup calls yourself. Through Jentic you install once, import the Tidio API from the API Directory, store those keys once, and your agent calls it.

Permission scoping

Tidio puts the contact id in the URL path (/contacts/{contactId}), so a rule can pin your agent to one contact: it can read that contact and its viewed pages and nothing else. You choose the operations it may call, so destructive ones like updating or deleting a contact are not included unless you add them.

Credential isolation

Your Tidio client id and client secret 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 'create a new contact' or 'get a contact's viewed pages', and Jentic returns the matching Tidio API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tidio API through Jentic.

What authentication does the Tidio API use?

The Tidio API uses an API key passed in the `X-Tidio-Openapi-Client-Id` 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 create a new contact with the Tidio API?

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

What are the rate limits for the Tidio 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 create a new contact through Jentic?

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

How many endpoints does the Tidio API have?

The Tidio API exposes 19 endpoints covering contact properties, contacts, departments operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Tidio operations and credentials the agent may use. Because the contact id lives in the URL path (/contacts/{contactId}), you can pin the agent to a single contact and let it only read that contact and its viewed pages. You pick the operations it may call, so write actions like updating or deleting a contact stay out of reach unless you explicitly grant them.

Tidio API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey19 EndpointsREST

For Agents

Programmatically create a new contact, retrieve all contacts. Covers 19 operations with apiKey authentication.

Use for: I need to a new contact, I want to all contacts, Search for multiple contacts, Find all multiple contacts

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

Tidio API provides programmatic access to manage contacts, conversations, tickets, operators, departments, and project settings for the Tidio live chat platform. The API exposes 19 endpoints secured with apiKey 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

98%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: D+Signals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

59%

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: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tidio API to your agent

Capabilities

Use Cases

Start building with Tidio API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tidio API

Jentic AI Readiness Score

Tidio 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