Install Jentic One Beta

Connect the InterMIND API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the InterMIND 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%2Fintermind.com%2Fintermind" | 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%2Fintermind.com%2Fintermind" | 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 InterMIND API.

Create an ad-hoc InterMIND meeting link or schedule one at a starts_at time with invitees

Read the latest finalized transcript of a meeting as Markdown grouped by speaker

Search recap summaries for a phrase and list the newest recaps of hosted meetings

Find the best-matching passages across recaps, transcripts, chats, and shared files with a date range

GET STARTED

Start building with InterMIND API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use InterMIND API for, with concrete tasks.

★ AI meeting assistant that reads recaps and follows up

A developer's agent connected through Jentic searches by intent, loads the InterMIND recap and channel operations with their input schemas, and calls them with the bearer token injected at execution time. After a call ends, the agent reads the recap, pulls action items from the transcript, and posts a summary into the team channel, all as the key's user and without the token entering the agent's context.

Call GET /recaps with limit 1 to find the newest recap, read GET /meetings/{id}/transcript for that meeting, then POST /channels/{id}/messages with a three-bullet summary in the text field

Scheduling meetings from a chat or calendar request

When a user asks to set up a call, a tool can create an InterMIND meeting link immediately or place it at a chosen time. The create call accepts a title, starts_at, duration_min, time_zone, and an invitees list, so one request returns a joinable link that lands in the user's calendar.

POST /meetings with title 'Q3 planning', starts_at set to next Tuesday 15:00, duration_min 45, time_zone 'Europe/Dublin', and two invitee emails, then return the meeting link

Searching what was decided across meetings

Teams lose decisions in long call histories. The InterMIND knowledge search returns the best-matching passages from recaps, transcripts, chats, and shared files, filterable by meeting_id and a from/to date range, while recap search finds summaries containing an exact phrase. A tool can answer 'when did we agree on the launch date' with the passage and its meeting.

Call GET /knowledge/search with q 'launch date' and from set to the first of last month, then return the top three passages with their meetings

Recap-ready notifications into another tool

A CRM or notes tool can react the moment a meeting recap is ready instead of polling. The webhook subscription takes a target_url and an event, the list call shows active subscriptions, and a subscription is removed by id when the integration is disconnected.

POST /webhooks with target_url 'https://example.org/hooks/recap' and event recap.ready, then confirm the subscription appears in GET /webhooks

Key Endpoints

16 endpoints — the intermind api schedules meetings on behalf of a user and returns the recaps and speaker-labelled transcripts intermind produces after each call, across a meeting space that understands 20+ languages.

METHOD

PATH

DESCRIPTION

POST

/meetings

Create or schedule a meeting link

GET

/meetings

List the user's meetings

GET

/meetings/{id}/transcript

Get a meeting's Markdown transcript

GET

/recaps

List newest meeting recaps

GET

/knowledge/search

Search recaps, transcripts, chats, and files

POST

/channels/{id}/messages

Post a channel message

POST

/webhooks

Subscribe a webhook to an event

POST

/meetings

Create or schedule a meeting link

GET

/meetings

List the user's meetings

GET

/meetings/{id}/transcript

Get a meeting's Markdown transcript

GET

/recaps

List newest meeting recaps

GET

/knowledge/search

Search recaps, transcripts, chats, and files

POST

/channels/{id}/messages

Post a channel message

POST

/webhooks

Subscribe a webhook to an event

Why Jentic?

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

Setup

Wiring InterMIND by hand means minting an imk_ bearer key, knowing that older keys return 403 on most routes, and stitching recaps, transcripts, and channels together yourself. Through Jentic you install once, import InterMIND from the API Directory, store the key once, and your agent calls it.

Permission scoping

InterMIND puts the channel id in the URL path (/channels/{id}/messages), so a rule can pin your agent to one channel's chat. You choose the operations it may call, so actions like posting messages or deleting a webhook subscription are not included unless you add them.

Credential isolation

Your InterMIND 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.

Intent-based discovery

Agents search Jentic by intent such as 'get a meeting transcript' or 'search meeting recaps', and Jentic returns the matching InterMIND operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using InterMIND API through Jentic.

What authentication does the InterMIND API use?

Per its OpenAPI spec, the InterMIND API authenticates every request with a bearer token in the Authorization header: either a personal API key created under InterMIND Settings, API keys (prefixed imk_), or a token minted by an OAuth connection. Keys created before v1.1 open only /me, POST /meetings, /recaps, and /webhooks, so other endpoints answer 403 until a new key is created. Through Jentic the token is stored by your own instance and attached at call time.

Can I get a meeting transcript with the InterMIND API?

Yes. GET /meetings/{id}/transcript returns the latest finalized transcript of a meeting as Markdown grouped by speaker. You can pass a session to pick a specific session and max_chars to cap the length, which keeps long calls inside an agent's working budget.

What are the rate limits for the InterMIND API?

The OpenAPI spec does not specify rate limits. Check the InterMIND documentation at https://intermind.com for current limits before running bulk transcript or recap reads.

Is there an InterMIND MCP server?

You don't need an MCP server to give your agent InterMIND. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the meeting, recap, and channel operations it needs, discovered on demand rather than loaded into its context up front.

Can I limit what my agent is allowed to do with InterMIND?

Yes. For example, write a rule that allows GET /recaps, GET /meetings/{id}/transcript, and POST /channels/{id}/messages for a single channel id, so the agent can read recaps and post summaries to that one channel and nothing else, and every call it makes is logged.

How do I post a meeting summary to a channel through Jentic?

Import InterMIND from the Jentic API Directory and store your API key once. Your agent then searches for 'post a message in a channel', gets POST /channels/{id}/messages with its schema, and sends the summary in the text field. To run it on your own infrastructure, install Jentic One from its GitHub repo.

InterMIND API

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVideo Conferencingbearer16 EndpointsREST

For Agents

Create InterMIND meeting links, read meeting recaps and Markdown transcripts, search an account's meeting knowledge, and post in channels as the key's user.

Use for: I need to schedule a meeting for tomorrow at 10am with two invitees, Get the transcript of yesterday's product sync, Search my meeting recaps for the phrase pricing change, Find what was said about the launch date across meetings, chats, and files

Not supported: Does not handle calendar sync for other providers, live call audio streaming, or meeting recording downloads. Use for InterMIND meetings, recaps, transcripts, and channel messages only.

The InterMIND API schedules meetings on behalf of a user and returns the recaps and speaker-labelled transcripts InterMIND produces after each call, across a meeting space that understands 20+ languages. It lists the user's meetings, searches recap summaries for a phrase, and runs a passage search across recaps, transcripts, channel chats, and shared files. It also reads and posts messages in the user's channels, returns the extracted text of documents shared in meetings, and lets a tool subscribe a webhook that fires when a recap is ready.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 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).

75%

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: DSignals: 4

31%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

56%

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

60%

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

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the InterMIND API to your agent

Capabilities

Start building with InterMIND API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

InterMIND API

Jentic AI Readiness Score

InterMIND 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