Install Jentic One Beta

Connect the Max Bot API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Max Bot 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%2Fplatform-api.max.ru%2Fmax-bot" | 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%2Fplatform-api.max.ru%2Fmax-bot" | 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 Max Bot API.

Send, edit, and delete messages in chats

Send chat actions such as typing indicators

Add and remove chat members and administrators

Pin and unpin messages in a chat

Subscribe to bot updates or poll the updates endpoint

GET STARTED

Start building with Max Bot API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Max Bot API for, with concrete tasks.

★ AI Chatbot Agent

An AI agent connected to the Max Bot API through Jentic can hold a conversation in a chat by reading incoming updates, sending replies, and responding to the buttons a user taps. It can send a typing action while it works, so the chat feels responsive to users.

Poll the updates endpoint for a new message, then send a reply to the originating chat

Automated Chat Responses

Send transactional and notification messages to chats and let users act through inline buttons. The Max Bot API sends messages, edits them in place, and answers the callbacks that buttons trigger.

Send a message with an inline button and answer the callback when the user taps it

Chat Administration

Keep a chat organized by managing its members and administrators and pinning the messages that matter. The Max Bot API adds and removes members, grants and revokes admin rights, and pins or unpins messages.

Add a new administrator to a chat and pin the welcome message

Key Endpoints

30 endpoints — the max bot api connects bots to the max messenger, sending, editing, and deleting messages in chats.

METHOD

PATH

DESCRIPTION

GET

/chats

List the chats the bot belongs to

POST

/messages

Send a message

POST

/chats/{chatId}/actions

Send a chat action such as typing

PUT

/chats/{chatId}/pin

Pin a message in a chat

POST

/chats/{chatId}/members/admins

Add a chat administrator

GET

/updates

Get incoming updates

GET

/chats

List the chats the bot belongs to

POST

/messages

Send a message

POST

/chats/{chatId}/actions

Send a chat action such as typing

PUT

/chats/{chatId}/pin

Pin a message in a chat

POST

/chats/{chatId}/members/admins

Add a chat administrator

GET

/updates

Get incoming updates

Why Jentic?

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

Setup

Wiring the Max Bot API by hand means passing your access token on every request and learning its chat, message, and members endpoints yourself. Through Jentic you install once, import Max Bot from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Max Bot API puts the chat id in the URL path, so a rule can pin your agent to one chat: it can send messages and actions there and nothing else. You choose the operations, so member removal or chat deletion is not included unless you add it.

Credential isolation

Your Max access 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 'send a message' or 'pin a message', and Jentic returns the matching Max Bot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Max Bot API through Jentic.

Is there a Max Bot MCP server?

You don't need an MCP server to give your agent the Max Bot API. Jentic connects it directly from the API Directory: import it, store your access token once, and your agent can send messages and manage chats. Operations are discovered on demand, so your agent's context stays lean.

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

Yes. The Max Bot API puts the chat id in the URL path, so a rule can pin your agent to one chat and allow only sending messages and actions there. It cannot remove members or delete the chat unless you add those operations, and every call is logged.

What authentication does the Max Bot API use?

The Max Bot API authenticates with an access token passed as the access_token query parameter per its OpenAPI spec; you receive the token from MasterBot when you create a bot. With Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I pin a message with the Max Bot API?

Yes. The pin endpoint sets the pinned message for a chat, and a matching endpoint removes it. An agent can also read the current pinned message before replacing it.

What are the rate limits for the Max Bot API?

The OpenAPI spec does not specify rate limits. Check the Max platform documentation at https://platform-api.max.ru for current limits before sending high-volume messages.

How do I send a chat message with the Max Bot API through Jentic?

Import the Max Bot API from the Jentic API Directory, store your access token once, and have your agent search by intent such as 'send a message'. Jentic returns the send operation with its input schema, and your agent passes the chat and text. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Platform Api Max Ru Max Bot API

AI ReadinessFoundational (D)45/100

See full scorecard

Community OpenAPI document · agent-readyCommunicationsChat MessagingapiKey30 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send, edit, and delete messages in Max messenger chats, manage members and administrators, pin messages, upload files, and respond to button callbacks. Receive events via subscriptions or the updates endpoint.

Use for: Send a message to a chat, Pin an important message in a chat, Add an administrator to a chat, Get the list of chats the bot is in

Not supported: Does not handle voice calls, SMS, or email. Use for Max messenger bot chat and messaging only.

The Max Bot API connects bots to the Max messenger, sending, editing, and deleting messages in chats. It manages chat members and administrators, pins and unpins messages, uploads files, and responds to inline button callbacks. Bots receive incoming events through subscriptions or by polling the updates endpoint.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

86%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: DSignals: 4

Example Density

How richly the API is illustrated with examples.

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

71%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

93%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

64%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Max Bot API to your agent

Capabilities

Start building with Max Bot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Platform Api Max Ru Max Bot API

Jentic AI Readiness Score

Max Bot API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness