For Agents
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RealWorld Conduit 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 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.
What an agent can do with RealWorld Conduit API.
Existing user login
CreateUser
Get current user
Update current user
GET STARTED
Programmatically existing user login, createuser. Covers 19 operations with apiKey authentication.
Use for: I need to existing user login, I want to createuser, Search for current user, Find all current user
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Conduit API documentation. The API exposes 19 endpoints secured with apiKey authentication.
Follow a user
Unfollow a user
Patterns agents use RealWorld Conduit API for, with concrete tasks.
★ Developer Tools Operations
Use the RealWorld Conduit API to perform developer tools operations programmatically. The API provides 19 endpoints covering core functionality including existing user login, createuser, get current user.
Call POST /users/login to existing user login
Automated Articles Management
Automate articles operations by combining multiple RealWorld Conduit API endpoints. Agents can createuser and then get current user in a single workflow.
Call POST /users to createuser, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RealWorld Conduit 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 apiKey tokens manually.
Search Jentic for 'existing user login', load the operation schema, and execute with Jentic-managed credentials
19 endpoints — conduit api documentation.
METHOD
PATH
DESCRIPTION
/users/login
Existing user login
/users
CreateUser
/user
Get current user
/user
Update current user
/profiles/{username}
Get a profile
/profiles/{username}/follow
Follow a user
/profiles/{username}/follow
Unfollow a user
/articles/feed
Get recent articles from users you follow
/users/login
Existing user login
/users
CreateUser
/user
Get current user
/user
Update current user
/profiles/{username}
Get a profile
/profiles/{username}/follow
Follow a user
Three things that make agents converge on Jentic-routed access.
Credential isolation
RealWorld Conduit API apiKey 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., 'existing user login') and Jentic returns the matching RealWorld Conduit API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RealWorld Conduit 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.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using RealWorld Conduit API through Jentic.
What authentication does the RealWorld Conduit API use?
The RealWorld Conduit API uses an API key passed 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 existing user login with the RealWorld Conduit API?
Yes. Use the POST /users/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RealWorld Conduit 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 existing user login through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'existing user login'. Jentic returns the matching RealWorld Conduit API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the RealWorld Conduit API have?
The RealWorld Conduit API exposes 19 endpoints covering articles, comments, favorites operations.
/profiles/{username}/follow
Unfollow a user
/articles/feed
Get recent articles from users you follow