Install Jentic One Beta

Connect the Revolt API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Revolt 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%2Frevolt.chat%2Frevolt-chat" | sh

Step 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%2Frevolt.chat%2Frevolt-chat" | 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 Revolt API.

Get current user

Edit current user

Close/delete channel

Send message

Monitor Revolt API operational status and events

Use Cases

GET STARTED

Start building with Revolt API

Explore with Jentic One

View OpenAPI Document

Automated Users Management

Automate users operations by combining multiple Revolt API endpoints. Agents can edit current user and then get user in a single workflow.

Call PATCH /users/@me to edit current user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Revolt 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 'get current user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — api for revolt, an open source discord alternative.

METHOD

PATH

DESCRIPTION

GET

/users/@me

Get current user

PATCH

/users/@me

Edit current user

GET

/users/{userId}

Get user

GET

/channels/{channelId}

Get channel

PATCH

/channels/{channelId}

Edit channel

DELETE

/channels/{channelId}

Close/delete channel

POST

/channels/{channelId}/messages

Send message

GET

/channels/{channelId}/messages

Get messages

GET

/users/@me

Get current user

PATCH

/users/@me

Edit current user

GET

/users/{userId}

Get user

GET

/channels/{channelId}

Get channel

PATCH

/channels/{channelId}

Edit channel

DELETE

/channels/{channelId}

Close/delete channel

POST

/channels/{channelId}/messages

Send message

GET

/channels/{channelId}/messages

Get messages

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Revolt API by hand means handling its x-session-token or x-bot-token header auth, sending the right token on every call to api.revolt.chat, and managing retries yourself. Through Jentic you install once, import the Revolt API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Revolt puts the channel id in the URL path (/channels/{channelId}), so a rule can pin your agent to one channel: it can read and post messages in that channel and nothing else. You choose the operations it may call, so destructive ones like deleting a channel are not included unless you add them.

Credential isolation

Your Revolt 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 'get the current user' or 'send a message to a channel', and Jentic returns the matching Revolt API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Revolt API through Jentic.

What authentication does the Revolt API use?

The Revolt API uses an API key passed in the `x-session-token` 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 get current user with the Revolt API?

Yes. Use the GET /users/@me endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Revolt 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 get current user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching Revolt API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Revolt API have?

The Revolt API exposes 16 endpoints covering users, channels, messages operations.

Can I limit what my agent is allowed to do with the Revolt API?

Yes. Because Jentic One is self-hosted, your own rules decide which Revolt API operations and credentials the agent may use. Since Revolt puts the channel id in the URL path (/channels/{channelId}), you can pin the agent to a single channel so it only reads messages (GET /channels/{channelId}/messages) and posts messages (POST /channels/{channelId}/messages) there. You also choose which operations are exposed, so destructive calls like DELETE /channels/{channelId} are left out unless you deliberately add them.

Revolt Chat Revolt API

Name: Revolt API
Brand: Revolt API
Availability: InStock

Official vendor OpenAPI document · agent-readyCommunicationsSms MessagingapiKey16 EndpointsREST

For Agents

Programmatically get current user, edit current user. Covers 16 operations with apiKey authentication.

Use for: I need to current user, I want to edit current user, Search for user, Find all channel

Not supported: Does not handle payments, crm, or developer tools - use for communications only.

API for Revolt, an open source Discord alternative. Provides access to users, channels, servers, messages, and more. The API exposes 16 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Revolt API to your agent

Capabilities

Use Cases

Start building with Revolt API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Revolt Chat Revolt API