Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Klingo API Informações, 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%2Fklingo.app%2Fklingo-informacoes" | shStep 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%2Fklingo.app%2Fklingo-informacoes" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Klingo API Informações API.
Retrieve material and medication consumption for a given month
Pull recorded financial expenses for a month from the finance module
Get production figures for a date range using the start and end parameters
Read general system report data for the clinic
Patterns agents use Klingo API Informações API for, with concrete tasks.
GET STARTED
★ Report clinic figures to an AI agent
An AI agent integration created through Jentic needs current operating numbers. The Klingo Informações API returns consumption, expense, production, and report data on demand, so the agent can answer questions about the clinic's month without a human exporting spreadsheets. Each call targets one read-only reporting endpoint.
Retrieve this month's consumption and expense figures and summarize them for the user
Monthly consumption and expense review
A clinic manager wants a monthly snapshot of material usage and spending. The Klingo Informações API serves consumption for a month and the finance module's recorded expenses, both selected with the month parameter, so an automation can assemble the review without manual lookups.
Pull consumption and expenses for the current month and flag any month-over-month increase
Production trend over a date range
Tracking output over time needs figures across a window, not just one month. The Klingo Informações API returns production figures filtered by the start and end parameters, letting an agent build a trend for a chosen date range from the clinic's own data.
Retrieve production figures between two dates and report the trend
4 endpoints — the klingo informações api retrieves operational and financial reporting data from klingo's clinic management system.
METHOD
PATH
DESCRIPTION
/consumos
Retrieve material and medication consumption for a month
/despesas
Retrieve recorded financial expenses for a month
/producao
Retrieve production figures for a date range
/relatorio
Retrieve system report data
/consumos
Retrieve material and medication consumption for a month
/despesas
Retrieve recorded financial expenses for a month
/producao
Retrieve production figures for a date range
/relatorio
Retrieve system report data
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Klingo Informações by hand means setting the X-APP-TOKEN header on every call and matching the right base path for the info service. Through Jentic you install once, import Klingo Informações from the API Directory, store the token once, and your agent calls it.
Permission scoping
Every operation here is read-only, and the month and date filters travel in the query string, so rules bound which reporting operations your agent may call, not which month. You can allow consumption and expense reads while leaving production and report reads out unless you add them.
Credential isolation
Your Klingo application 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 monthly consumption' or 'read clinic expenses', and Jentic returns the matching Klingo Informações operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Klingo API Informações API through Jentic.
What authentication does the Klingo Informações API use?
The Klingo Informações API authenticates with an application key sent in the X-APP-TOKEN request header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.
Can I read monthly consumption and expenses with the Klingo Informações API?
Yes. The consumption endpoint returns material and medication usage for a month and the expenses endpoint returns recorded finance-module expenses, both selected with the month parameter, so an agent can assemble a monthly snapshot.
Can I get production figures for a date range?
Yes. The production endpoint accepts optional start and end parameters alongside the month, so an agent can request figures for a specific window and build a trend from the clinic's own data.
How do I pull Klingo reporting data through Jentic?
Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Klingo Informações API from the API Directory and search for 'get monthly clinic consumption and expenses'. Store the application token once and your agent can read the reports. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Klingo Informações MCP server?
You don't need an MCP server to give your agent the Klingo Informações API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls it, with each reporting operation discovered on demand instead of loaded into the agent's context.
Can I limit what my agent is allowed to do with the Klingo Informações API?
Yes. Every operation here is read-only, so you choose which reporting endpoints the agent may call, such as consumption and expenses while leaving production and reports out. The month and date parameters travel in the query string, so a rule bounds which operations run rather than which month, and every action is recorded in an audit log.
Know of an official OpenAPI document? Contribute it →
For Agents
Read monthly consumption, recorded expenses, production figures, and system reports from Klingo's clinic management system.
Use for: Get this month's material and medication consumption, Retrieve recorded expenses for a given month, Show production figures between two dates, Pull the clinic's system report
Not supported: Does not create records, schedule appointments, or process payments. Use for reading Klingo consumption, expense, production, and report data only.
The Klingo Informações API retrieves operational and financial reporting data from Klingo's clinic management system. It returns material and medication consumption for a month, financial expenses recorded in the finance module, production figures over a date range, and general system report data. Each endpoint is read-only and controlled by an application token in a request header.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>