René's URL Explorer Experiment

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Person",
      "@id": "https://lastping.dev/#builder",
      "name": "Tedo Patsatsia",
      "jobTitle": "Systems engineer, DevOps",
      "url": "https://lastping.dev/about",
      "sameAs": [
        "https://ge.linkedin.com/in/tedo-patsatsia-95868723b",
        "https://github.com/tp322d",
        "https://github.com/lastping-dev"
      ],
      "knowsAbout": [
        "DevOps",
        "Heartbeat monitoring",
        "Cron job monitoring",
        "CI/CD pipeline monitoring",
        "AI agent monitoring",
        "Infrastructure as code",
        "Terraform",
        "Model Context Protocol"
      ]
    },
    {
      "@type": "Organization",
      "@id": "https://lastping.dev/#org",
      "name": "LastPing",
      "url": "https://lastping.dev/",
      "logo": "https://lastping.dev/icon-512.png",
      "description": "AI agent monitoring: alerts when your agents fail, stall or need you.",
      "email": "hello@lastping.dev",
      "founder": {
        "@id": "https://lastping.dev/#builder"
      },
      "sameAs": [
        "https://github.com/lastping-dev/lastping-app"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://lastping.dev/#website",
      "url": "https://lastping.dev/",
      "name": "LastPing",
      "publisher": {
        "@id": "https://lastping.dev/#org"
      }
    },
    {
      "@type": "SoftwareApplication",
      "@id": "https://lastping.dev/#app",
      "name": "LastPing",
      "applicationCategory": "DeveloperApplication",
      "applicationSubCategory": "Monitoring",
      "operatingSystem": "Web, Linux, macOS, Windows (any HTTP client)",
      "url": "https://lastping.dev/",
      "description": "LastPing alerts you when your AI agents fail, stall, wait for your approval or never start, and watches the cron jobs and CI/CD pipelines around them. It works with Claude Code, Codex, Cursor and any agent over MCP, and your assistant can set up its own monitoring. It also watches scheduled AI tasks and routines, n8n, Zapier and Make workflows, cron jobs, and GitHub Actions, GitLab CI and Jenkins pipelines with no YAML changes. Alerts go to Slack, email, Discord, Telegram, Microsoft Teams, Google Chat, webhooks, or your phone through ntfy or Pushover. Free for individuals.",
      "featureList": [
        "An AI agent can create and instrument its own monitor over MCP: 50 tools on a hosted server at mcp.lastping.dev, with a standalone binary at full tool parity",
        "Agent registry and fleet view: every agent's monitors, live status and last-seen in one place",
        "Agent run reporting: start, success, fail, blocked (waiting on a human), and progress steps within a run",
        "Absence detection (the dead man's switch): opens an incident when an expected check-in never arrives",
        "Silence floor (expect_every_s): catches an agent that quietly stops reporting between runs, which no cadence rule can see",
        "Run budgets for long jobs: max_runtime_s catches an overrun, and step_timeout_s catches a run that stopped making progress between stages, both opt-in, so a monitor that sets neither behaves exactly as before",
        "Output assertions: a successful run whose ping body fails a condition opens an incident; catches the job that exits zero having done nothing",
        "Metric guards: ceilings on a number a job reports about itself, for catching a runaway or looping agent before it burns cost",
        "Cron and scheduled job monitoring",
        "CI/CD pipeline monitoring via signed webhooks (GitHub Actions, GitLab CI, Jenkins): zero YAML changes",
        "Catches CI runs that fail, hang, or never start, with failure detail and a deep link to the run",
        "HTTP/uptime probing with status code, latency, and keyword checks",
        "Terraform provider for monitoring-as-code: registry.terraform.io/providers/lastping-dev/lastping",
        "Four surfaces: web console, REST API (OpenAPI), MCP, and Terraform, each carrying what you would use it for",
        "Nine alert destinations: email, Slack, Discord, Telegram, webhook, ntfy, Pushover, Microsoft Teams and Google Chat",
        "Per-destination x per-event routing matrix, with custom alert message templates and live preview",
        "Public status pages and embeddable badges",
        "Flap damping, per-channel rate limits, and a notification duration floor that keeps trivial runs quiet without ever silencing a failure",
        "Per-project Prometheus /metrics endpoint to scrape into Grafana or Alertmanager"
      ],
      "offers": {
        "@type": "Offer",
        "price": "0",
        "priceCurrency": "USD"
      },
      "author": {
        "@id": "https://lastping.dev/#builder"
      },
      "publisher": {
        "@id": "https://lastping.dev/#org"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://lastping.dev/#faq",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is LastPing?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "LastPing is AI agent monitoring: it alerts you when your AI agents fail, stall, wait for your approval or never start, and watches the cron jobs and CI/CD pipelines around them, with HTTP uptime checks alongside. Instead of polling your jobs, it waits for them to check in. If one goes silent (an agent run that stalled, a cron that never ran, a CI pipeline that hung), LastPing opens an incident and alerts you before your users notice. Your AI assistant sets the whole stack up: connect it over MCP and it creates the monitors, schedules and alert routes for you in one conversation."
          }
        },
        {
          "@type": "Question",
          "name": "Is LastPing free?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. LastPing is free for individuals at app.lastping.dev, with no monitor cap and no feature gate. Sign up with Google, GitHub or email and start monitoring immediately. Everything runs on our infrastructure; no setup required. Follow the project at github.com/lastping-dev/lastping-app."
          }
        },
        {
          "@type": "Question",
          "name": "How do I get alerted when a job goes down?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Alerts fire automatically on the very first check you create. LastPing emails the account owner by default, with no routing to configure. You can add Slack, Discord, Telegram, ntfy, Pushover, Microsoft Teams, Google Chat or a signed outbound webhook and choose which events reach which channel per check. Ask your assistant to add the channel, or add it in the console."
          }
        },
        {
          "@type": "Question",
          "name": "Does LastPing support CI/CD pipelines and HTTP uptime?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. LastPing supports three monitor types: heartbeat (cron/scheduled jobs that ping when they finish), CI/CD signals (signed webhooks from GitHub Actions, GitLab CI, Jenkins, zero YAML, deep-link to the run on alert), and HTTP/uptime probing (LastPing polls your URL on a schedule for status code, latency, and keyword presence)."
          }
        },
        {
          "@type": "Question",
          "name": "How is LastPing different from Healthchecks.io?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Healthchecks.io is an excellent heartbeat monitor for cron jobs. LastPing covers cron jobs the same way (your job curls a ping URL) and additionally treats CI/CD pipelines as first-class monitors: one signed webhook from GitHub Actions, GitLab CI, or Jenkins, no curl step in every workflow, catching runs that fail, hang, or never start, with failure detail on the incident. LastPing is free for individuals with no monitor cap. Full comparison: lastping.dev/vs/healthchecks/"
          }
        },
        {
          "@type": "Question",
          "name": "What does LastPing collect and keep?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "LastPing keeps what your jobs and agents send, each kind for a fixed time. Pings, run steps and alert delivery records are kept 90 days, agent traces 30 days, closed incidents one year, and your monitors until you delete them. Prompts, commands and tool output are not stored unless you opt in. Every period is on the privacy page."
          }
        },
        {
          "@type": "Question",
          "name": "What can my assistant do once connected?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "It can create and change monitors and alert routes, read incidents and runs, and add notes to an incident. It works only inside your LastPing project and reaches nothing outside it. You can revoke its access at any time in Settings."
          }
        },
        {
          "@type": "Question",
          "name": "What does a first setup look like?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Connect your first workload, verify a real run, and test an alert. Your assistant can do all three in one conversation, or you can follow the same steps in the console."
          }
        }
      ]
    }
  ]
}