Remote API
✓ Official Vendor SpecDeveloper ToolsSource Controlbasic, bearer, oauth2206 EndpointsREST
For Agents
Programmatically token, get token identity. Covers 206 operations with basic, bearer, oauth2 authentication.
Use for: I need to token, I want to token identity, Search for magic links generator, Find all the sso configuration
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
remote.com/main version 1.0.0. The API exposes 206 endpoints secured with basic, bearer, oauth2 authentication.
Install Jentic One Beta
Connect the Remote API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Remote 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Remote API.
Token
Get token identity
Magic links generator
Create the SSO Configuration
Show the current SSO Configuration
List Benefit Offers By Employment
Use Cases
Patterns agents use Remote API for, with concrete tasks.
★ Developer Tools Operations
Use the Remote API to perform developer tools operations programmatically. The API provides 206 endpoints covering core functionality including token, get token identity, magic links generator.
Call POST /auth/oauth2/token to token
Automated Auth Management
Automate auth operations by combining multiple Remote API endpoints. Agents can get token identity and then magic links generator in a single workflow.
Call GET /v1/identity/current to get token identity, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Remote 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, bearer, oauth2 tokens manually.
Search Jentic for 'token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
206 endpoints — remote.
METHOD
PATH
DESCRIPTION
POST
/auth/oauth2/token
Token
GET
/v1/identity/current
Get token identity
POST
/v1/magic-link
Magic links generator
POST
/v1/sso-configuration
Create the SSO Configuration
GET
/v1/sso-configuration
Show the current SSO Configuration
GET
/v1/sso-configuration/details
Show the SSO Configuration Details
GET
/v1/benefit-offers
List Benefit Offers By Employment
GET
/v1/benefit-offers/country-summaries
List Benefit Offers
POST
/auth/oauth2/token
Token
GET
/v1/identity/current
Get token identity
POST
/v1/magic-link
Magic links generator
POST
/v1/sso-configuration
Create the SSO Configuration
GET
/v1/sso-configuration
Show the current SSO Configuration
GET
/v1/sso-configuration/details
Show the SSO Configuration Details
GET
/v1/benefit-offers
List Benefit Offers By Employment
GET
/v1/benefit-offers/country-summaries
List Benefit Offers
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Remote API basic, bearer, oauth2 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., 'token') and Jentic returns the matching Remote API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Remote API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
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 Remote API through Jentic.
What authentication does the Remote API use?
The Remote API uses basic, bearer, oauth2 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 token with the Remote API?
Yes. Use the POST /auth/oauth2/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Remote 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 token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'token'. Jentic returns the matching Remote API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Remote API have?
The Remote API exposes 206 endpoints covering auth, benefit offers, benefit renewal requests operations.
GET STARTED