AtlasRTX Mobile API
Browse all Swaggerhub Atlasrtx APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlbasic15 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically logs in a user, updates a user. Covers 15 operations with basic authentication.
Use for: I need to logs in a user, I want to updates a user, Search for gets data for the home screen, Find all notifications for a user
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is the AtlasRTX Mobile App API. The API exposes 15 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the AtlasRTX Mobile API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AtlasRTX Mobile 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.
1
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%2Fswaggerhub.atlasrtx%2Fatlasrtx-mobile-api" | sh2
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%2Fswaggerhub.atlasrtx%2Fatlasrtx-mobile-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Mobile API.
logs in a user
updates a user
gets data for the home screen
get notifications for a user
create a new engagement
Use Cases
Patterns agents use AtlasRTX Mobile API for, with concrete tasks.
★ Developer Tools Operations
Use the AtlasRTX Mobile API to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including logs in a user, updates a user, gets data for the home screen.
Call POST /login to logs in a user
Automated m Management
Automate m operations by combining multiple AtlasRTX Mobile API endpoints. Agents can updates a user and then gets data for the home screen in a single workflow.
Call POST /updateUser to updates a user, then verify the result
AI Agent Integration via Jentic
AI agents discover and call AtlasRTX Mobile 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 'logs in a user', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
15 endpoints — this is the atlasrtx mobile app api.
METHOD
PATH
DESCRIPTION
POST
/login
logs in a user
POST
/updateUser
updates a user
GET
/getHomeScreenData
gets data for the home screen
POST
/getNotifications
get notifications for a user
POST
/getEngagements
get engagements for a user
POST
/getEngagementMessages
get messages for an engagement
POST
/newEngagement
create a new engagement
POST
/markEngagementHandled
Mark the messages of an engagement as "Handled"
POST
/login
logs in a user
POST
/updateUser
updates a user
GET
/getHomeScreenData
gets data for the home screen
POST
/getNotifications
get notifications for a user
POST
/getEngagements
get engagements for a user
POST
/getEngagementMessages
get messages for an engagement
POST
/newEngagement
create a new engagement
POST
/markEngagementHandled
Mark the messages of an engagement as "Handled"
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
This AtlasRTX Mobile API uses HTTP basic authentication against a test host, so hand-wiring it means encoding the basic credentials, threading them through each POST call, and handling retries yourself. Through Jentic you install once, import the AtlasRTX Mobile API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
This API selects engagements and users through values in the request body rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as reading home-screen data or listing engagement messages, and leave writes like updating a user out unless you add them.
Credential isolation
Your AtlasRTX Mobile API basic 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 'get home screen data' or 'list engagement messages', and Jentic returns the matching AtlasRTX Mobile API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using AtlasRTX Mobile API through Jentic.
What authentication does the AtlasRTX Mobile API use?
The AtlasRTX Mobile 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 logs in a user with the AtlasRTX Mobile API?
Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the AtlasRTX Mobile 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 logs in a user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'logs in a user'. Jentic returns the matching AtlasRTX Mobile API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the AtlasRTX Mobile API have?
The AtlasRTX Mobile API exposes 15 endpoints covering m operations.
Can I limit what my agent is allowed to do with the AtlasRTX Mobile API?
Yes. Because you run Jentic One yourself, your own rules decide which AtlasRTX Mobile API operations and credentials the agent may use. This API selects engagements and users through values in the request body rather than a resource id in the path, so you scope by operation: grant only the calls the agent needs, such as reading GET /getHomeScreenData or listing POST /getEngagementMessages, and leave writes like POST /updateUser, POST /newEngagement, or POST /markEngagementHandled out unless you deliberately add them. The stored basic credentials are injected only for the operations you allow, so the agent cannot reach anything you have not granted.
GET STARTED