# PulseWatch Status API
> Is this vendor down? Pay-per-call current status and recent incidents for 1,700+ SaaS/cloud vendors, read live from PulseWatch (pulsewatch.us).

Payments: x402 v2, scheme "exact", USDC on Base mainnet (eip155:8453), asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0x2dAF658B01e257206375798a15832E9f547D65dD. No accounts or API keys.
Flow: call the paid URL -> HTTP 402 with a base64 JSON PAYMENT-REQUIRED header -> sign an EIP-3009 USDC authorization for one of `accepts` -> retry with PAYMENT-SIGNATURE -> 200 + PAYMENT-RESPONSE (settlement receipt). Invalid input returns 400 and is never charged; upstream failures return 5xx and are not settled.
Client libraries: @x402/fetch (wrapFetchWithPayment), @x402/axios, or any x402 v2 client.

## Paid endpoints
- [GET /v1/status](https://api.pulsewatch.us/v1/status) $0.01: Current outage status for a vendor (PulseWatch). Current status, active-incident summary, last-checked time and source URL for one vendor, read live from PulseWatch. Includes data_source, checked_at and freshness fields. Unknown vendors return 404 and are not charged. Query: `vendor`. Example: https://api.pulsewatch.us/v1/status?vendor=stripe.com
- [GET /v1/incidents](https://api.pulsewatch.us/v1/incidents) $0.01: Recent incidents for a vendor (PulseWatch). Up to 10 most recent incidents (title, status, severity, start/resolve times) for one vendor from PulseWatch. Unknown vendors return 404 and are not charged. Query: `vendor`. Example: https://api.pulsewatch.us/v1/incidents?vendor=stripe

## Free endpoints
- GET https://api.pulsewatch.us/v1/vendors?search=&page=: list/search tracked vendors (slugs)
- GET https://api.pulsewatch.us/v1/validate?vendor=: check a vendor name/domain format before paying

## Discovery
- OpenAPI: https://api.pulsewatch.us/openapi.json
- x402 manifest: https://api.pulsewatch.us/.well-known/x402
- API catalog (RFC 9727): https://api.pulsewatch.us/.well-known/api-catalog
- Sitemap: https://api.pulsewatch.us/sitemap.xml

## Honesty
Statuses are PulseWatch's own conclusions, not the vendor's. 'unknown' or 'not_monitored_sufficiently' means PulseWatch lacks current evidence. Every response has data_source, checked_at and freshness (last_checked_at age, stale flag, data_fetched_at). Unknown vendors return 404 and are not charged.