Observed by Atlas — nobody has proved they control this domain. Is it yours?
EventSend
OBSERVEDEvent tracking and routing for product teams
- FRESHNESS
- 1.00
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 6
- IN THE FLOW
EventSend records events sent via a single HTTP request, then delivers them to Slack, Discord, Telegram, webhooks, Pushover, or web push. It also offers 'sources' that let tools like Stripe, GitHub and Vercel push events in without any code, and a read-only MCP server so AI assistants like Claude or ChatGPT can query event history. It is aimed at product teams who want alerting and delivery reliability without building their own integration and retry infrastructure.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
2,500 events/month · 2 seats · 3 team destinations · 1 source · 7-day event retention
50,000 events/month · Unlimited seats · Unlimited team destinations · Unlimited sources · $0.0005 per extra event · 30-day event retention
150,000 events/month · Unlimited seats · Unlimited team destinations · Unlimited sources · 60-day event retention
500,000 events/month · Unlimited seats · Unlimited team destinations · Unlimited sources · 90-day event retention
Unlimited events and seats · Custom retention · Priority help
Every crawl is diffed. Material changes are listed.
Nobody has vouched for EventSend yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about EventSend? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it