// docs

Get from a URL toa verified alert path.

The shortest path is the default. Deeper integrations, API access, and MCP stay available when you need them.

Documentation sections

guides

Practical guides

What to watch on Stripe, Supabase and Lambda, getting a real alert to your phone, and the failures that return HTTP 200.

quickstart

Start with HTTP

Create an account, paste one production URL, wait for the first signal, then send a test alert.

connections

Integration guides

Setup for all 14 connectable providers, each with what Beaam alerts on.

detection

How alerts work

Repeated evidence, hysteresis, correlation, delivery, acknowledgement, and recovery.

trust

Security and architecture

Isolation, credential handling, outbound safety, and watchdog independence.

api

API reference

Every operation, generated from the live capability manifest — one endpoint, one auth header, one response envelope. Create an API key in Settings.

mcp

Remote MCP connector

Connect a compatible assistant over an OAuth-protected endpoint and ask about your stack in plain language. Billing and admin operations are never exposed.

bring your own

OpenTelemetry

Already exporting OTLP? Point it at Beaam and let it decide what needs your attention — no new agent to adopt.

reference

API conventions

The response envelope, error shape, and authentication rules every capability follows.

Need a hand?

Free support is best-effort with a one-business-day response target. Solo receives priority support; Beaam does not promise a staffed 24/7 support desk.

Email support