Install Jentic One Beta

Connect the StatusCake API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the StatusCake 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%2Fstatuscake.com%2Fstatuscake" | sh

Step 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%2Fstatuscake.com%2Fstatuscake" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with StatusCake API.

Create uptime check

List uptime checks

Get uptime check

Update uptime check

Delete uptime check

Use Cases

GET STARTED

Start building with StatusCake API

Explore with Jentic One

View OpenAPI Document

Automated Contact Groups Management

Automate contact groups operations by combining multiple StatusCake API endpoints. Agents can list uptime checks and then get uptime check in a single workflow.

Call GET /uptime to list uptime checks, then verify the result

AI Agent Integration via Jentic

AI agents discover and call StatusCake 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 uptime check', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

29 endpoints — statuscake provides website monitoring services.

METHOD

PATH

DESCRIPTION

POST

/uptime

Create uptime check

GET

/uptime

List uptime checks

GET

/uptime/{testId}

Get uptime check

PUT

/uptime/{testId}

Update uptime check

DELETE

/uptime/{testId}

Delete uptime check

GET

/uptime/{testId}/history

Get uptime check history

GET

/uptime/{testId}/periods

Get uptime check periods

GET

/uptime/{testId}/alerts

Get uptime check alerts

POST

/uptime

Create uptime check

GET

/uptime

List uptime checks

GET

/uptime/{testId}

Get uptime check

PUT

/uptime/{testId}

Update uptime check

DELETE

/uptime/{testId}

Delete uptime check

GET

/uptime/{testId}/history

Get uptime check history

GET

/uptime/{testId}/periods

Get uptime check periods

GET

/uptime/{testId}/alerts

Get uptime check alerts

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the StatusCake API by hand means setting up its Authorization header key, mapping the uptime test endpoints, and threading the test id through history, periods and alerts calls yourself. Through Jentic you install once, import the StatusCake API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

StatusCake puts the test id in the URL path (/uptime/{testId}, /uptime/{testId}/history), so a rule can pin your agent to one uptime test: it can read that test's history, periods and alerts and nothing else. You choose the operations it may call, so deleting a test is not included unless you add it.

Credential isolation

Your StatusCake 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 an uptime check' or 'read a test's uptime history', and Jentic returns the matching StatusCake API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using StatusCake API through Jentic.

What authentication does the StatusCake API use?

The StatusCake 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 uptime check with the StatusCake API?

Yes. Use the POST /uptime endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the StatusCake 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 uptime check through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create uptime check'. Jentic returns the matching StatusCake API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the StatusCake API have?

The StatusCake API exposes 29 endpoints covering contact groups, heartbeat, locations operations.

Can I limit what my agent is allowed to do with the StatusCake API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which StatusCake operations and credentials your agent can use. StatusCake carries the test id in the URL path, such as /uptime/{testId} and /uptime/{testId}/history, so you can pin an agent to a single uptime test and let it read only that test's history, periods, and alerts. You choose exactly which operations it may call, so destructive actions like deleting a test stay off limits unless you grant them.

StatusCake API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey29 EndpointsREST

For Agents

Programmatically create uptime check, list uptime checks. Covers 29 operations with apiKey authentication.

Use for: I need to uptime check, I want to uptime checks, Search for uptime check, Find all uptime check

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

StatusCake provides website monitoring services. The API allows programmatic management of uptime checks, SSL checks, pagespeed checks, heartbeat checks, maintenance windows, and contact groups. The API exposes 29 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

55%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

66%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the StatusCake API to your agent

Capabilities

Use Cases

Start building with StatusCake API

Key Endpoints

Why Jentic?

Related APIs

FAQs

StatusCake API

Jentic AI Readiness Score

StatusCake API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness