Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Changed the definition of "billing", "create_endpoint", "ping_slug" and 1 more
Free plan, x402Readpricescurrentandfreetheallowances,trialoptionsoffer:withanbillingaccountoff,=prices90anddaysthewithoutaccount'sthe90-dayusageperiod.paywall,E-mailcountedalertsfromcostits$0.10firstonceuseperhereadditional(`trial`monitor,field;even with asession it shows thereusedstate).address. Check before creating the second monitor or lowering ⟨11 unchanged words⟩
CreatesCreate adead-manmonitorendpoint.forUseacron+tz+grace_secroutine.forUseacron,realtzscheduleand(mutuallygrace_secexclusiveforwithainterval_sec)schedule, or interval_sec for
Ping that creates itsCreateowna monitor ontheits firsthit.check-in.SameThe same slug=uses the samemonitor;monitor.402Servicewhenandthebillingfreelimitstierapply.is
SaysRecordthearunfailedFAILED.run. Theingestnextneverfive-minutesendschecke-mail:sends the5-minute cronalertturnswithitreasonintofail.anThealert
Changed the definition of "list_input_fleet"
⟨58 unchanged words⟩ get the same data here without the socket. A failed input-central request or an invalid fleet response returns 503 inputs_unavailable, never a successful empty fleet. Fleet reads give the input-central exchange, including its response body, a 750 ms deadline. The optional time-series query has a 400 ms deadline; when it is unavailable or too slow, channels are preserved with stats null. An authenticated owner with no channels still gets an empty list.
Changed the definition of "api_index", "billing", "contact" and 38 more
before
—after
API indexbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"API index"}before
—Billing
Certificate changed, valid to 2026-12-22
Recently observed → Live
Added "create_collection", "create_device_input", "create_environment" and 16 more; changed the definition of "billing", "contact", "create_endpoint" and 12 more (22 tools before, 41 now)
Free plan, x402 prices and the trial offer:sign-up with a confirmedan
Support.
Live → Recently observed
Certificate changed, valid to 2026-12-14
Added "pricing" (21 tools before, 22 now)
Current public prices and free allowances; no charge.
Certificate recorded, valid to 2026-11-08
Authorization not required
First tool surface recorded: 21 tools (server version 1d82a4fa)
Showing the latest 12 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
before
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Billing"}before
—after
Contactbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Contact"}before
—after
Create collectionbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Create collection"}before
—after
Create device inputbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Create device input"}before
—after
Create endpointbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Create endpoint"}before
—after
Create environmentbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Create environment"}before
—after
Create guestbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Create guest"}before
—after
Delete collectionbefore
—after
{"destructiveHint":true,"idempotentHint":true,"readOnlyHint":false,"title":"Delete collection"}before
—after
Delete device inputbefore
—after
{"destructiveHint":true,"idempotentHint":true,"readOnlyHint":false,"title":"Delete device input"}before
—after
Delete endpointbefore
—after
{"destructiveHint":true,"idempotentHint":true,"readOnlyHint":false,"title":"Delete endpoint"}before
—after
Delete environmentbefore
—after
{"destructiveHint":true,"idempotentHint":true,"readOnlyHint":false,"title":"Delete environment"}before
—after
Get collection seriesbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Get collection series"}before
—after
Get device input batchbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Get device input batch"}before
—after
Get device input setupbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Get device input setup"}before
—after
Get endpointbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Get endpoint"}before
—after
Get environmentbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Get environment"}before
—after
Healthbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Health"}before
—after
Import crontabbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Import crontab"}before
—after
Ingest keybefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Ingest key"}before
—after
Ingest key rotatebefore
—after
{"destructiveHint":true,"idempotentHint":true,"readOnlyHint":false,"title":"Ingest key rotate"}before
—after
List collectionsbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List collections"}before
—after
List device input historybefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List device input history"}before
—after
List device inputsbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List device inputs"}before
—after
List endpointsbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List endpoints"}before
—after
List environmentsbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List environments"}before
—after
List eventsbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List events"}before
—after
List input fleetbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List input fleet"}before
—after
List templatesbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"List templates"}before
—after
Ping ingestbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Ping ingest"}before
—after
Ping slugbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Ping slug"}before
—after
Pricingbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Pricing"}before
—after
Report environmentbefore
—after
{"destructiveHint":false,"idempotentHint":false,"readOnlyHint":false,"title":"Report environment"}before
—after
Set device input activebefore
—after
{"destructiveHint":true,"idempotentHint":false,"readOnlyHint":false,"title":"Set device input active"}before
—after
Signal exit codebefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Signal exit code"}before
—after
Signal failbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Signal fail"}before
—after
Signal startbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Signal start"}before
—after
Status feed rotatebefore
—after
{"destructiveHint":true,"idempotentHint":true,"readOnlyHint":false,"title":"Status feed rotate"}before
—after
Status feed URLbefore
—after
{"destructiveHint":false,"idempotentHint":true,"readOnlyHint":true,"title":"Status feed URL"}before
—after
Update collectionbefore
—after
{"destructiveHint":true,"idempotentHint":false,"readOnlyHint":false,"title":"Update collection"}before
—after
Update environmentbefore
—after
{"destructiveHint":true,"idempotentHint":false,"readOnlyHint":false,"title":"Update environment"}⟨32 unchanged words⟩ 402 x402 when it leaves the free tier. This response is the only one that shows the monitor's `token` and the `templates` — keep them. The second monitor, or an interval below the free minimum, answers **402 with `accepts[]`**: pay and repeat. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is late at 03:01:30, not 24 hours later. `max_duration_sec` catches the other failure: a run that starts and hangs, which plain silence detection only notices at the next scheduled time.
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.⟨5 unchanged words⟩ 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 the last runs we measured, computed at read time over the event window we already keep — the list does not pay for it.
⟨21 unchanged words⟩ 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=1` it is all or nothing, under the same rules as `POST /api/endpoints`. Comments, variables and `@reboot` are ignored (there is no way to know when to expect a reboot); `@daily` and friends become the equivalent expression. The command becomes the monitor name, with passwords and tokens redacted first — the name travels in the alert e-mail, in the public dashboard and in the badge.
⟨22 unchanged words⟩ 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 signing in: the crontab you deployed keeps working.
⟨6 unchanged words⟩ one stops creating monitors. Existing ones keep working. Monitors already created keep working — rotating only revokes the power to create new ones.
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.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.⟨19 unchanged words⟩ tier is full, and then nothing is written. 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 trial); past it the ping is a 402 with `accepts[]` and nothing is written — not even the event. Works by GET or POST.
⟨8 unchanged words⟩ 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.
⟨17 unchanged words⟩ with reason `fail`, under the same one-per-24h cap. 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-per-24h cap. Works by GET or POST.
⟨18 unchanged words⟩ 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=` on both ends when runs can overlap, or the duration is measured against the wrong start. With `max_duration_sec` set on the monitor, a run left open past that ceiling alerts with `reason: "too_long"` on the next 5-minute check. Works by GET or POST.
⟨5 unchanged words⟩ 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.
Adds compatible measurements to a previously detected device. First create /api/ambientes and submit its environment report. Reference that ambiente_id here; its saved name and group are authoritative. Same device+measurement returns the existing stream instead of duplicating it. A profile adds only compatible measurements. Up to 200 collections per owner. The signed collection id writes only its own measurement stream.
Create or rotate an authenticated collector channel for this device. Ownership is checked before the app asks the input central. The server chooses the channel id and authenticates batches only against a hash of the collector credential. The whole setup this call returns — credential included — is also saved, encrypted with a key only the input central holds and bound to that credential, so the owner can read it again with GET /api/ambientes/:id/inputs/:collector/setup. The credential does not expire: a device that stays off for weeks reconnects with it. It stops working only when a new confi…
Register a device UUID before discovery and collector selection. Registers one device (maximum 25 per owner), creating a guest if needed. The UUID is the one-hour discovery capability; it is not a telemetry credential. Choose passos.posix or passos.powershell for the TARGET terminal. The checks only display allowlisted system facts and install nothing.
Removes one measurement and frees that slot on the device. What disappears is the OWNERSHIP: your list, the authority to read that series, and the unique slot that measurement holds on that environment — so you can add it again later. Readings already stored at the ingest origin stay there until their own retention. The machine keeps sending: the symbol is signed and stands on its own there, which is why the answer carries `remover`, the command that takes the line out of the crontab. Use `ativa:false` instead when you only want to stop looking.
Revokes and removes one collector channel from a device. The input central removes only a channel of the same owner. This stops new authenticated input and removes the channel from the device list — also for a channel whose device was already deleted. It does not uninstall or stop the collector on the device (`uninstall.remove` in GET /api/ambientes/:id/inputs is the command for that), and stored measurements remain subject to their retention policy.
Removes a device and every measurement on it, in one call. One call, not one per measurement — the same reason `GET /api/coletas/serie` exists. What goes away is the ownership: your list, the authority to read those series, and the slots those measurements held, so the device can be registered again. Readings already stored at the ingest origin stay there until their own retention, and the machine keeps sending: the symbols are signed and stand on their own there. That is why the answer carries `remover`, one command per measurement that had a cron line. The device's collector channels are re…
The latest readings of one device, for the screen that draws it. Authorised by YOUR session, never by the symbol in the crontab. A device that is not yours answers 404 exactly like one that does not exist — telling the two apart would confirm to a stranger that the id exists — 401 is only for sending no credential at all, which tells the caller what they already know. When the ingest origin cannot be read the answer is 503, not an empty series: a screen must say "I could not read now", never let you believe your machine stopped. Readings are reused for up to 60 seconds. Poll no faster than on…
One received batch, decoded: its series with labels and values, or its NCPA checks. Remote Write (1.0 and 2.0), OTLP (protobuf or JSON) and NRDP become the same shape: `series` (`name`, `labels`, `points` as `[milliseconds, value]`, and `type`/`unit`/`help` when the collector sent them; OTLP points also carry `resource`, an index into `resources`) or `checks` for NCPA (`host`, `service`, `state` 0–3, `output`, `perfdata`). A value JSON cannot hold comes as a string: `"NaN"`, `"+Inf"`, `"-Inf"` or `"stale"`. Very large batches keep the first 5,000 series (`truncated`). `newer`/`older` are the …
The saved setup of one collector channel: the configuration in use, its files and steps. Returns the setup generated last for this channel — the one whose credential is accepted now — exactly as POST /api/ambientes/:id/inputs returned it, so the files can be copied or installed again without rotating the credential. It carries the credential: only the device owner gets it, one channel per request, never cached; list routes never include it. 404 `setup_not_saved` when the channel was generated before setups were saved, or was removed; 409 `setup_unreadable` when the input central can no longer…
Read the detected environment and compatible measurements.
Lists your measurements with commands adapted to each saved device environment. Two views of the same thing: `coletas` is one entry per measurement, `equipamentos` is one per machine with a SINGLE command that does all of its measurements and a SINGLE cron line. Use the device one unless you really want a single measurement on its own. Commands are generated only from a detected environment. Legacy collections without one keep their readings, but comandos.agora/agenda are null until a compatible environment is provided. Curl, wget and Python 3 follow the detected capabilities; Windows disk us…
The batches this collector sent, newest first — filtered and paginated on the server. Every batch the input central received for this channel, as it arrived: when, the protocol, the result (`stored`; `rejected` by the receiver, with the reason; or `discarded` while the channel was paused, when its data is not kept), the answer given to the collector, the size, and how many series and samples it carried. The central keeps the newest batches of each channel up to the limits in `limits` (count, bytes and days); older ones leave as new ones arrive, and removing the channel deletes them. `q` searc…
List this device's collector channels, their state and their live numbers.
Saved environments owned by the current account or guest; empty without a session.
Every collector channel of the caller, with state and live numbers, in one response. One call for the whole fleet — one query to the time-series store for all channels, never one per device. It is the same function the dashboard subscribes to over the socket (`/api/inputs/serie`), where the input central then pushes `inputs.updated` and `inputs.removed` events; integrators get the same data here without the socket.
Preview or save the allowlisted discovery report for one device. Send terminal and saidas (step id to pasted output), initially with conferir:true. Preview returns normalized dados, additional passos and pronto without writing. Omit conferir to save when complete. Only allowlisted facts are saved, never raw commands. First report wins within one hour; identical retries do not rewrite. The discovery never creates a legacy measurement, sends a reading, installs software or creates a schedule. With Accept: text/plain the receipt is only `ok`.
Pauses or resumes one collector channel. Pausing keeps the channel, its credential and its configuration: batches the collector sends while paused are accepted and discarded, so nothing is stored or measured and the collector does not retry in a loop. Resuming stores the next batch again. The input central changes only a channel of the same owner, including one whose device was already deleted.
Renames one measurement, or stops and resumes reading it. The id never changes: it is the write symbol already sitting in a crontab, and renaming on a screen must not send anyone back to the machine to edit a line. Send only what you are changing; anything omitted stays as it is. `ativa:false` takes the measurement out of the fleet read — it keeps its history and its commands, stops costing a query, and comes back with `ativa:true`. It does NOT silence the machine: the symbol is signed and stands on its own at the ingest origin, so a device keeps sending until you remove its cron line. The an…
Renames a device, and its measurements along with it. One machine has one name. The measurements carry a copy of it, so renaming here renames them too — leaving the old name on them would show the same machine twice in a list that groups by device. Its collector channels take the new name and group too in `GET /api/coletas` (`inputs[]`), and the group decides which dashboard tab the device is under. Send only what changes; what you omit stays. The detected environment is never rewritten: it is evidence of what that machine reported.