For Agents
Programmatically get an api token using client credentials, search vehicles with filters, sorts, and pagination. Covers 5 operations with bearer authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RTA Fleet Management 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 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.
What an agent can do with RTA Fleet Management API API.
Get an API token using client credentials
Search vehicles with filters, sorts, and pagination
Update a vehicle by ID
Extract raw database records from RTA
GET STARTED
Use for: I need to an api token using client credentials, I want to vehicles with filters, sorts, and pagination, Search for vehicle details by id, Find all a vehicle by id
Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.
REST API for interacting with RTA Fleet Management software, including vehicle search, details, updates, authentication, and data extraction. The API exposes 5 endpoints secured with bearer authentication.
Monitor RTA Fleet Management API operational status and events
Patterns agents use RTA Fleet Management API API for, with concrete tasks.
★ Identity and Authentication Operations
Use the RTA Fleet Management API to perform identity auth operations programmatically. The API provides 5 endpoints covering core functionality including get an api token using client credentials, search vehicles with filters, sorts, and pagination, get vehicle details by id.
Call GET /information-management/{tenantId}/integrations/get-api-token to get an api token using client credentials
Automated Authentication Management
Automate authentication operations by combining multiple RTA Fleet Management API endpoints. Agents can search vehicles with filters, sorts, and pagination and then get vehicle details by id in a single workflow.
Call POST /asset-management/{tenantId}/vehicles/search-vehicles-enhanced to search vehicles with filters, sorts, and pagination, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RTA Fleet Management 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 'get an api token using client credentials', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — rest api for interacting with rta fleet management software, including vehicle search, details, updates, authentication, and data extraction.
METHOD
PATH
DESCRIPTION
/information-management/{tenantId}/integrations/get-api-token
Get an API token using client credentials
/asset-management/{tenantId}/vehicles/search-vehicles-enhanced
Search vehicles with filters, sorts, and pagination
/asset-management/{tenantId}/vehicles/{id}
Get vehicle details by ID
/asset-management/{tenantId}/vehicles/{id}
Update a vehicle by ID
/v0/extract/{tablename}
Extract raw database records from RTA
/information-management/{tenantId}/integrations/get-api-token
Get an API token using client credentials
/asset-management/{tenantId}/vehicles/search-vehicles-enhanced
Search vehicles with filters, sorts, and pagination
/asset-management/{tenantId}/vehicles/{id}
Get vehicle details by ID
/asset-management/{tenantId}/vehicles/{id}
Update a vehicle by ID
/v0/extract/{tablename}
Extract raw database records from RTA
Three things that make agents converge on Jentic-routed access.
Credential isolation
RTA Fleet Management API bearer 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., 'get an api token using client credentials') and Jentic returns the matching RTA Fleet Management API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RTA Fleet Management API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Auth0
Alternative identity auth API
Choose Auth0 when you need a different approach to identity auth operations
Okta
Alternative identity auth API
Choose Okta when you need a different approach to identity auth operations
Specific to using RTA Fleet Management API API through Jentic.
What authentication does the RTA Fleet Management API use?
The RTA Fleet Management API uses a Bearer token in the Authorization header. 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 get an api token using client credentials with the RTA Fleet Management API?
Yes. Use the GET /information-management/{tenantId}/integrations/get-api-token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RTA Fleet Management 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 get an api token using client credentials through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get an api token using client credentials'. Jentic returns the matching RTA Fleet Management API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the RTA Fleet Management API have?
The RTA Fleet Management API exposes 5 endpoints covering authentication, vehicles, data extract operations.