Install Jentic One Beta

Connect the MonsiTools Calculation API to your agent

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

Compute a business, finance, marketing, or AI-cost metric by calculator slug with its declared inputs

List every calculator with its name, category, input ids, and formula from /api-tools.json

Catch missing inputs as a missing_inputs error instead of a silent zero

Read API key status, the key hint, and this month's call and error counts with top tools

GET STARTED

Start building with MonsiTools Calculation API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MonsiTools Calculation API for, with concrete tasks.

★ AI analyst agent that runs calculators on demand

An agent answering a business question needs a reliable formula rather than doing arithmetic in its own reasoning. Through Jentic the agent searches for 'run a break-even calculation', loads the MonsiTools calculate operation with its input schema, reads the calculator's input ids from the tool listing, and sends the values. The mt_live_ API key is attached by your own Jentic One instance, so the agent only sees the slug, inputs, and result.

Fetch GET /api-tools.json to read the inputs for break-even-units-calculator, then call POST /api/calculate with slug break-even-units-calculator and those inputs, and return the result

SaaS and marketing metric checks

Growth and finance teams often need the same metrics computed the same way: CAC payback period, LTV to CAC ratio, churn rate, ARR, and ROAS. MonsiTools exposes each as a named calculator slug, so a report or spreadsheet job can send the raw figures and get a consistent number back. Each response echoes the inputs it used alongside the result.

Call POST /api/calculate with slug customer-lifetime-value-to-cac-ratio-calculator and the inputs listed for it in /api-tools.json, then report the ratio

Estimating AI usage costs

Developers budgeting an agent deployment can use calculators such as ai-token-cost-calculator, ai-agent-cost-per-run-calculator, and ai-context-window-calculator to estimate spend before scaling up. Each takes the calculator's declared inputs and returns a single numeric result.

Call POST /api/calculate with slug ai-agent-cost-per-run-calculator and the token and price inputs listed for it in /api-tools.json

Monitoring calculation usage

Premium account holders track how their key is used. GET /api/keys returns whether a key exists, its last four characters, and usage for the month, including calls, errors, top tools, and the last status. It requires a signed-in session token rather than the calculation key.

Call GET /api/keys with a signed-in session token and report this month's calls, errors, and the top three tools by calls

Key Endpoints

5 endpoints — the monsitools calculation api runs any of several hundred named calculators and returns the numeric result as json.

METHOD

PATH

DESCRIPTION

POST

/api/calculate

Run a calculator

GET

/api-tools.json

List every tool with its input ids

GET

/api/keys

Key status and this month's usage

POST

/api/keys

Create or replace the API key

DELETE

/api/keys

Revoke the API key

POST

/api/calculate

Run a calculator

GET

/api-tools.json

List every tool with its input ids

GET

/api/keys

Key status and this month's usage

POST

/api/keys

Create or replace the API key

DELETE

/api/keys

Revoke the API key

Why Jentic?

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

Setup

Wiring MonsiTools by hand means issuing an mt_live_ key from the dashboard, sending it as a bearer token, and looking up each calculator's input ids before the first call. Through Jentic you install once, import MonsiTools from the API Directory, store the key once, and your agent calls it.

Permission scoping

The calculator slug travels in the request body, so rules bound which operations your agent may call, not which calculator it runs. You choose the operations it may call, so key management ones like creating or revoking the API key are not included unless you add them.

Credential isolation

Your MonsiTools 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 'calculate customer lifetime value' or 'estimate AI token cost', and Jentic returns the MonsiTools calculate operation with its input schema, including the slug enum and inputs object.

FAQs

Specific to using MonsiTools Calculation API through Jentic.

What authentication does the MonsiTools Calculation API use?

The spec declares HTTP bearer authentication. POST /api/calculate takes an API key in the form mt_live_... from Dashboard > API access, sent as Authorization: Bearer, while the /api/keys operations expect a signed-in session token instead. GET /api-tools.json is public and needs no token. Through Jentic the key is stored by your own Jentic One instance and attached at call time.

How do I know which inputs a MonsiTools calculator needs?

Call GET /api-tools.json. It returns a map of calculator slug to its name, category, input ids, formula, and whether it is premium. POST /api/calculate requires every input the tool lists; a missing one returns the missing_inputs error rather than computing with a zero.

What are the rate limits for the MonsiTools Calculation API?

The OpenAPI spec states that Premium accounts get 60 requests per minute. Over that limit the API returns the rate_limited error, so an agent running many calculations should pace its calls.

Is there a MonsiTools MCP server?

You don't need an MCP server to give your agent MonsiTools. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent runs calculators on demand without another server's tool definitions in its context.

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

Yes. Write a rule that allows only POST /api/calculate and GET /api-tools.json, so the agent can look up calculators and run them but cannot create a new key or revoke the one you use. Every call it makes is logged.

How do I run a calculator through Jentic?

Search Jentic for 'run a break-even calculation', load the POST /api/calculate operation, and execute it with the slug and an inputs object keyed by the calculator's input ids. The response returns the name, the inputs used, and the numeric result. To run it on your own infrastructure, install Jentic One from its GitHub repo.

MonsiTools Calculation API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness Intelligencebearer5 EndpointsREST

For Agents

Run a named MonsiTools calculator, such as break-even, CAC payback, or AI token cost, by slug with its inputs and get the numeric result back as JSON.

Use for: Calculate the break-even point for a product launch, Find all calculators that MonsiTools offers and their inputs, Get the customer lifetime value from average order value and churn, I need to estimate the token cost of an AI agent run

Not supported: Does not store spreadsheets, evaluate free-form math expressions, or fetch live market prices. Use for running named MonsiTools calculators with supplied inputs only.

The MonsiTools Calculation API runs any of several hundred named calculators and returns the numeric result as JSON. A request names the calculator by its slug, such as customer-lifetime-value-ltv-calculator, break-even-calculator, or ai-token-cost-calculator, and passes a value for every input the tool declares. A public tool listing returns each calculator's name, category, input ids, and formula, so a client knows what to send before calling. Premium accounts can also check key status and monthly usage, and create or revoke their API key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

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

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

15%

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

27%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

80%

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

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MonsiTools Calculation API to your agent

Capabilities

Start building with MonsiTools Calculation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MonsiTools Calculation API

Jentic AI Readiness Score

MonsiTools Calculation 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