canonical: https://jentic.com/apis/ritc.io/ritc # Ritc Ritc provides programmatic access to developer tools functionality. The API exposes 66 endpoints secured with apiKey authentication. ## For AI agents Programmatically addaction, listactions. Covers 66 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - addAction - listActions - getAction - updateAction - removeAction - admin - logInRitc ## Use cases ### Developer Tools Operations Use the Ritc to perform developer tools operations programmatically. The API provides 66 endpoints covering core functionality including addaction, listactions, getaction. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'addaction', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/actions` | addAction | | GET | `/actions` | listActions | | GET | `/actions/{action_id}` | getAction | | PATCH | `/actions/{action_id}` | updateAction | | DELETE | `/actions/{action_id}` | removeAction | | GET | `/admin` | admin | | POST | `/admin/log` | logInRitc | | GET | `/admin/ping` | pingRitc | ## Key resources - **Actions** — Operations related to Actions - **Apps** — Operations related to Apps - **Channels** — Operations related to Channels - **Orgs** — Operations related to Orgs - **Rules** — Operations related to Rules ## AI readiness 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. - **Score:** 60 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 68 / 100 - AI-Readiness & Agent Experience: 38 / 100 - Agent Usability: 92 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/ritc.io/ritc/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### 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.