Build with agents

Get notified when an agent changes

Create a confirmed email watch for one listing or a capability policy, interpret change notices and manage the subscription.

7 min readReviewed

Before you start

  • An email address you control and a listing or capability requirement you want to watch.
  • A browser for subscribing. The optional Python example only builds a public watch URL and sends no email.

1. Choose a listing or a capability policy

Watch one listing when you depend on that particular agent. Open its profile or connection plan and follow the email-watch link, or enter its numeric listing ID on the Email watchlists page. This does not claim the listing or sign you up for marketing.

Watch a policy when you want to know about agents meeting a requirement. Start with Find by task, choose filters such as a recent card and reachable TLS, then follow the watch option. Keep the policy as narrow as the task requires. Requesting an impossible combination can legitimately produce no current matches.

2. Prepare a policy link without subscribing

This example creates the URL for a PDF-extraction policy. Run it locally, then open the printed address if you want to review the form. Creating or opening this link sends no confirmation email and creates no subscription. It contains public requirements, not a private management token.

Download this example

What to expect

The printed URL opens a form labelled Capability policy, displaying the selected requirements. It still needs your email, service-email consent and later confirmation. Boolean values in a browser URL use lowercase true or false.

3. Confirm the email request deliberately

After confirmation, the next background cycle records the initial baseline. It is not sent as a change alert, and the watch does not immediately rerun the publisher's endpoint. A LocalMark listing claim and its optional card-check notices are separate from this watch subscription.

  1. Review the target and enter an email address you control. Never enter an address copied from somebody else's Agent Card.
  2. Read and select the service-email consent box, then press Send confirmation link. The response deliberately says a message will arrive if the request can be accepted; it does not reveal other people's subscription status.
  3. Open the confirmation email within 24 hours. On the website, review the target again and press Confirm my subscription. Opening a GET link alone does not activate the watch, which prevents automatic email-link previews from confirming it.
  4. Keep the private management link from the confirmation flow or later notices. Active subscriptions expire after 180 days and can be renewed from that page.

4. Interpret notices and investigate alternatives

Watches compare LocalMark's stored observations. They can describe availability, changed requirements, recorded risk signals or new matching candidates. Meaningful changes are grouped into at most one notice per 24 hours. Scheduled card checks and backoff mean this is not an instant outage alarm or continuous uptime service.

A candidate losing a fresh observation may no longer meet your policy even when it is still online. Open the current profile, observation times and change history before deciding what to do. Suggested alternatives are candidates to inspect; LocalMark does not switch providers or pass along your credentials automatically.

If email is not your preferred workflow, read the public card-change feed or risk-only feed. Those feeds describe confirmed recorded changes, not a guarantee that every relevant change on the Internet was detected. They need no email address.

5. Renew, unsubscribe or delete

Open your private management link and select the action you intend. Unsubscribe stops future emails and cancels queued notices. Delete subscription and stored data also removes the associated contact, policy and consent record. Opening the management link alone performs neither action.

Treat confirmation and management URLs as private credentials. Do not post them in repositories, screenshots or support discussions. If you need help, send support the public listing URL or policy description instead of publishing a private link.

Troubleshooting
No confirmation email arrived
Check the address and spam folder, allow for delivery, and avoid repeated rapid submissions. A pending link expires after 24 hours.
No alert arrived after subscribing
An unchanged baseline is not an alert. Confirm the subscription and check whether the stored evidence actually changed; this is not a live connection monitor.

Examples are checked with read-only requests or isolated fixtures. Email confirmation, publisher changes and paid task authorization remain actions for you to complete. No example grants permission to run a third-party task.