Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Realwork 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frealwork-labs.stoplight.io%2Frealwork-labs-stoplight" | shStep 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%2Frealwork-labs.stoplight.io%2Frealwork-labs-stoplight" | 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 Realwork API.
List Workspaces
Get Workspace
Create Project
Access Realwork API productivity resources via REST API
Patterns agents use Realwork API for, with concrete tasks.
GET STARTED
★ Productivity Operations
Use the Realwork API to perform productivity operations programmatically. The API provides 9 endpoints covering core functionality including list workspaces, get workspace, create project.
Call GET /workspaces to list workspaces
Automated projects Management
Automate projects operations by combining multiple Realwork API endpoints. Agents can get workspace and then create project in a single workflow.
Call GET /workspaces/{id} to get workspace, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Realwork 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 'list workspaces', load the operation schema, and execute with Jentic-managed credentials
9 endpoints — work management and collaboration api (stoplight documentation not accessible).
METHOD
PATH
DESCRIPTION
/workspaces
List Workspaces
/workspaces/{id}
Get Workspace
/projects
Create Project
/projects
List Projects
/projects/{id}
Get Project
/tasks
Create Task
/tasks
List Tasks
/tasks/{id}
Get Task
/workspaces
List Workspaces
/workspaces/{id}
Get Workspace
/projects
Create Project
/projects
List Projects
/projects/{id}
Get Project
/tasks
Create Task
/tasks
List Tasks
/tasks/{id}
Get Task
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Realwork API by hand means setting up its bearer auth, coordinating the workspace, project, and task resources, and handling paging and retries yourself. Through Jentic you install once, import the Realwork API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Realwork API creates projects and tasks through collection endpoints with data in the request body, so you limit the agent to the operations it needs, such as listing workspaces or reading a project. It only calls the operations you allow, so creating a task is out of scope unless you add it.
Credential isolation
Your Realwork API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list workspaces' or 'get a project by id', and Jentic returns the matching Realwork API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Realwork API through Jentic.
What authentication does the Realwork API use?
The Realwork API uses a Bearer token in the Authorization header. 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 list workspaces with the Realwork API?
Yes. Use the GET /workspaces endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Realwork 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 list workspaces through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list workspaces'. Jentic returns the matching Realwork API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Realwork API have?
The Realwork API exposes 9 endpoints covering projects, tasks, workspaces operations.
Can I limit what my agent is allowed to do with the Realwork API?
Yes. Because you run Jentic One yourself, your own rules decide which Realwork API operations and credentials your agent can use. You can restrict it to read-only calls such as listing workspaces, getting a project by ID, or listing tasks, and leave out the collection endpoints that create projects or tasks. The agent can only call the operations you allow, so writing a new task stays out of scope until you grant it.
For Agents
Programmatically list workspaces, get workspace. Covers 9 operations with bearer authentication.
Use for: I need to workspaces, I want to workspace, Search for project, Find all projects
Not supported: Does not handle payments, communications, or crm - use for productivity only.
Work management and collaboration API (Stoplight documentation not accessible). The API exposes 9 endpoints secured with bearer authentication.