Ritc

Name: Ritc API
Brand: Ritc
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey66 EndpointsREST

Install Jentic One Beta

Connect the Ritc to your agent

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

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 instance

Jentic 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 Ritc API.

addAction

listActions

getAction

updateAction

GET STARTED

Start building with Ritc API

Explore with Jentic

View OpenAPI Document

Use Cases

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

Key Endpoints

66 endpoints — ritc provides programmatic access to developer tools functionality.

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

POST

/actions

addAction

GET

/actions

listActions

GET

/actions/{action_id}

getAction

PATCH

/actions/{action_id}

updateAction

DELETE

/actions/{action_id}

removeAction

GET

/admin

admin

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ritc 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., 'addaction') and Jentic returns the matching Ritc operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Ritc 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

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.