{"id":"net.hookpulse/hookpulse","slug":"net-hookpulse-hookpulse","title":"Hookpulse","description":"Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.","version":"1.1.0","publisher":{"kind":"domain","id":"hookpulse.net","label":"hookpulse.net","url":"https://hookpulse.net"},"website":"https://hookpulse.net","repository":"https://github.com/wrpbr/hookpulse","remotes":[{"type":"streamable-http","url":"https://hookpulse.net/mcp"}],"packages":[],"published":"2026-11-10","updated":"2026-11-10","status":"online","auth":"","latency_ms":1255,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_plans","title":"List plans","description":"The plans for sale, with price and term, and the account's active plan. Each purchase lasts 30 days, with no automatic renewal. Each purchase lasts 30 days, with no automatic renewal. Without an account or wallet credential, `account` is `null`.","read_only":true},{"name":"buy_plan","title":"Buy plan","description":"Buy a plan: starter (40 more monitors, up to 50), team (90 more monitors, up to 100), business (490 more monitors, up to 500). Each purchase lasts 30 days, with no automatic renewal. Answers 402 with the price; pay with x402 or prepaid credit and repeat. Each purchase lasts 30 days, with no automatic renewal. Without payment, the answer is 402 with the price. Pay with prepaid credit (`X-Credito`) ","read_only":false},{"name":"cancel_plan","title":"Cancel plan","description":"Cancel the active plan. Nothing else is charged; a purchase under 7 days and a paid period that has not started are refunded and end now, and the rest of the paid period stays active until keeps_until. Requires accept_data_removal: true. Send `{ \"accept_data_removal\": true }`. The monthly card subscription stops. A purchase made less than 7 days ago and a paid period that has not started yet, such","read_only":false},{"name":"api_index","title":"API index","description":"Full index of the HookPulse API.","read_only":true},{"name":"health","title":"Health","description":"Read service liveness before using HookPulse. Returns the health response; does not check a monitor.","read_only":true},{"name":"create_guest","title":"Create guest","description":"Creates a guest token hp_… Keep the token: without it there is no way back to the monitors, unless you have already tied them to an e-mail.","read_only":false},{"name":"list_endpoints","title":"List endpoints","description":"Lists the guest's/session's endpoints.","read_only":true},{"name":"create_endpoint","title":"Create endpoint","description":"Create a monitor for a routine. Use cron, tz and grace_sec for a schedule, or interval_sec for a fixed check-in interval. Set max_duration_sec to detect an open run that exceeds its time limit. Without an owner token, creation returns guest_token; keep it private for later calls. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and se","read_only":false},{"name":"create_site","title":"Create site","description":"Monitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Without an owner token, creation returns guest_token; keep it private. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in","read_only":false},{"name":"check_site","title":"Check site","description":"Check a site monitor now. One call every 10 seconds per destination host. One call every 10 seconds per destination host, for everyone: the button cannot hammer a site. The first state of a new site comes from here, without an alert — you are looking at it. After that, the state and the alerts come from the check that runs every minute.","read_only":false},{"name":"list_sites","title":"List sites","description":"The state of every site you monitor (up, down, waiting, paused), with the last check. The same answer is the snapshot of the live subscription (`/api/realtime/`): after it, every check arrives as an event, so a screen never has to poll.","read_only":true},{"name":"import_crontab","title":"Import crontab","description":"Reads a crontab and proposes one monitor per scheduled line. Without apply=1 nothing is written; the proposal says what was ignored and why. Passwords in the command are redacted. The body is the crontab itself, as `text/plain`. Without `?apply=1` **nothing is written**: you get the proposal — what would become a monitor, what was ignored and why, and what still fits in the free tier. With `apply=","read_only":false},{"name":"get_endpoint","title":"Get endpoint","description":"Status of one endpoint (use the endpoint token if you have it). The monitor token only reads: it lets you put the state on a third-party dashboard without handing over the owner's credential. With a schedule it is here that `next_expected_at` says when the next run is due. Only this endpoint carries `duration`: `p50_ms` (the low median, so always a duration that really happened) and `max_ms` over ","read_only":true},{"name":"delete_endpoint","title":"Delete endpoint","description":"Removes the owner's endpoint.","read_only":false},{"name":"list_events","title":"List events","description":"Latest ingest pings.","read_only":true},{"name":"ping_ingest","title":"Ping ingest","description":"Simulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret. It costs nothing and there is no quota per ping.","read_only":true},{"name":"signal_start","title":"Signal start","description":"Says the run STARTED. Does not clear the dead-man clock: a routine that starts and hangs still becomes a miss. The next success records the duration. `start` is not proof of life: it does not move `last_event_at` and does not clear the miss counter, so a routine that starts and hangs still becomes a miss at the right time. The next success closes the run and records `last_duration_ms` — pass `?rid","read_only":true},{"name":"signal_fail","title":"Signal fail","description":"Record a failed run. The next five-minute check sends the alert with reason fail. The monitor's alert_repeat_sec controls repeated alerts; the default is 24 hours. Failing is not proof of life either: the clock keeps running. The ingest never sends e-mail and never calls out — it records `alert_pending` and the cron turns it into an alert with `reason: \"fail\"` within 5 minutes, under the same one-","read_only":true},{"name":"signal_exit_code","title":"Signal exit code","description":"The shell exit status: 0 behaves like a ping, 1-255 record the code as a failure. `curl -fsS $ORIGIN/in/ID/$?` at the end of a script is the whole integration. `0` behaves exactly like a plain ping; 1 to 255 record the code and leave the failure for the cron.","read_only":true},{"name":"ingest_key","title":"Ingest key","description":"Returns (minting the first time) the key for /in/<key>/<slug>, where a ping creates its own monitor inside the free tier. Instruments a whole fleet with no setup call per job. One key per owner. Point a whole fleet at `/in/<key>/<slug>` and each job creates its monitor on the first check-in, **inside the free tier** — beyond it the ping answers 402 without creating anything. The key survives signi","read_only":true},{"name":"ingest_key_rotate","title":"Ingest key rotate","description":"Rotates the ingest key; the previous one stops creating monitors. Existing ones keep working. Monitors already created keep working — rotating only revokes the power to create new ones.","read_only":false},{"name":"ping_slug","title":"Ping slug","description":"Create a monitor on its first check-in. The same slug uses the same monitor. Service and billing limits apply. A rejected creation writes no monitor or event. The slug becomes the monitor name and its identity: the same slug always means the same monitor, so a retry never creates a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Creation happens **only inside the free tier** (or the tr","read_only":true},{"name":"signal_slug","title":"Signal slug","description":"Send start, fail or an exit code by name, with the ingest key; the first signal of a new name creates its monitor. The same signals as `/in/:id/start`, `/in/:id/fail` and `/in/:id/:exit_code`, for a fleet that only knows the ingest key: the job sends its name, not the monitor id. The first signal of a new name creates the monitor, with the same rules and the same `cron`, `tz` and `grace_sec` as th","read_only":true},{"name":"pricing","title":"Pricing","description":"Read current free allowances, options with billing off, prices and the account's 7-day trial. E-mail alerts cost $0.10 once per additional monitor, even with a reused address. Check before creating the second monitor or lowering the interval: it is the number IN FORCE, not the documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was ","read_only":true},{"name":"status_feed_url","title":"Status feed URL","description":"Public URL (JSON and RSS) with the status of all the owner's endpoints. The feed token only reads status: it does not create, change or delete. Whoever has the link sees the dashboard — treat it as a secret.","read_only":true},{"name":"status_feed_rotate","title":"Status feed rotate","description":"Rotates the status feed token; the previous URL stops working.","read_only":false},{"name":"list_templates","title":"List templates","description":"Ingest snippets and the JSON HookPulse POSTs on a miss. It exists so nobody guesses the alert format: `miss_json` and `recovery_json` here are the same bodies that arrive at your `alert_url`. Slack and Discord receive only the field they read.","read_only":true},{"name":"contact","title":"Contact","description":"Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. Free, no captcha and no payment; one message every 10 s per network (one that arrives sooner waits its turn). One route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`). No captcha, no account, no payment. One message every 10 s","read_only":false},{"name":"get_api_x402_check","title":"Get API X402 check","description":"Checks a URL once for an agent, paid per call: status, response time, keyword and TLS certificate, with no account and no monitor.\nOne reading with the probe of the site monitors, and the certificate of an https address that answered. A request without payment gets the 402 with the price; a paid one gets the reading in the same response, with the payment in `cobranca`. A site that is down is the a","read_only":false}],"server_info":{"name":"HookPulse","version":"0b8d298a"},"category":"cloud","tags":["hr","crypto","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-05","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/net-hookpulse-hookpulse/"}