Hund API

Name: Hund API API
Brand: Hund API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer, basic14 EndpointsREST

For Agents

Open and update incidents, post events, manage components, and drive a Hund status page from an AI agent or automation pipeline.

Quickstart

Get started with Hund API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"open a status page incident"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Hund API API.

Open a new Hund issue with title, body, severity, and affected components

Append events to an existing issue to track incident progress and resolution

Add or remove components from a component group on a status page

Configure watchdog monitors and preview their next scheduled check

Post custom metric values to a metric provider for status page graphs

GET STARTED

Start building with Hund API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Hund API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Hund API, keeping it validated and agent-ready. Hund is a hosted status page and incident-management platform; its API exposes 14 endpoints for managing components, component groups, issues, events, statuses, watchdogs, and metric providers that drive a live status page. Operators can open and update incidents, attach events to existing issues, configure watchdog probes, and post custom metric data programmatically. Authentication uses HTTP bearer tokens or HTTP basic credentials issued from the Hund dashboard.

Use Cases

Patterns agents use Hund API API for, with concrete tasks.

★ Automated Incident Reporting

Wire monitoring alerts from observability tools into Hund so that PagerDuty or Datadog incidents automatically open a public issue on the company status page. The /issues endpoint creates a new issue with affected components, severity, and a description, and the /events endpoint attaches subsequent updates as the incident progresses. Customers get visibility within seconds of detection.

POST to /issues with title='Payments degraded', severity='major', and affected_component_ids=['payments'] then attach an /events update.

Component and Group Management

Programmatically maintain the structure of a status page as services come and go: add a new microservice as a component, attach it to a Production group, and remove deprecated components. This avoids drift between the service catalogue and the public status page when the engineering team ships fast.

Call POST /groups/{group_id}/add_component with the new payments-v2 component id.

Custom Metric Reporting

Push application metrics like API latency, queue depth, or error rate into Hund metric providers so the status page graphs reflect live performance. The watchdog endpoint also lets operators preview the next probe to confirm a configuration before it ships. Together they keep status page data in sync with internal monitoring.

PATCH /metric_providers/{metric_provider_id} to publish a new latency reading of 123ms.

AI Agent Incident Response

Give an on-call AI agent the ability to open and update Hund incidents directly. Through Jentic, the agent searches for 'open a status page incident', loads the input schema, and executes a POST to /issues with the right severity and components. Bearer credentials stay in the Jentic vault rather than the agent context, which matters when the agent is exposed to user prompts.

Search Jentic for 'open a status page incident', load the Hund POST /issues schema, and execute with the affected components and severity.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/issues/{issue_id}

Retrieve an issue by id

POST

/events

Append an event to an issue

POST

/groups/{group_id}/add_component

Add a component to a group

GET

/statuses

List configured statuses

PATCH

/metric_providers/{metric_provider_id}

Update a metric provider

GET

/watchdogs/preview

Preview the next watchdog check

GET

/context

Retrieve account and domain context

GET

/issues/{issue_id}

Retrieve an issue by id

POST

/events

Append an event to an issue

POST

/groups/{group_id}/add_component

Add a component to a group

GET

/statuses

List configured statuses

PATCH

/metric_providers/{metric_provider_id}

Update a metric provider

Why though Jentic?

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

Credential isolation

Hund bearer or basic credentials are stored encrypted in the Jentic vault. Agents receive a scoped reference and Jentic injects the Authorization header at execution time, so the raw token never enters the agent's context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'open a status page incident') and Jentic returns the matching Hund operation with its input schema, so the agent can call the correct endpoint without browsing docs.

Time to first call

Direct integration with Hund: 1-2 days to wire up auth, error handling, and event sequencing for a basic incident flow. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Atlassian Statuspage

Statuspage is the Atlassian-owned alternative to Hund with deeper enterprise integrations and a larger feature surface

Choose Statuspage if the team already runs Atlassian tooling; choose Hund for a lighter, status-page-focused product

Complementary

PagerDuty API

PagerDuty handles on-call paging while Hund handles public status communication — they pair naturally

Use PagerDuty to page the on-call engineer and Hund to update the public status page about the same incident

Complementary

Opsgenie API

Opsgenie alerts on-call responders and integrates with Hund for downstream public status communication

Use Opsgenie for incident routing inside the team and Hund for customer-facing incident updates

FAQs

Specific to using Hund API API through Jentic.

Why is there no official OpenAPI spec for Hund API?

Hund does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hund 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 Hund API use?

The Hund API supports both HTTP bearer tokens and HTTP basic authentication. Through Jentic the credentials are stored in the credential vault and injected at execution time, so the agent only sees a scoped reference rather than the raw token.

Can I open an incident on the Hund status page through the API?

Yes. POST to /issues with a title, severity, and the affected component ids to open a new incident, then call POST /events to append progress updates as the situation changes. Both endpoints authenticate with the same bearer token.

What are the rate limits for the Hund API?

The OpenAPI spec does not declare numeric rate limits. Check the Hund help docs at hund.io/help/api for current limits before scaling agent traffic, and watch for HTTP 429 responses to back off automatically.

How do I add a component to a group through Jentic?

Search Jentic for 'add a component to a status page group', load the schema for POST /groups/{group_id}/add_component, and execute with the group id and component id. Install with pip install jentic and use the async search, load, and execute pattern.

Can I push custom metrics to a Hund status page?

Yes. PATCH the /metric_providers/{metric_provider_id} endpoint with the new metric reading to update the graph displayed on the status page. This is suited to publishing application latency, queue depth, or error rates from observability pipelines.