Install Jentic One Beta

Connect the SIGNL4 API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SIGNL4 API V1, 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%2Fsignl4.com%2Fsignl4" | 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%2Fsignl4.com%2Fsignl4" | 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 SIGNL4 API V1 API.

Trigger Alert

Get Alert

Acknowledge an alert

Annotate Alert

Monitor SIGNL4 API V1 operational status and events

Use Cases

GET STARTED

Start building with SIGNL4 API V1 API

Explore with Jentic One

View OpenAPI Document

Automated Alerts Management

Automate alerts operations by combining multiple SIGNL4 API V1 endpoints. Agents can get alert and then acknowledge an alert in a single workflow.

Call GET /alerts/{alertId} to get alert, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SIGNL4 API V1 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, oauth2 tokens manually.

Search Jentic for 'trigger alert', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

109 endpoints — <p>use our api for systems integration or to build your own use cases.

METHOD

PATH

DESCRIPTION

POST

/alerts

Trigger Alert

GET

/alerts/{alertId}

Get Alert

POST

/alerts/{alertId}/acknowledge

Acknowledge an alert

POST

/alerts/{alertId}/annotate

Annotate Alert

GET

/alerts/{alertId}/annotations

Get annotations of an alert

GET

/alerts/{alertId}/attachments

Get attachments of an alert

GET

/alerts/{alertId}/attachments/{attachmentId}

Gets a specified attachment of a specified alert.

POST

/alerts/{alertId}/close

Close an alert

POST

/alerts

Trigger Alert

GET

/alerts/{alertId}

Get Alert

POST

/alerts/{alertId}/acknowledge

Acknowledge an alert

POST

/alerts/{alertId}/annotate

Annotate Alert

GET

/alerts/{alertId}/annotations

Get annotations of an alert

GET

/alerts/{alertId}/attachments

Get attachments of an alert

GET

/alerts/{alertId}/attachments/{attachmentId}

Gets a specified attachment of a specified alert.

POST

/alerts/{alertId}/close

Close an alert

Why Jentic?

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

Setup

Wiring SIGNL4 by hand means choosing between its x-s4-api-key header and OAuth2 authorization-code auth with read and write scopes, and pointing calls at https://connect.signl4.com/api. Through Jentic you install once, import SIGNL4 from the API Directory, store the credential once, and your agent calls it.

Permission scoping

SIGNL4 puts the alert id in the URL path (/alerts/{alertId}), so a rule can pin your agent to one alert: it can acknowledge, annotate, and read that alert and nothing else. You choose the operations it may call, so closing an alert is not included unless you add it.

Credential isolation

Your SIGNL4 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 'trigger an alert' or 'acknowledge an alert', and Jentic returns the matching SIGNL4 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SIGNL4 API V1 API through Jentic.

What authentication does the SIGNL4 API V1 use?

The SIGNL4 API V1 uses apiKey, oauth2 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 trigger alert with the SIGNL4 API V1?

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

What are the rate limits for the SIGNL4 API V1?

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 trigger alert through Jentic?

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

How many endpoints does the SIGNL4 API V1 have?

The SIGNL4 API V1 exposes 109 endpoints covering alerts, categories, duties operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which SIGNL4 operations and credentials your agent may use. SIGNL4 puts the alert id in the URL path (/alerts/{alertId}), so you can pin an agent to a single alert and allow only acknowledge, annotate, and read on it. Closing an alert or triggering a new one via POST /alerts stays off limits unless you explicitly add those operations.

SIGNL4 API V1

Name: SIGNL4 API V1 API
Brand: SIGNL4 API V1
Availability: InStock

AI ReadinessFoundational (D)47/100

See full scorecard

ProductivityCalendar SchedulingapiKey, oauth2109 EndpointsREST

For Agents

Programmatically trigger alert, get alert. Covers 109 operations with apiKey, oauth2 authentication.

Use for: I need to trigger alert, I want to alert, Search for acknowledge an alert, Find all annotate alert

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

<p>Use our API for systems integration or to build your own use cases. Sample scenarios include but are not limited to:</p><ul><li>2-way integration: Triggering of Signls and updates in the third party systems when alert state changes occur</li><li>Retrieving alarms for logging purposes</li><li>Calendar integrations: Creation and management of on-call duties</li><li>Punch users in and out based on. The API exposes 109 endpoints secured with apiKey, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

75%

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.

72%

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: FSignals: 4

43%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

82%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

52%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SIGNL4 API V1 to your agent

Capabilities

Use Cases

Start building with SIGNL4 API V1 API

Key Endpoints

Why Jentic?

Related APIs

FAQs

SIGNL4 API V1

Jentic AI Readiness Score

SIGNL4 API V1

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