# PulsAPI
# Service count for marketing copy: keep aligned with frontend/lib/constants/catalog.ts (PULSEBOARD_CATALOG_SERVICE_COUNT_PLUS) and services.json _meta.totalServices.
> Cloud service status monitoring for engineering teams.

PulsAPI pulls live status, incident timelines, and 90-day SLA data from 2463+ cloud providers into one dashboard. Teams use it to catch third-party outages early, check vendor SLA compliance, and route alerts to Slack, Discord, Microsoft Teams, and PagerDuty.

Founded October 2025. Status pages are polled every 60 seconds; alerts typically land in under 4 seconds.

## Key Facts
- Monitors 2463+ cloud services across 14 browsable categories (Cloud Infrastructure, Developer Tools, AI & Machine Learning, Payments & Fintech, Communication & Messaging, Databases & Data, Observability, Security, Identity & Access, CDN & Edge, Analytics, Marketing, Media & Streaming, SaaS & Business Apps)
- Real-time status with under 4-second alert latency
- Status pages polled every 60 seconds
- Component-level granularity: track individual service components and regions (e.g., AWS S3 in us-east-1, Lambda in eu-west-2)
- 90-day SLA metrics: uptime percentage, MTTR (Mean Time to Recovery), incident frequency
- Alert integrations: Slack, Discord, Microsoft Teams, PagerDuty, outbound webhooks, email
- Smart alert routing: route by service, severity, and custom conditions
- Alert rules engine: thresholds, status transitions, consecutive failures, flap detection, escalation policies
- Maintenance windows to suppress alert noise during planned work
- Custom dashboard groups to organise services by project, team, or infrastructure layer
- Team collaboration with role-based access control (Owner, Admin, Member)
- Enterprise features: SSO/SAML (Okta, Entra ID, Google Workspace), audit logs, custom SLA targets, 99.99% platform SLA guarantee
## Pricing
- Starter: Free forever, up to 25 services, Slack and email alerts, 7-day incident history, 3 viewer seats. Every new account starts with a 30-day Business trial (full features, no credit card)
- Pro: $29/month ($23/month billed yearly), unlimited services, Discord/MS Teams/Google Chat integrations, configurable alert rules, 90-day SLA reporting, MTTR, SLA export (CSV/PDF), downtime budget tracking, P50/P95/P99 latency, up to 50 viewer seats and up to 5 admin seats
- Business: $99/month ($79/month billed yearly), everything in Pro plus PagerDuty, Opsgenie, custom alert routing, SSO/SAML, RBAC, audit logs, up to 5 workspaces, up to 15 admin seats, priority support
- Enterprise: Custom pricing, everything in Business plus dedicated account manager, custom integrations, compliance support, tailored API rate limits, 99.99% platform SLA guarantee, onboarding help

## Use Cases
- DevOps and SRE teams needing instant visibility into third-party outages affecting production
- Engineering managers wanting a clear picture of upstream reliability without tab-hopping
- Platform teams building internal status dashboards for their organisation
- On-call engineers needing consolidated alerts when vendor services degrade
- Enterprise security teams requiring SSO and audit logs for compliance (SOC 2, ISO 27001)

## Differentiators vs. Checking Status Pages Directly
- Single dashboard replacing 30-50 individual status page bookmarks
- Unified alert routing: one configuration, all channels
- 90-day historical SLA data with MTTR calculations, not just current status
- Component-level granularity (e.g., "AWS S3 us-east-1 is degraded" not just "AWS has issues")
- Alert latency under 4 seconds from detection to delivery

## Authors / Team
- James Okafor, Co-founder and CTO
- Marcus Webb, Head of Product
- Sofia Andrade, Senior Infrastructure Engineer
- Lena Hoffmann, Enterprise Security Lead

## Links
- Homepage: https://www.pulsapi.com
- Pricing: https://www.pulsapi.com/pricing
- Documentation: https://www.pulsapi.com/docs
- Developer hub (API, OpenAPI, MCP, CLI): https://www.pulsapi.com/developers
- About PulsAPI: https://www.pulsapi.com/about
- Contact PulsAPI: https://www.pulsapi.com/contact
- Blog: https://www.pulsapi.com/blog
- Changelog: https://www.pulsapi.com/changelog
- Service Directory: https://www.pulsapi.com/directory
- Support: https://www.pulsapi.com/support
- Sign up (free): https://www.pulsapi.com/signup

## Developer Resources
Named surfaces, at predictable URLs. Status reads need no account and no API key.
- PulsAPI Developer Hub: https://www.pulsapi.com/developers
- PulsAPI OpenAPI 3.1 specification (JSON): https://www.pulsapi.com/openapi.json
- PulsAPI OpenAPI 3.1 specification (YAML): https://www.pulsapi.com/openapi.yaml
- PulsAPI MCP server (JSON-RPC 2.0, Streamable HTTP): https://www.pulsapi.com/api/mcp
- PulsAPI MCP manifest: https://www.pulsapi.com/.well-known/mcp.json
- PulsAPI MCP server card (SEP-2127): https://www.pulsapi.com/.well-known/mcp/server-card.json
- PulsAPI API catalog (RFC 9727): https://www.pulsapi.com/.well-known/api-catalog
- PulsAPI CLI: package @pulsapi/cli, install with `npm install -g @pulsapi/cli`; docs at https://www.pulsapi.com/developers
- PulsAPI API key documentation: https://www.pulsapi.com/docs/settings/api-keys
- PulsAPI API health probe: https://www.pulsapi.com/api/health
- PulsAPI sitemap: https://www.pulsapi.com/sitemap.xml
- This file: https://www.pulsapi.com/llms.txt
- Agent brief: https://www.pulsapi.com/AGENTS.md

## API Quick Reference
Base URL https://www.pulsapi.com/api. JSON responses, ISO 8601 UTC timestamps, page envelopes.
- GET /api/services - paged catalog with current status and 30-day uptime (operationId listServices)
- GET /api/services/{slug} - one vendor with components and open incidents (getService)
- GET /api/services/{slug}/history - worst status per day, up to 90 days (getServiceHistory)
- GET /api/services/{slug}/uptime - 7/30/90-day uptime and MTTR (getServiceUptime)
- GET /api/services/status-counts - catalog histogram by status (getServiceStatusCounts)
- GET /api/incidents - cross-vendor incident feed (listIncidents)
- GET /api/status/providers-overview - one aggregate row per provider (getProvidersOverview)
- GET /api/user/services/{slug}/sla - SLA report, needs an API key with sla:read (getServiceSlaReport)
- POST /api/mcp - MCP server, JSON-RPC 2.0 over Streamable HTTP (callMcpServer)

## API Key Scopes
Keys are created in Settings > API Keys and carry an explicit scope list. An operation refuses a key
that lacks its scope with HTTP 403 and names the scope it wanted. Request the narrowest set.
- status:read - public service, provider, and component status, uptime, and history
- incidents:read - incident timelines, catalog-wide and per service
- sla:read - SLA reports, uptime percentages, MTTR, latency percentiles, breach history
- monitors:read / monitors:write - monitors, boards, groups, and subscriptions
- alerts:read / alerts:write - alert rules, routes, escalation policies, delivered events
- account:read - account profile, plan, seats, API-key metadata
- mcp:invoke - call the MCP server at /api/mcp

## MCP Tools
Anonymous callers may use the first four under a per-IP budget; get_uptime_report needs a plan with
MCP access and a key holding mcp:invoke.
- list_services - list monitored services with current status, filterable by category and status
- get_service_status - current status and details for one service by slug
- list_incidents - active or recent incidents across all monitored services
- get_component_status - status of the components inside a service, such as a region or subsystem
- get_uptime_report - uptime statistics and SLA compliance over a time range

## Browse by Category
Each page lists the monitored vendors in that category with live status and 30-day uptime.
- Cloud Infrastructure: https://www.pulsapi.com/directory/cloud
- Developer Tools: https://www.pulsapi.com/directory/devtools
- AI & Machine Learning: https://www.pulsapi.com/directory/ai-ml
- Payments & Fintech: https://www.pulsapi.com/directory/payments
- Communication & Messaging: https://www.pulsapi.com/directory/communication
- Databases & Data: https://www.pulsapi.com/directory/database
- Observability: https://www.pulsapi.com/directory/monitoring
- Security: https://www.pulsapi.com/directory/security
- Identity & Access: https://www.pulsapi.com/directory/identity
- CDN & Edge: https://www.pulsapi.com/directory/cdn
- Analytics: https://www.pulsapi.com/directory/analytics
- Marketing: https://www.pulsapi.com/directory/marketing
- Media & Streaming: https://www.pulsapi.com/directory/media
- SaaS & Business Apps: https://www.pulsapi.com/directory/saas

## Featured Engineering Guides
- Observability vs Monitoring (2026): https://www.pulsapi.com/blog/observability-vs-monitoring-explained
- OpenTelemetry Getting Started: https://www.pulsapi.com/blog/opentelemetry-getting-started-guide
- Distributed Tracing Best Practices: https://www.pulsapi.com/blog/distributed-tracing-best-practices
- Chaos Engineering Introduction: https://www.pulsapi.com/blog/chaos-engineering-introduction
- Kubernetes Cluster Monitoring Guide: https://www.pulsapi.com/blog/kubernetes-cluster-monitoring-guide
- Serverless Monitoring (AWS Lambda): https://www.pulsapi.com/blog/serverless-monitoring-aws-lambda
- GraphQL API Monitoring Guide: https://www.pulsapi.com/blog/graphql-api-monitoring-guide
- Microservices Monitoring Strategy: https://www.pulsapi.com/blog/microservices-monitoring-strategy
- AI API Reliability Monitoring: https://www.pulsapi.com/blog/ai-api-reliability-monitoring
- Edge & CDN Uptime Monitoring: https://www.pulsapi.com/blog/edge-cdn-uptime-monitoring

## Contact
- General: hello@pulsapi.com
- Sales: sales@pulsapi.com
- Support: support@pulsapi.com
- Privacy: privacy@pulsapi.com
- Twitter/X: @pulsapi