Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ritc, 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%2Fritc.io%2Fritc" | 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%2Fritc.io%2Fritc" | 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 Ritc API.
addAction
listActions
getAction
updateAction
removeAction
GET STARTED
admin
logInRitc
Patterns agents use Ritc API for, with concrete tasks.
★ Developer Tools Operations
Use the Ritc to perform developer tools operations programmatically. The API provides 66 endpoints covering core functionality including addaction, listactions, getaction.
Call POST /actions to addaction
Automated Actions Management
Automate actions operations by combining multiple Ritc endpoints. Agents can listactions and then getaction in a single workflow.
Call GET /actions to listactions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Ritc 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 'addaction', load the operation schema, and execute with Jentic-managed credentials
66 endpoints — ritc provides programmatic access to developer tools functionality.
METHOD
PATH
DESCRIPTION
/actions
addAction
/actions
listActions
/actions/{action_id}
getAction
/actions/{action_id}
updateAction
/actions/{action_id}
removeAction
/admin
admin
/admin/log
logInRitc
/admin/ping
pingRitc
/actions
addAction
/actions
listActions
/actions/{action_id}
getAction
/actions/{action_id}
updateAction
/actions/{action_id}
removeAction
/admin
admin
/admin/log
logInRitc
/admin/ping
pingRitc
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Ritc by hand means encoding your API key as HTTP Basic in the Authorization header, remembering the trailing colon so you are not prompted for a password, and threading that header through every actions call yourself. Through Jentic you install once, import Ritc from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Ritc puts the resource id in the URL path (/actions/{action_id}), so a rule can pin your agent to one action: it can read and patch that action and nothing else. You choose the operations it may call, so destructive ones like deleting an action are not included unless you add them.
Credential isolation
Your Ritc API key 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 'create an action' or 'get an action by id', and Jentic returns the matching Ritc 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 Ritc API through Jentic.
What authentication does the Ritc use?
The Ritc uses an API key passed 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 addaction with the Ritc?
Yes. Use the POST /actions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Ritc?
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 addaction through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'addaction'. Jentic returns the matching Ritc operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Ritc have?
The Ritc exposes 66 endpoints covering actions, apps, channels operations.
Can I limit what my agent is allowed to do with the Ritc API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Ritc operations and credentials your agent may use. Since Ritc puts the resource id in the URL path, such as /actions/{action_id}, you can pin the agent to a single action so it only reads (GET /actions/{action_id}) and patches (PATCH /actions/{action_id}) that one action. You also choose which operations it may call, so a destructive one like DELETE /actions/{action_id} is excluded unless you add it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically addaction, listactions. Covers 66 operations with apiKey authentication.
Use for: I need to addaction, I want to listactions, Search for getaction, Find all updateaction
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Ritc provides programmatic access to developer tools functionality. The API exposes 66 endpoints secured with apiKey authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>