Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Status.io API v2, 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%2Fstatus.io%2Fstatus" | 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%2Fstatus.io%2Fstatus" | 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 Status.io API v2 API.
admin/ip_access_control/list
admin/ip_access_control/update/ipv4
admin/ip_access_control/update/ipv6
admin/ssl_cert/update
component/list
GET STARTED
component/status/update
incident/create
Patterns agents use Status.io API v2 API for, with concrete tasks.
★ Communications Operations
Use the Status.io API v2 to perform communications operations programmatically. The API provides 36 endpoints covering core functionality including admin/ip_access_control/list, admin/ip_access_control/update/ipv4, admin/ip_access_control/update/ipv6.
Call GET /admin/ip_access_control/list/{statuspage_id} to admin/ip_access_control/list
Automated Components Management
Automate components operations by combining multiple Status.io API v2 endpoints. Agents can admin/ip_access_control/update/ipv4 and then admin/ip_access_control/update/ipv6 in a single workflow.
Call POST /admin/ip_access_control/update/ipv4 to admin/ip_access_control/update/ipv4, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Status.io API v2 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 none tokens manually.
Search Jentic for 'admin/ip_access_control/list', load the operation schema, and execute with Jentic-managed credentials
36 endpoints — welcome to the official [status.
METHOD
PATH
DESCRIPTION
/admin/ip_access_control/list/{statuspage_id}
admin/ip_access_control/list
/admin/ip_access_control/update/ipv4
admin/ip_access_control/update/ipv4
/admin/ip_access_control/update/ipv6
admin/ip_access_control/update/ipv6
/admin/ssl_cert/update
admin/ssl_cert/update
/component/list/{statuspage_id}
component/list
/component/status/update
component/status/update
/incident/create
incident/create
/incident/delete
incident/delete
/admin/ip_access_control/list/{statuspage_id}
admin/ip_access_control/list
/admin/ip_access_control/update/ipv4
admin/ip_access_control/update/ipv4
/admin/ip_access_control/update/ipv6
admin/ip_access_control/update/ipv6
/admin/ssl_cert/update
admin/ssl_cert/update
/component/list/{statuspage_id}
component/list
/component/status/update
component/status/update
/incident/create
incident/create
/incident/delete
incident/delete
What agents get from Jentic-routed access to this vendor.
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Status.io API v2 API through Jentic.
What authentication does the Status.io API v2 use?
The Status.io API v2 uses no authentication. 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 admin/ip_access_control/list with the Status.io API v2?
Yes. Use the GET /admin/ip_access_control/list/{statuspage_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Status.io API v2?
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 admin/ip_access_control/list through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'admin/ip_access_control/list'. Jentic returns the matching Status.io API v2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Status.io API v2 have?
The Status.io API v2 exposes 36 endpoints covering components, incidents, maintenance operations.
Can I limit what my agent is allowed to do with the Status.io API v2?
Yes. Because Jentic One is self-hosted, your own rules decide which Status.io operations and credential the agent may use, so you can allow it to list components or create an incident while excluding the admin IP access control, SSL certificate, and delete operations unless you add them. Since the create and delete calls take their target in the request body, scope the agent by operation rather than by a single status page. The credential is injected only for the operations you permit, so the agent cannot reach anything outside that set.
For Agents
Programmatically admin/ip_access_control/list, admin/ip_access_control/update/ipv4. Covers 36 operations.
Use for: I need to admin/ip_access_control/list, I want to admin/ip_access_control/update/ipv4, Search for admin/ip_access_control/update/ipv6, Find all admin/ssl_cert/update
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Welcome to the official [Status.io](https://status.io) Developer API. This API is designed to help you seamlessly integrate your existing tools with your status page. API Testing Live Sandbox Use the built-in API client to test and debug API calls, and view example requests in multiple programming languages. **Caution:** These are live API calls and will make real changes to your status page. We s. The API exposes 36 endpoints.
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>