Tool search 164,478 tools · 10,067 live servers

Files feedback (bug, idea, friction, praise, other) with the COTAL team on behalf of the user. The same log the site's feedback widget writes to. Requires the user's email so the team can follow up.

Reserves a seat on the waitlist for Cotal Cloud, the hosted Cotal mesh (closed alpha), for the user's email. Idempotent per email: calling again updates the optional details instead of adding a second seat.

Subscribes the user's email to release updates from the COTAL team. Idempotent: an already-subscribed email is a no-op.

Sends a discovery-call request to the COTAL founders for a company evaluating agent coordination. The team replies by email. Requires the user's work email and company.

The org's notification channels: id, operator-set name, kind (email, slack, telegram, webhook, and so on), and whether the channel is enabled. Two flags say a channel is not working even where it reads as ready: awaiting_verification for an email address nobody confirmed, and not_delivering for an enabled channel whose recent alerts all failed to arrive. auto_bind_tags is the channel's tag rule: it also pages any monitor carrying one of those tags, so a monitor with no binding can still be covered. Channel settings are withheld, since they hold webhook URLs and bot tokens. Channels are created in the Uptimepage app, not here. Read-only.

Create a notification destination (channel) that monitors can route alerts to. Provide the fields for the chosen kind; unrelated fields are ignored. Non-email kinds are usable immediately; email kinds are created unverified and send a confirmation link that must be clicked before they can be attached to a route. Returns the new channel id — pass it to set_route.

List all notification destinations (channels) in the project: email, webhook, Slack, Discord, Telegram. Use channel IDs to configure routing rules for monitors.

Route a monitor's alerts for one event type to a set of destinations (channels). THIS REPLACES THE WHOLE SET for that event type — every destination you leave out stops receiving that event, including ones somebody else configured. CALL get_monitor FIRST and read its `routes` field: that is the monitor's current routing, and adding a destination means passing the existing ids PLUS the new one. Pass an empty channel_ids to remove all routing for the event. Destinations must be verified and enabled (email destinations must be confirmed first). Use list_destinations for IDs.

Send something through a destination right now, to move it from 'created' to 'known to work'. By default it delivers a synthetic 'LastPing test alert' immediately — use that after create_destination to confirm the credentials are right. For an EMAIL destination that is still unverified, a test alert is not what you need: an unverified email cannot be attached to a route at all, and no amount of testing changes that. Pass resend_verification=true instead to re-send the confirmation link a human must click. That is the tool to reach for when create_destination reported UNVERIFIED and the confirmation email never arrived or has expired.

Update a notification destination's name and/or config in place. Only the fields you pass are changed. The destination kind cannot be changed — delete and recreate instead. Changing an email destination's address resets verification and sends a new confirmation email.

Save a named list of carriers (by US DOT number) for continuous monitoring. Requires a paid CarrierScore API key (Monitor or Compliance tier) — connect with your key via OAuth (or set CARRIERSCORE_API_KEY on a self-hosted server); the free tier gets a 403 with an upgrade link. Once saved, CarrierScore diffs every carrier on the list against the previous day's scoring run after each daily run and records alerts: new out-of-service order (critical), operating authority lost (critical), insurance filing lapsed (high), operating status leaving Active (high), risk score up 10+ points (medium), high-confidence reincarnated-carrier link appearing (medium). Alerts are always retrievable with list_alerts; optionally they are also pushed to a webhook (JSON POST, HMAC-signed via the X-CarrierScore-Signature header with the per-key secret from GET /v1/lists) and/or summarized in one daily digest email. Use this when a broker asks to "watch" or "keep an eye on" their carrier roster. Caps: 500 DOTs total across all lists on the Monitor tier, 5000 on Compliance; up to 50 lists per key. Saving the same DOT twice in one list is deduped. Args: - name: short label for the list (1-100 chars) - dot_numbers: array of DOT number strings (1-8 digits each) - webhook_url (optional): https URL to POST new alerts to - email (optional): address for the daily digest Returns JSON: { list_id, name, dots, created, updated, webhook_url?, email? }. Keep list_id — list_alerts needs it. Errors: 403 without a paid key; 400 on invalid DOTs, empty list, or exceeding the tier cap (message says which); 401 bad key.

Create a seat alert that notifies you by email when a matching seat becomes available on a specific flight. Supports preferences like window, aisle, exit row, specific seat, adjacent seats, and class availability. Requires authentication. The flight must already be in our database — use search_flight first if not.

Set someone up with competitor tracking before they have an account, and hand them a link to take it over. Name the companies they care about, by name or by domain. We match them against the companies we already track and the first three you list go on file, with their change history readable straight away. We do not fetch an address you supply: a company we do not track yet comes back in `shortfalls`, which is not a failure — it is something the person can add themselves once they have claimed. Call this ONCE per person, with every company you know about. If more come up later, use `add_tracked_competitors` to fill the remaining slots on the same organization rather than calling this again — a second call here starts a second organization with a second link, and the person ends up with two things to claim instead of one. Nothing is charged to anyone, no email is sent and the organization is removed after four days unless someone claims it. The claim link comes back in the response and travels no further, so pass it on and tell them what went on file and what did not.

Listeaza ultimele notificari trimise userului (email, webhook, slack, discord, telegram), cu detalii despre schimbarea care a declansat fiecare alerta.

Start monitoring a taken username so the user can claim it when it frees up or drops (alerts follow the plan's check schedule after two confirming checks). Creates one watch per platform against the plan's slot limit (already-watched pairs are skipped); checks then run automatically on a plan-based schedule and alerts are delivered in-app, by email, and to any configured webhooks. Returns JSON with created watch ids and the skipped count. List watches with namesniper_watches; stop one with namesniper_unwatch. Requires a paid API key (Pro or Business).