Install Jentic One Beta

Connect the Relatel API to your agent

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

List chat conversations

Get chat by UUID

Create contact

Query and filter Relatel API records by parameters

Monitor Relatel API operational status and events

GET STARTED

Start building with Relatel API

Explore with Jentic One

View OpenAPI Document

Automated Calls Management

Automate calls operations by combining multiple Relatel API endpoints. Agents can get chat by uuid and then list recent orders in a single workflow.

Call GET /chats/{uuid} to get chat by uuid, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Relatel 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 'list chat conversations', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

43 endpoints — relatel telephony platform api for managing chats, contacts, employees, receptions, voicemails, calls, messages, and statistics.

METHOD

PATH

DESCRIPTION

GET

/chats

List chat conversations

GET

/chats/{uuid}

Get chat by UUID

GET

/orders

List recent orders

GET

/orders/{id}

Get order details

POST

/contacts

Create contact

GET

/contacts

List contacts

GET

/contacts/{id}

Get contact

PUT

/contacts/{id}

Update contact

GET

/chats

List chat conversations

GET

/chats/{uuid}

Get chat by UUID

GET

/orders

List recent orders

GET

/orders/{id}

Get order details

POST

/contacts

Create contact

GET

/contacts

List contacts

GET

/contacts/{id}

Get contact

PUT

/contacts/{id}

Update contact

Why Jentic?

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

Setup

Wiring Relatel by hand means handling its bearer token auth against app.relatel.dk and mapping its chats, orders, and contacts endpoints yourself. Through Jentic you install once, import Relatel from the API Directory, store the token once, and your agent calls it.

Permission scoping

Relatel puts the contact id in the URL path (/contacts/{id}), so a rule can pin your agent to reading and updating one contact. You choose the operations it may call, so creating contacts is not included unless you add it.

Credential isolation

Your Relatel 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 chat conversations' or 'look up a contact', and Jentic returns the matching Relatel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Relatel API through Jentic.

What authentication does the Relatel API use?

The Relatel 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 list chat conversations with the Relatel API?

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

What are the rate limits for the Relatel 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 list chat conversations through Jentic?

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

How many endpoints does the Relatel API have?

The Relatel API exposes 43 endpoints covering calls, chats, contacts operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Relatel operations and credentials the agent may use. Because Relatel puts the contact id in the URL path (/contacts/{id}), you can pin the agent to reading and updating a single contact while excluding broader calls like GET /chats or listing all contacts. Creating contacts with POST /contacts stays off unless you explicitly add that operation to the agent's allowed set.

Relatel Dk Relatel API

Name: Relatel API
Brand: Relatel API
Availability: InStock

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVoice Telephonybearer43 EndpointsREST

For Agents

Programmatically list chat conversations, get chat by uuid. Covers 43 operations with bearer authentication.

Use for: I need to chat conversations, I want to chat by uuid, Search for recent orders, Find all order details

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

Relatel telephony platform API for managing chats, contacts, employees, receptions, voicemails, calls, messages, and statistics. The API exposes 43 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

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).

14%

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

51%

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.

60%

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 Relatel API to your agent

Capabilities

Start building with Relatel API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Relatel Dk Relatel API

Jentic AI Readiness Score

Relatel 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