Install Jentic One Beta

Connect the TamTam Bot API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TamTam 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%2Ftamtam.chat%2Ftamtam-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%2Ftamtam.chat%2Ftamtam-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 TamTam Bot API.

Get bot info

Edit bot info

Send message

Query and filter TamTam Bot API records by parameters

Monitor TamTam Bot API operational status and events

GET STARTED

Start building with TamTam Bot API

Explore with Jentic One

View OpenAPI Document

Automated Bots Management

Automate bots operations by combining multiple TamTam Bot API endpoints. Agents can edit bot info and then get all chats in a single workflow.

Call PATCH /me to edit bot info, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TamTam Bot 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 bot info', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — bot api to interact with tamtam messenger.

METHOD

PATH

DESCRIPTION

GET

/me

Get bot info

PATCH

/me

Edit bot info

GET

/chats

Get all chats

GET

/chats/{chatId}

Get chat

PATCH

/chats/{chatId}

Edit chat

GET

/chats/{chatId}/members

Get chat members

POST

/messages

Send message

GET

/messages

Get messages

GET

/me

Get bot info

PATCH

/me

Edit bot info

GET

/chats

Get all chats

GET

/chats/{chatId}

Get chat

PATCH

/chats/{chatId}

Edit chat

GET

/chats/{chatId}/members

Get chat members

POST

/messages

Send message

GET

/messages

Get messages

Why Jentic?

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

Setup

Wiring the TamTam Bot API by hand means passing its access_token as a query parameter on every call, tracking the botapi.tamtam.chat host, and building your own retry handling. Through Jentic you install once, import the TamTam Bot API from the API Directory, store the bot access token once, and your agent calls it.

Permission scoping

The TamTam Bot API puts the chat id in the URL path (/chats/{chatId}/...), so a rule can pin your agent to one chat: it can read that chat and its members and nothing else. You choose the operations it may call, so an edit like patching chat settings is not included unless you add it.

Credential isolation

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

FAQs

Specific to using TamTam Bot API through Jentic.

What authentication does the TamTam Bot API use?

The TamTam Bot API uses an API key passed in the `access_token` query. 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 bot info with the TamTam Bot API?

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

What are the rate limits for the TamTam Bot 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 bot info through Jentic?

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

How many endpoints does the TamTam Bot API have?

The TamTam Bot API exposes 16 endpoints covering bots, chats, messages operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which TamTam Bot API operations and credentials the agent may use. Because the chat id sits in the URL path, such as /chats/{chatId} and /chats/{chatId}/members, you can pin the agent to a single chat and let it read only that chat and its members. You choose the operations it may call, so a write like PATCH /chats/{chatId} or POST /messages stays out of reach unless you add it.

Tamtam Chat TamTam Bot API

AI ReadinessFoundational (D)45/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsSms MessagingapiKey16 EndpointsREST

For Agents

Programmatically get bot info, edit bot info. Covers 16 operations with apiKey authentication.

Use for: I need to bot info, I want to edit bot info, Search for all chats, Find all chat

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

Bot API to interact with TamTam messenger. Send and receive messages, manage chats, handle subscriptions and webhooks. The API exposes 16 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

94%

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).

60%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: D-Signals: 4

23%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

88%

OperationId Quality

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

59%

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).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the TamTam Bot API to your agent

Capabilities

Start building with TamTam Bot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tamtam Chat TamTam Bot API

Jentic AI Readiness Score

TamTam 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