canonical: https://jentic.com/apis/senseon.io/senseon # Senseon API Senseon AI-driven cybersecurity platform API for threat detection, incident management, and security analytics. The API exposes 11 endpoints secured with bearer authentication. ## For AI agents Programmatically list alerts, get alert. Covers 11 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for security only. ## Capabilities - List alerts - Get alert - Update alert status - Create incident - Monitor Senseon API operational status and events ## Use cases ### Security Operations Use the Senseon API to perform security operations programmatically. The API provides 11 endpoints covering core functionality including list alerts, get alert, update alert status. Example prompt: Call GET /alerts to list alerts ### Automated alerts Management Automate alerts operations by combining multiple Senseon API endpoints. Agents can get alert and then update alert status in a single workflow. Example prompt: Call GET `/alerts/{alertId}` to get alert, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Senseon 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 bearer tokens manually. Example prompt: Search Jentic for 'list alerts', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/alerts` | List alerts | | GET | `/alerts/{alertId}` | Get alert | | PATCH | `/alerts/{alertId}` | Update alert status | | POST | `/incidents` | Create incident | | GET | `/incidents` | List incidents | | GET | `/incidents/{incidentId}` | Get incident | | PUT | `/incidents/{incidentId}` | Update incident | | GET | `/threats` | List threats | ## Key resources - **alerts** — Security alerts management - **incidents** — Security incidents - **threats** — Threat intelligence - **assets** — Asset management ## 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: 93 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/senseon.io/senseon/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 Senseon by hand means obtaining a bearer token and attaching it to every alert, incident, and threat call yourself. Through Jentic you install once, import Senseon from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Senseon puts the alert and incident ids in the URL path (`/alerts/{alertId}`, `/incidents/{incidentId}`), so a rule can pin your agent to reading and updating specific alerts and incidents. You choose the operations it may call, so an incident update via PUT is not included unless you add it. - **Credential handling:** Your Senseon 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. - **Discovery method:** Agents search Jentic by intent such as 'list alerts' or 'get an incident', and Jentic returns the matching Senseon operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Snyk** — Alternative security API - **Crowdstrike** — Alternative security API ## FAQ ### What authentication does the Senseon API use? The Senseon API uses a Bearer token 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 list alerts with the Senseon API? Yes. Use the GET /alerts endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Senseon 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 list alerts through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list alerts'. Jentic returns the matching Senseon API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Senseon API have? The Senseon API exposes 11 endpoints covering alerts, incidents, threats operations. ### Can I limit what my agent is allowed to do with the Senseon API? Yes. Because you run Jentic One yourself, your own rules decide which Senseon operations and credentials the agent may use. Since Senseon carries the alert and incident ids in the URL path (`/alerts/{alertId}`, `/incidents/{incidentId}`), you can pin the agent to reading and updating specific alerts and incidents. You choose the operations it may call, so an incident update via PUT `/incidents/{incidentId}` is excluded unless you explicitly add it.