Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rétine 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%2Fretine.io%2Fretine" | 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%2Fretine.io%2Fretine" | 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 Rétine API.
Create a monitor
List monitors
Integrate Rétine API into automated workflows
Query and filter Rétine API records by parameters
Monitor Rétine API operational status and events
GET STARTED
Patterns agents use Rétine API for, with concrete tasks.
★ Analytics Operations
Use the Rétine API to perform analytics operations programmatically. The API provides 3 endpoints covering core functionality including create a monitor, list monitors, list screenshots.
Call POST /monitors to create a monitor
Automated monitors Management
Automate monitors operations by combining multiple Rétine API endpoints. Agents can list monitors and then list screenshots in a single workflow.
Call GET /monitors to list monitors, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Rétine API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create a monitor', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — api for visual monitoring and analytics.
METHOD
PATH
DESCRIPTION
/monitors
Create a monitor
/monitors
List monitors
/screenshots
List screenshots
/monitors
Create a monitor
/monitors
List monitors
/screenshots
List screenshots
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Rétine API by hand means passing your API key, targeting the api.retine.io host, and managing monitor and screenshot calls yourself. Through Jentic you install once, import Rétine API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Rétine API takes its inputs in the request body rather than a resource id in the URL path. Limit the agent to the operations it needs, such as creating a monitor or listing screenshots, so it works within the operations you approve.
Credential isolation
Your Rétine 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 'create a monitor' or 'list screenshots', and Jentic returns the matching Rétine API 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 Rétine API through Jentic.
What authentication does the Rétine API use?
The Rétine API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a monitor with the Rétine API?
Yes. Use the POST /monitors endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Rétine API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a monitor through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a monitor'. Jentic returns the matching Rétine API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Rétine API have?
The Rétine API exposes 3 endpoints covering monitors, screenshots operations.
Can I limit what my agent is allowed to do with the Rétine API?
Yes. Because you run Jentic One yourself, your own rules decide which Rétine API operations the agent may call, so you can approve just the ones it needs, such as creating a monitor with POST /monitors or listing screenshots with GET /screenshots, while withholding the rest. Since the Rétine API takes its inputs in the request body rather than a resource id in the URL path, you scope access at the operation level and the agent works only within the calls you allow. Your Rétine API key is held encrypted by your own instance and injected at execution time, so it never enters the agent's prompt or context.
For Agents
Programmatically create a monitor, list monitors. Covers 3 operations with apiKey authentication.
Use for: I need to a monitor, I want to monitors, Search for screenshots, List all records from Rétine API
Not supported: Does not handle payments, communications, or crm - use for analytics only.
API for visual monitoring and analytics. The API exposes 3 endpoints secured with apiKey authentication.
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>