Install Jentic One Beta

Connect the LTPM API to your agent

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

Create a single sign-on game_link for a user by uuid, company, language, and product_id

Pass callback_url and webhook_url with each SSO request so the partner is notified about the session

Read a user's play data for a product, including sessions, session_resume_requests, and play_status

Reset a user's progress on a product so they can start the game again

GET STARTED

Start building with LTPM API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LTPM API for, with concrete tasks.

★ Agent-managed game invitations through Jentic

A partner platform's agent can invite users into a Mindgame product and follow up on their progress. Through Jentic it calls the SSO operation with the user's uuid, company, language, and product_id to get a game_link, sends that link to the user, and later reads play_status from the data operation. Your Mindgame basic-auth credentials stay on your own Jentic One instance.

POST /sso with uuid 'XXXXX-XXXXX-XXXXX-XXXXX', company 'CompanyX', language 'en', product_id 1, callback_url 'https://example.com/done', webhook_url 'https://example.com/hook', then send the returned game_link to the user

Tracking completion and usage

Partners reporting on usage can read a user's play data per product. The data operation requires uuid, company, and product_id as query parameters and returns sessions, session_resume_requests, and a play_status such as not_played, so a dashboard or reminder flow can see who has not started yet.

GET /data with uuid 'XXXXX-XXXXX-XXXXX-XXXXX', company 'CompanyX', product_id 1 and send a reminder if play_status is 'not_played'

Retakes and support requests

When a user's session breaks or a retake is approved, the reset operation clears that uuid's progress for one product and company. Because the reset is a GET call, it is worth keeping out of any automated flow that only needs to read data.

GET /reset with uuid 'XXXXX-XXXXX-XXXXX-XXXXX', company 'CompanyX', product_id 2 after a support agent approves the retake

Key Endpoints

4 endpoints — the ltpm api is mindgame's partner integration for ltp to give users access to mindgame's game products and retrieve their usage data.

METHOD

PATH

DESCRIPTION

POST

/sso

Process SSO request and return game link

GET

/data

Return play data for a uuid

GET

/reset

Reset progress for a uuid

POST

/register-360

POST

/sso

Process SSO request and return game link

GET

/data

Return play data for a uuid

GET

/reset

Reset progress for a uuid

POST

/register-360

Why Jentic?

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

Setup

Wiring the LTPM API by hand means sending basic-auth credentials, building SSO payloads with six required fields, and passing uuid, company, and product_id on every read. Through Jentic you install once, import the LTPM API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The LTPM API carries the user's uuid in the request body or query string, not the URL path, so rules bound which operations your agent may call, not which user. Limit the agent to the operations it needs, such as SSO and play data, so the reset operation is not included unless you add it.

Credential isolation

Your LTPM basic-auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Mindgame game link' or 'check a user's play status', and Jentic returns the matching LTPM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LTPM API through Jentic.

What authentication does the LTPM API use?

Per its OpenAPI spec, the LTPM API uses HTTP basic authentication (basicAuth) on each of its four operations, sending a username and password in the Authorization header. Through Jentic those credentials are stored encrypted by your own Jentic One instance and injected when the agent calls.

What does the SSO operation return?

POST /sso returns a status, a message, and a data object with a game_link that carries a JWT, so the user can open the game without a separate login. All six body fields are required: uuid, company, language, product_id, callback_url, and webhook_url. The spec bounds product_id from 1 to 7.

How do I check a user's play status through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the LTPM API from the directory, and store your basic-auth credentials. Your agent searches 'get Mindgame play data for a user', gets GET /data with its schema, and sends uuid, company, and product_id. 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 LTPM API?

Yes. For example, allow only POST /sso and GET /data, so the agent can send game links and check progress but cannot call GET /reset and wipe a user's results. Every call it makes is logged.

Is there a Mindgame MCP server?

You don't need an MCP server to give your agent the LTPM API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it.

What are the rate limits for the LTPM API?

The OpenAPI spec does not specify rate limits. Check with Mindgame at https://mindgame.eu for current limits.

Mindgame LTPM API

AI ReadinessNon-Ready (F)31/100

See full scorecard

Community OpenAPI document · agent-readyEducationAssessmentbasic4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Generate single sign-on game links for Mindgame products, read a user's play data and status, and reset or register users through Mindgame's LTPM partner API.

Use for: Generate a Mindgame game link for user XXXXX-XXXXX in English, Check whether this user has played product 3 yet, Get the session data for a user and company, Reset a user's progress so they can retake the game

Not supported: Does not create games, manage candidate pipelines, or score results beyond the play data it returns. Use for Mindgame SSO links, play data, resets, and 360 registration only.

The LTPM API is Mindgame's partner integration for LTP to give users access to Mindgame's game products and retrieve their usage data. A single sign-on call takes a user's uuid, the company, a language, a product_id, and callback and webhook URLs, and returns a game_link carrying a JWT that drops the user straight into the game. Partners can then read the play data for that uuid and product, including sessions, session_resume_requests, and play_status, reset a user's progress, or register a uuid with custom content for the 360 product.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

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

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

53%

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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

10%

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

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LTPM API to your agent

Capabilities

Start building with LTPM API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mindgame LTPM API

Jentic AI Readiness Score

LTPM 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