Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SIC 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%2Fcsso.cl%2Fcsso" | 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%2Fcsso.cl%2Fcsso" | 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 SIC API.
Report a patient admission or update by episode
Record a patient's diet regimen
Report a patient's bed or location change
Request a cleaning service for an admission or bed move
Register parking entry and exit for a vehicle plate
GET STARTED
Log staff entry and exit
Patterns agents use SIC API for, with concrete tasks.
★ Agent-driven patient event sync
An AI agent connected through Jentic forwards patient events from a source system into SIC, reporting an admission, then the patient's diet regimen, then any bed move. Each event is tied to the patient's episode, so SIC keeps a consistent patient record without a human re-keying it.
Report a patient admission, then record the patient's diet regimen for the same episode
Facility services triggers
When a patient is admitted or moved, a workflow requests a cleaning service for the affected location so housekeeping is notified automatically. The SIC API exposes a dedicated cleaning-request operation triggered by admission or bed-move context.
Submit a cleaning request for a patient location after reporting a bed move
Access and staffing logs
An integration logs parking access for vehicle plates and staff entry and exit into SIC, giving the hospital a single record of who and what entered. The parking and staffing operations accept entry and exit events so access data flows into the same system as patient events.
Register a parking entry for a vehicle plate and log a staff member's entry
12 endpoints — the sic api reports hospital events into the salud ness sic system, keeping patient and facility records in sync with an external source.
METHOD
PATH
DESCRIPTION
/alimentacionPacientes/pacient
Report a patient admission or update
/alimentacionPacientes/pacient/{numepisodio}
Update a patient by episode
/alimentacionPacientes/pacientDiet
Record a patient's diet regimen
/alimentacionPacientes/pacientLocation
Report a patient bed or location change
/aseo/request
Request a cleaning service
/estacionamiento/entry
Register parking entry for a vehicle plate
/alimentacionPacientes/pacient
Report a patient admission or update
/alimentacionPacientes/pacient/{numepisodio}
Update a patient by episode
/alimentacionPacientes/pacientDiet
Record a patient's diet regimen
/alimentacionPacientes/pacientLocation
Report a patient bed or location change
/aseo/request
Request a cleaning service
/estacionamiento/entry
Register parking entry for a vehicle plate
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SIC API by hand means handling HTTP Basic credentials against the SIC integration host and mapping your source events to its patient, cleaning, parking, and staffing operations. Through Jentic you install once, import SIC from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
SIC groups its operations by event type, and rules bound which operations your agent may call. You choose the operations it may call, so it can report patient admissions and diets without being able to log parking or staff events unless you add those.
Credential isolation
Your SIC 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 'report a patient admission' or 'request a cleaning service', and Jentic returns the matching SIC 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 SIC API through Jentic.
What authentication does the SIC API use?
The SIC API uses HTTP Basic authentication against the SIC integration host, per its OpenAPI spec. Through Jentic the credentials are stored once by your own self-hosted instance and injected when a call runs, so they never appear in the agent's prompt or logs.
Can I report a patient admission with the SIC API?
Yes. Use the patient operation to report an admission or update, and the diet and location operations to record a diet regimen or a bed move. Updates to an existing patient are made by episode through the patient update operation.
Can I limit what my agent is allowed to do with the SIC API?
Yes. Write a rule that allows only the event operations the agent needs, such as patient admission and diet, so it cannot report parking or staff events, and every call it makes is logged. Add other operations only when the integration requires them.
What are the rate limits for the SIC API?
The OpenAPI spec does not specify rate limits. Check the Salud Ness SIC integration documentation for current limits before sending high volumes of patient or facility events.
Is there a SIC MCP server?
You don't need an MCP server to give your agent the SIC API. Jentic connects it directly from the API Directory: import it, store the credentials once, and your agent calls the patient and facility operations on demand without loading another server's tool definitions into its context.
How do I report a patient event with the SIC API through Jentic?
Search Jentic by intent such as 'report a patient admission', and Jentic returns the patient operation with its input schema so your agent fills in the patient and episode details. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Report hospital events into the Salud Ness SIC system: patient admissions and updates, diet regimens, bed moves, cleaning requests, parking access, and staff entry and exit.
Use for: Report a new patient admission to the SIC system, Update an existing patient by episode, Record the diet regimen for this patient, Report that a patient moved to a new bed
Not supported: Does not handle clinical charting, lab results, or billing. Use for reporting patient and facility events into the Salud Ness SIC system only.
The SIC API reports hospital events into the Salud Ness SIC system, keeping patient and facility records in sync with an external source. It records patient admissions and updates, a patient's diet regimen, and a patient's bed or location change, each tied to an episode. It also logs operational events: staff dining-room entry, cleaning requests triggered by an admission or bed move, parking access for a vehicle plate, and staff entry and exit. Every call uses HTTP Basic authentication against the SIC integration host.
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>