Documentation
SignalSitter documentation
Never let critical work fall through the cracks again. SignalSitter watches your scheduled jobs, pipelines and services, and tells you when one goes quiet or a number crosses a limit you set, so you or your agent can fix it before your customers notice.
Use a coding agent
Let your agent add SignalSitter to your code and run it for you, through the REST API or MCP.
- AgentsPick how your agent connects and give it the docs.
- REST APIYour agent calls the API directly.
- MCPConnect an MCP client with a scoped credential.
Read https://docs.signalsitter.com/llms-full.txt, then add a SignalSitter heartbeat to the end of my nightly backup job.Integrate directly
Send a heartbeat from any job or app with one HTTP request.
- Publish your first heartbeatFrom zero to a watched job in a few minutes.
- Publishing heartbeatsCadence, measurements and limits.
- REST APIManage monitors, incidents and alerts from code.
- API referenceEvery operation, with its request and response.
curl --request POST \ --url https://ingest.signalsitter.com/nightly-backup \ --header "Authorization: Bearer ${SIGNALSITTER_PUBLISH_CREDENTIAL}"Use the dashboard
Prefer clicking to coding? Do everything in the dashboard.
- Get startedSign in and create your first monitor.
- MonitorsStatus, history and settings.
- Alerts and notificationsChoose where alerts go.
Plans and support
Section titled “Plans and support”See plans and limits. Questions? Email support@signalsitter.com. Read the Privacy Statement and Terms of Service.
For agents
Section titled “For agents”llms.txt indexes these docs; llms-full.txt has every page as Markdown in one file. The full API description is openapi.json.
SignalSitter documentation