# ai.txt tells AI crawlers how to use Bleepit content.
# Source: https://bleepit.io/

website: https://bleepit.io/
landing-page-summary: Bleepit receives a single HTTPS POST from every run so you can watch schedules, declare heartbeats UP/LATE/DOWN, and store each JSON log entry to search or forward anywhere.

# Core value
Bleepit gives SRE, DevOps, and platform teams one endpoint that handles JSON ingest, heartbeats, alerting, and fan-out.

# How it works
1. Create a monitor, name it, and toggle a schedule whenever you want uptime checks. Cron syntax is validated, plan minimums are respected, and next due stays in your timezone.
2. Send JSON from any language to /b/<bleep-id> with top-level primitives (≤16 KB). When a schedule is enabled you can send light heartbeats like {"heartbeat":"alive"}; pure heartbeats never consume monthly log quota.
3. See events instantly, subscribe channels to DOWN/UP, and add payload-match forwarding rules to fan out matches to Slack, Teams, or any HTTPS webhook.

# Capabilities
- Searchable event feed with stable keyset pagination, filters for status, event type, IP, or whitelisted payload keys, plus CSV export for bounded ranges.
- Heartbeats with honest status that compute UP, LATE, and DOWN from your schedule while anchoring uptime after the first successful run.
- Alerts where your team works by routing DOWN (and optional UP) to Email, Slack, Teams, or webhooks with per-channel cooldowns.
- Built-in reports that surface heartbeat uptime, lowest uptime, outage summaries, and ingestion trends without extra setup.
- Payload forwarding rules that match JSON with ANDed conditions (eq, neq, gt, lt, contains, not_contains) and fan-out to chat tools or webhooks with cooldown windows.

# Integrations
Use any tool that can POST JSON—cURL, fetch, requests, and PowerShell are all supported. Forward events to Slack, Teams, or generic HTTPS webhooks.

# Documentation
Docs: https://bleepit.io/docs
Support: https://bleepit.io/support
Pricing: https://bleepit.io/pricing