Install Jentic One Beta

Connect the mumo REST API to your agent

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

Start a deliberation on a prompt with an explicit panel of 2 to 3 model IDs or a platform-curated panel

Poll a round's progress until moderation_status or execution_status is complete or failed

Read a full session with every round, model response, snippet, and claim map

Steer the next round with KEEP, EXPLORE, CHALLENGE, CORE, or SHIFT snippets quoted from prior responses

GET STARTED

Start building with mumo REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use mumo REST API for, with concrete tasks.

★ AI agent getting a second and third opinion

A coding agent facing an architecture choice can ask several models at once instead of trusting one answer. Through Jentic the agent searches for 'start a multi-model deliberation', loads the mumo create operation with its input schema, and sends the prompt with an optional reference document, with the platform key injected at call time. It then polls the progress route and reads the session's claim map to see where the models agree and where they split.

Call POST /api/deliberation with prompt 'Should we use Postgres or MongoDB for an event store?', poll GET /api/sessions/{id}/progress until the round is terminal, then read GET /api/sessions/{id}

Steering a debate round by round

mumo has no autonomous moderator, so the caller decides what happens next. After reading a round, the moderator appends a new round with a prompt and snippets that quote earlier responses verbatim, tagged to keep an idea, explore it, challenge it, mark it as core, or shift the discussion. The round reuses the session's model panel.

Call POST /api/sessions/{id}/rounds with a prompt and a snippets array tagging one quoted claim as CHALLENGE, then poll progress until terminal

Publishing a decision record

Once a deliberation settles a question, the team can share it. The share route publishes the session at a public reader-deck URL that anyone with the link can view, and calling it again after new rounds refreshes the same URL with the latest snapshot.

Call POST /api/sessions/{id}/share for a completed session and return the public URL

Budget check before a billable run

Every billable model call debits a dollar-denominated wallet, and a write is admitted only when the effective balance covers the round's minimum. A scheduler reads the credit route for effective_balance_usd and the models route for per-model pricing and availability before starting a session.

Call GET /api/credit and stop if effective_balance_usd is zero or below, otherwise call GET /api/models and pick two available models

Key Endpoints

11 endpoints — the mumo rest api runs structured multi-model deliberations: you send a prompt, a panel of two or three language models answers it, and the session returns every model's response alongside a cross-model claim map.

METHOD

PATH

DESCRIPTION

POST

/api/deliberation

Create a deliberation

GET

/api/sessions/{id}/progress

Poll round progress

GET

/api/sessions/{id}

Get a full session

POST

/api/sessions/{id}/rounds

Append a steered round

GET

/api/sessions

List sessions

POST

/api/sessions/{id}/share

Share a session publicly

GET

/api/models

List available models

GET

/api/credit

Get wallet balance

POST

/api/deliberation

Create a deliberation

GET

/api/sessions/{id}/progress

Poll round progress

GET

/api/sessions/{id}

Get a full session

POST

/api/sessions/{id}/rounds

Append a steered round

GET

/api/sessions

List sessions

POST

/api/sessions/{id}/share

Share a session publicly

GET

/api/models

List available models

GET

/api/credit

Get wallet balance

Why Jentic?

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

Setup

Wiring mumo by hand means sending an mmo_live_ key as a bearer token or in X-Mumo-Api-Key, handling 202 acknowledgements, and writing a poll loop on round progress. Through Jentic you install once, import mumo from the API Directory, store the key once, and your agent calls it.

Permission scoping

mumo puts the session id in the URL path, as in /api/sessions/{id}/rounds, so a rule can pin your agent to one session and the operations you pick. You choose the operations it may call, so billable ones like creating a deliberation or appending a round, and public ones like sharing, are not included unless you add them.

Credential isolation

Your mumo platform 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 'ask several models the same question' or 'check if a deliberation round is done', and Jentic returns the matching mumo operation with its input schema, so the agent sends the right prompt, models, and snippets fields.

FAQs

Specific to using mumo REST API through Jentic.

What authentication does the mumo REST API use?

The mumo OpenAPI spec declares two carriers for the same platform key, which begins with mmo_live_. Send it as an HTTP bearer token in Authorization, or bare in the X-Mumo-Api-Key header for proxies that reserve Authorization. GET /api/health needs no credentials, and GET /api/models accepts calls with or without a key. Through Jentic your key is held by your own instance and injected at call time.

How do I know when a mumo round is finished?

Poll GET /api/sessions/{id}/progress. A round is terminal when moderation_status or execution_status is complete or failed, and then GET /api/sessions/{id} returns every response, snippet, and claim map for the session.

What are the rate limits for the mumo REST API?

The OpenAPI spec does not specify a numeric rate limit. Writes are gated by your credit wallet instead: a round is admitted only when the effective balance covers its minimum. See https://mumo.chat for current plan limits.

How do I run a deliberation through Jentic?

Search Jentic for 'start a multi-model deliberation', load POST /api/deliberation, and execute it with your prompt and optionally a models array of 2 to 3 IDs from GET /api/models. Then load the progress operation and poll it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only GET /api/sessions/{id} and GET /api/sessions/{id}/progress for one session id, and the agent can read that deliberation but cannot start new billable rounds or publish anything publicly. Every call it makes is logged.

Can I pick which models answer in mumo?

Yes. Pass a models array of 2 to 3 model IDs when creating a deliberation, using IDs from GET /api/models. Omit it and the platform curates a panel up to your plan's seat cap. The panel is fixed for the session, so later rounds reuse it.

Mumo Chat mumo REST API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer, apiKey11 EndpointsREST

For Agents

Ask a panel of two or three language models the same question through mumo, steer follow-up rounds with tagged snippets, and read each model's answer plus the cross-model claim map.

Use for: Ask three models whether we should use Postgres or MongoDB for an event store, Check whether my mumo round has finished, Get the claim map from my last deliberation, I want to challenge one model's claim in the next round

Not supported: Does not host or fine-tune models, generate images, or run a single-model chat completion. Use for multi-model deliberations and their claim maps only.

The mumo REST API runs structured multi-model deliberations: you send a prompt, a panel of two or three language models answers it, and the session returns every model's response alongside a cross-model claim map. Creating a deliberation or appending a round returns a 202 acknowledgement, and the caller polls a lightweight progress route until the round is terminal before reading the full session. The caller steers each following round with typed snippets quoted from earlier responses, tagged KEEP, EXPLORE, CHALLENGE, CORE, or SHIFT. Supporting routes list sessions, publish a session at a public reader URL, list available models with pricing, report the credit wallet, and return platform defaults.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

17%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

59%

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

68%

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.

50%

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: CSignals: 1

55%

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

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the mumo REST API to your agent

Capabilities

Start building with mumo REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mumo Chat mumo REST API

Jentic AI Readiness Score

mumo REST 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