Status.io API v2

Setup

Wiring the Status.io API by hand means learning its request conventions, mapping the component, incident and maintenance endpoints, and handling the admin IP and SSL calls yourself. Through Jentic you install once, import the Status.io API v2 from the API Directory, store the credential once, and your agent calls it.

Permission scoping

You limit the agent to the operations it needs, such as listing components or creating an incident, so it never runs admin IP or deletion calls unless you include them. Because create and delete take their target in the request body, scope the agent by operation rather than by a single status page.

Credential isolation

Your Status.io credential 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 'list status page components' or 'create an incident', and Jentic returns the matching Status.io API v2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.