> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kodostatus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Kodo Status Documentation

> Developer-first status pages with built-in monitoring, error tracking, and incident management

# Welcome to Kodo Status

Kodo is the **developer-first** status page platform. Unlike legacy tools that require clicking through dashboards, Kodo is built API-first with a powerful CLI, so you can manage incidents, monitors, and status pages the same way you manage code.

<CardGroup cols={2}>
  <Card title="Quick Start" icon="rocket" href="/quickstart">
    Deploy your first status page in 5 minutes
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    Full REST API with 50+ endpoints
  </Card>

  <Card title="CLI Tool" icon="terminal" href="/integrations/cli">
    Git-like workflow for incident management
  </Card>

  <Card title="Monitoring" icon="chart-line" href="/monitoring/uptime-monitors">
    Built-in uptime, SSL, and heartbeat monitoring
  </Card>
</CardGroup>

## Why Kodo?

<AccordionGroup>
  <Accordion title="Built for developers, not dashboards" icon="code">
    **The Problem**: Traditional status pages force you into clunky web UIs. Creating an incident means clicking through forms while your users are waiting.

    **Kodo's Solution**: Create incidents from your terminal, CI/CD pipeline, or monitoring alerts. One command: `kodo incidents create --title "API Degraded" --severity major`.
  </Accordion>

  <Accordion title="Monitoring + Status Page = One Tool" icon="layer-group">
    **The Problem**: You're paying for a status page AND uptime monitoring AND error tracking. Three tools, three dashboards, three bills.

    **Kodo's Solution**: Uptime monitors, heartbeat tracking, SSL/domain monitoring, and client-side error tracking—all feeding into your status page automatically.
  </Accordion>

  <Accordion title="Automate incident response" icon="bolt">
    **The Problem**: When something breaks at 3 AM, you're manually updating status pages, paging on-call, and copying error messages.

    **Kodo's Solution**: Workflows automatically create incidents from monitor failures, notify the right team, and update your status page. You focus on fixing, not communicating.
  </Accordion>

  <Accordion title="Real error tracking, not just uptime" icon="bug">
    **The Problem**: "Site is up" doesn't mean "site is working." Your uptime monitor says 100% while JavaScript errors frustrate users.

    **Kodo's Solution**: The Beacon SDK captures frontend errors, performance issues, and user impact—then correlates them with your status page.
  </Accordion>
</AccordionGroup>

## Key Features

| Feature                         | What It Does                                                                            |
| ------------------------------- | --------------------------------------------------------------------------------------- |
| **Status Pages**                | Beautiful, customizable pages with your branding, custom domains, and real-time updates |
| **Uptime Monitoring**           | HTTP checks from multiple regions with automatic incident creation                      |
| **Heartbeat Monitoring**        | Track cron jobs and background tasks—know instantly when they fail                      |
| **SSL & Domain Monitoring**     | Never let a certificate expire or lose a domain again                                   |
| **Incident Management**         | Full lifecycle from creation to postmortem with subscriber notifications                |
| **Error Tracking**              | Capture frontend JavaScript errors with stack traces and user context                   |
| **Workflows**                   | Automate incident response with trigger-based actions                                   |
| **On-Call Scheduling**          | Rotation schedules with escalation policies                                             |
| **Multi-channel Notifications** | Slack, Discord, PagerDuty, email, SMS, webhooks                                         |

## Quick Examples

### Create an incident from CLI

```bash theme={null}
kodo incidents create \
  --title "Payment processing delayed" \
  --severity major \
  --service payments \
  --message "Investigating increased latency in payment processing"
```

### Auto-create incidents from monitoring

```javascript theme={null}
// Your uptime monitor fails → Workflow triggers → Incident created
{
  "trigger": "uptime.down",
  "actions": [
    { "type": "create_incident", "title": "{{monitor.name}} is down" },
    { "type": "notify", "channel": "pagerduty" }
  ]
}
```

### Track frontend errors

```javascript theme={null}
import { Beacon } from '@kodo/beacon';

Beacon.init({
  apiKey: 'your_beacon_key',
  service: 'web-app'
});

// Errors automatically captured and sent to Kodo
```

## Base URL

All API requests should be made to:

```
https://kodostatus.com/api/v1
```

## Authentication

Authenticate using the `X-API-Key` header:

```bash theme={null}
curl "https://kodostatus.com/api/v1/incidents" \
  -H "X-API-Key: your_api_key_here"
```

Get your API key from the [Dashboard](https://kodostatus.com/dashboard/api).

## What's Next?

<CardGroup cols={3}>
  <Card title="Quick Start" icon="rocket" href="/quickstart">
    Set up in 5 minutes
  </Card>

  <Card title="Status Management" icon="signal" href="/status-management/incidents">
    Learn incident workflows
  </Card>

  <Card title="Monitoring" icon="chart-line" href="/monitoring/uptime-monitors">
    Configure monitors
  </Card>
</CardGroup>