AtlasRTX API V1

Name: AtlasRTX API V1 API
Brand: AtlasRTX API V1
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat Messagingnone4 Endpoints

Install Jentic One Beta

Connect the AtlasRTX API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AtlasRTX API V1, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 AtlasRTX API V1 API.

Creates a new engagement with a location auth token

Provides access to the retrieval of engagement conversation data

Integrate AtlasRTX API V1 into automated workflows

Query and filter AtlasRTX API V1 records by parameters

GET STARTED

Start building with AtlasRTX API V1 API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically creates a new engagement with a location auth token, creates a new engagement based on an api auth token. Covers 4 operations.

Use for: I need to creates a new engagement with a location auth token, I want to creates a new engagement based on an api auth token, Search for creates a new engagement by a user, Find all provides access to the retrieval of engagement conversation data

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

Use Cases

Patterns agents use AtlasRTX API V1 API for, with concrete tasks.

★ Communications Operations

Use the AtlasRTX API V1 to perform communications operations programmatically. The API provides 4 endpoints covering core functionality including creates a new engagement with a location auth token, creates a new engagement based on an api auth token, creates a new engagement by a user.

Call POST /engagement to creates a new engagement with a location auth token

Automated engagements Management

Automate engagements operations by combining multiple AtlasRTX API V1 endpoints. Agents can creates a new engagement based on an api auth token and then creates a new engagement by a user in a single workflow.

Call POST /engagementbytoken to creates a new engagement based on an api auth token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call AtlasRTX API V1 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 none tokens manually.

Search Jentic for 'creates a new engagement with a location auth token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — atlasrtx is a chatbot platform for engaging your customers.

METHOD

PATH

DESCRIPTION

POST

/engagement

Creates a new engagement with a location auth token

POST

/engagementbytoken

Creates a new engagement based on an API auth token

POST

/engagementbyuser

Creates a new engagement by a User

POST

/getengagementdata

Provides access to the retrieval of engagement conversation data

POST

/engagement

Creates a new engagement with a location auth token

POST

/engagementbytoken

Creates a new engagement based on an API auth token

POST

/engagementbyuser

Creates a new engagement by a User

POST

/getengagementdata

Provides access to the retrieval of engagement conversation data

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AtlasRTX API V1 none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'creates a new engagement with a location auth token') and Jentic returns the matching AtlasRTX API V1 operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct AtlasRTX API V1 integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using AtlasRTX API V1 API through Jentic.

What authentication does the AtlasRTX API V1 use?

The AtlasRTX API V1 uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I creates a new engagement with a location auth token with the AtlasRTX API V1?

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

What are the rate limits for the AtlasRTX API V1?

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 creates a new engagement with a location auth token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'creates a new engagement with a location auth token'. Jentic returns the matching AtlasRTX API V1 operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the AtlasRTX API V1 have?

The AtlasRTX API V1 exposes 4 endpoints covering engagements operations.

AtlasRTX API V1

Connect the AtlasRTX API V1 to your agent

Capabilities

Start building with AtlasRTX API V1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs