Alerty API

Name: Alerty API
Brand: Alerty API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer, apiKey52 EndpointsREST

For Agents

Query logs, metrics, and traces, manage monitors and incidents, and chat with Alerty's AI over your observability data through 52 endpoints.

Install Jentic One Beta

Connect the Alerty API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alerty 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Alerty API.

Run a logs, metrics, or traces query against ingested telemetry via /query/logs, /query/metrics, and /query/traces

Create and manage monitors that watch for conditions in observability data

Open, update, and resolve incidents tied to monitor breaches

GET STARTED

Start building with Alerty API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Alerty API, keeping it validated and agent-ready. Alerty is a developer monitoring platform that combines logs, metrics, traces, monitors, and incident management with an AI chat interface. The REST API exposes endpoints for organisation and member management, integrations (such as Slack), monitor and incident lifecycle, telemetry queries against logs/metrics/traces, inventory of detected services, and a chat interface for asking questions about observability data. Authentication uses a bearer token; some endpoints also accept a session cookie.

Use Cases

Patterns agents use Alerty API for, with concrete tasks.

★ AI-assisted incident triage

An on-call agent receives an alert and immediately POSTs to /chat to start a conversation with the Alerty AI, then sends follow-up messages via /chat/{id}/message asking for a summary of recent error spikes. The chat references underlying logs and metrics, so the engineer gets a contextual triage report without writing query strings by hand.

POST /chat to start a conversation, then POST /chat/{id}/message with a triage prompt describing the alert and the affected service

Programmatic log query for SRE automation

An SRE pipeline runs nightly checks for error log patterns by POSTing to /query/logs with filter expressions and a time range, then writes the result counts to a status board. Because the API returns structured results, the same pipeline can also drive automated rollbacks when error counts cross a threshold.

POST /query/logs with the service filter and timeframe, parse the count, and trigger the rollback workflow when the threshold is exceeded

Incident lifecycle automation

A deploy pipeline opens an incident in Alerty when a release fails health checks, posts updates from the deploy logs, and closes the incident once the rollback succeeds. The integration uses the incident endpoints alongside monitor lookups so the team has a single timeline of every release event without manual ticket entry.

POST to the incident create endpoint with the failing service, PATCH the incident as the rollback progresses, then close it once health checks pass

Agent-driven observability lookup through Jentic

A Jentic agent answers questions like 'what services are deployed in production?' by calling the Alerty inventory endpoint and filtering by environment. The same agent can chain a metrics query if the user asks 'and which one had the highest error rate yesterday?'. The bearer token stays in the Jentic vault.

Search Jentic for 'list services in Alerty inventory', execute the inventory endpoint, then chain POST /query/metrics with an error rate expression for the top services

Key Endpoints

52 endpoints — jentic publishes the only available openapi specification for alerty api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/query/logs

Query logs

POST

/query/metrics

Query metrics

POST

/chat

Create a chat conversation

POST

/chat/{id}/message

Send a chat message

GET

/integration

List integrations

POST

/integration/{id}/test

Trigger a test for an integration

POST

/organization/{id}/invitation

Invite a member to an organisation

POST

/query/logs

Query logs

POST

/query/metrics

Query metrics

POST

/chat

Create a chat conversation

POST

/chat/{id}/message

Send a chat message

GET

/integration

List integrations

POST

/integration/{id}/test

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Alerty bearer token is stored encrypted in the Jentic credential vault and injected as the Authorization header at execution time. The agent never sees the raw token in its context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'query logs in Alerty', 'open an incident'), and Jentic returns the matching Alerty operation with its input schema for direct execution.

Time to first call

Direct Alerty integration: 2-3 days to wire auth, query payloads, and incident lifecycle. Through Jentic: under an hour with search, load, and execute.

FAQs

Specific to using Alerty API through Jentic.

Why is there no official OpenAPI spec for Alerty API?

Alerty does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Alerty API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Alerty API use?

Alerty uses an HTTP bearer token in the Authorization header for programmatic access; certain endpoints also accept a __lumos_session cookie for browser flows. Jentic stores the bearer token encrypted in its credential vault and injects it at execution time.

Can I run a logs query against Alerty programmatically?

Yes. POST /query/logs with your filter expression, a time range, and any pagination parameters. Alerty returns structured rows you can drive into automation, dashboards, or downstream alerts.

What are the rate limits for the Alerty API?

The OpenAPI spec does not declare rate limits. Alerty enforces them server-side based on workspace plan; throttle long-running query and chat workflows and check for 429 responses.

How do I start an Alerty AI chat conversation through Jentic?

Search Jentic for 'start an alerty chat conversation', execute POST /chat to create the conversation, then POST /chat/{id}/message to send the question. Jentic returns the assistant's response without the bearer token leaving the vault.

Can I open and close incidents with the Alerty API?

Yes. The incident endpoints let you create incidents tied to a monitor or service, post updates as the situation evolves, and resolve the incident when the issue is fixed. This lets a deploy pipeline keep an end-to-end timeline in Alerty automatically.

Alerty API

Connect the Alerty API to your agent

Capabilities

Start building with Alerty API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs