canonical: https://jentic.com/apis/retine.io/retine # Retine Rétine API API for visual monitoring and analytics. The API exposes 3 endpoints secured with apiKey authentication. ## For AI agents Programmatically create a monitor, list monitors. Covers 3 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for analytics only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a monitor', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/monitors` | Create a monitor | | GET | `/monitors` | List monitors | | GET | `/screenshots` | List screenshots | ## Key resources - **monitors** — Operations related to monitors - **screenshots** — Operations related to screenshots ## AI readiness 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. - **Score:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/retine.io/retine/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Mixpanel** — Alternative analytics API - **Amplitude** — Alternative analytics API - **Segment** — Complementary analytics API - **Pendo** — Complementary analytics API ## FAQ ### 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.