The vocabulary around agentic web monitoring is forming faster than the market can agree on what the words mean. A handful of terms now mean something specific, even though some coverage and buyers are still using them loosely. This glossary sets working definitions while the category is still young enough to move.

Each entry is the shortest accurate definition I can write, followed by a paragraph of context. Cross-references point to related terms in this list and to the longer pieces elsewhere in the series. Some of these will calcify into the language. Some will get replaced by sharper words. If you think one of them is wrong, tell me. The vocabulary is still soft enough to move.

Fixing the vocabulary before the press waters it down.

Agentic Search

Agentic search is search that runs in the background on a recurring schedule, takes action without re-prompting, and returns results when something matches. The user states a topic or URL once; the system samples or polls continuously; results arrive when conditions are met instead of when the user asks.

I use agentic search as the umbrella that contains both open-web agents and page monitoring agents. Visualping is a page monitoring agent. Related consumer vocabulary became more visible at Google I/O 2026, when Google announced its "information agents" feature inside Search. Before that, the same behavior had been shipping for years under names like "saved searches," "alerts," and "monitoring."

Not to be confused with AI search, which is a single on-demand query answered by a language model. Agentic search is recurring; AI search is one-shot.

Information Agent

Information agent is the consumer-facing name for an AI agent that continuously samples the open web for a topic and reports back. The input is a topic. The output is a synthesized briefing. The freshness model is wide and shallow.

Google introduced the term at I/O 2026 for a feature it said would roll out in summer 2026 to paid AI Pro and Ultra subscribers. ChatGPT Pulse, launched in September 2025 and initially available to Pro subscribers, fits the same architectural definition though OpenAI uses different branding. The term may become a broader category label if competitors adopt similar language.

See also: the two architectures of agentic search for why information agents and page monitors are different systems.

Open-Web Agent

Open-web agent is the architectural term for any agent that samples the broad web (rather than watching one specific URL) on behalf of a user. Named examples and adjacent products include Google Information Agents, ChatGPT Pulse, Exa, and Perplexity, depending on whether the use case is recurring discovery, API search, or AI research.

The architecture inherits from search and retrieval. An open-web agent typically relies on crawling, indexing, retrieval, ranking, and synthesis across sources. It typically does not produce the same page-specific timestamped evidence as a dedicated page monitor. The freshness model is "what is happening in this topic this week," not "what is on this page right now."

Not to be confused with a web crawler. A crawler indexes pages. An open-web agent uses a crawler (usually somebody else's) to answer a recurring question.

Page Monitoring Agent

Page monitoring agent is the consumer-facing name for a system that watches one specific URL on a schedule, detects changes, classifies them, and routes an alert. The input is a URL. The output is a change event. The freshness model is narrow and deep. The shorter term "page monitor" refers to the same architecture.

Visualping is a long-running page monitoring agent, with a sample of 1,874,911 active monitors on a single day in May 2026 and 58.8 percent of those owned by a team or workspace. Page monitoring agents inherit from testing and observability, not search. The two architectures (page monitoring agents and open-web agents) are more complementary than competitive.

See also: the precision-layer explainer.

Monitoring Primitive

Monitoring primitive is the lowest-level building block that any agent or workflow needs when it has to know that web state has changed. A monitoring primitive exposes a small interface: create a monitor on a URL, read recent change events, receive a webhook when something changes.

Higher-level agents call monitoring primitives the same way browsers call TLS or databases call an index. The Visualping MCP and REST API are shaped this way. The term is useful because it separates "the thing that watches" (a primitive) from "the thing that decides what to do with the watch" (an information agent or coding agent).

See also: how Claude Code and Codex use Visualping as a monitoring primitive.

Discovery Layer

Discovery layer is the part of an agentic search stack that finds sources you do not yet know about. It samples the open web, surfaces candidate URLs, and synthesizes summaries across many pages.

The discovery layer is wide and shallow. It is the right layer when the user has a topic but no specific URL in mind. Google Information Agents and ChatGPT Pulse fit this layer; Exa can feed it when used for recurring API search or discovery. The discovery layer's output can be a list of candidate URLs or a summary across them, which can then be handed downstream to the precision layer for tight tracking.

Precision Layer

Precision layer is the part of an agentic search stack that verifies specific URLs on a defensible schedule with timestamped evidence. It is not primarily a synthesis layer; it tells you, with a timestamp, that one specific page changed.

The precision layer is narrow and deep. It is the right layer when the user already knows the URL and needs to be notified soon after a scheduled check detects a change. Visualping is one established product in this layer. Many workflows can use both layers together: discovery feeds precision, precision feeds action.

Change Event

Change event is the unit of output a page monitoring agent produces when a watched page changes. A change event can contain the URL, a timestamp, a visual or structural diff, an optional AI-generated summary of what changed, and, where supported, an importance flag.

Change events are typed objects, not strings. They get routed to email, Slack, webhook, REST API consumers, or directly into an agent stack via MCP. The format Visualping uses, with sample fields shown in the developer cornerstone, is one practical model for a monitoring primitive.

Diff Fidelity

Diff fidelity is the accuracy of a page monitor's change detection. High-fidelity diffs catch meaningful changes (a price moved, a sentence was reworded, a button was renamed) while suppressing noise (a randomized hero image, a relative-time stamp, an analytics widget that re-renders on every fetch).

Diff fidelity is one of the main engineering problems in page monitoring. Pure visual diffing can have high recall but lower precision on dynamic pages, while pure text diffing can miss layout changes. One current approach is AI-classified diffing, where an importance prompt filters changes to a specific concern ("alert me when pricing changes, not when the hero image rotates"). Visualping's AI importance system is designed to help with this problem: identifying changes that matter while reducing alerts for cosmetic updates.

AI Importance Classification

AI importance classification is the layer that decides whether a detected change is worth alerting on, based on a user-supplied prompt or a default importance model. It runs after diff detection and before notification routing.

The binary output ("important" or "not important") lets downstream systems behave differently. A noisy channel like Slack should fire only on important changes; a quieter audit log should record every change. Visualping change events include an importance flag and a plain-English summary. The classification depends on the prompt; a well-written importance prompt can reduce false positives on a noisy page.

Audit-Grade Evidence

Audit-grade evidence is a change record designed to support a compliance review, legal review, or internal audit. The minimum bar: a timestamped screenshot of the page state before the change, a timestamped screenshot of the page state after, stable change metadata, and retention controls appropriate to the organization. Legal admissibility and chain-of-custody requirements vary, so teams should validate those requirements separately.

Open-web agents typically do not produce that kind of page-specific evidence. Dedicated page monitors are better suited to producing it because they poll a specific URL on a schedule. This is one reason some compliance and legal workflows have used page monitors for years.

Model Context Protocol (MCP)

Model Context Protocol (MCP) is an open standard that lets AI agents call external tools through a unified interface. An MCP server exposes a small set of named tools; an MCP client (Claude, ChatGPT, OpenAI Codex, Google Antigravity) discovers and invokes those tools by name during a conversation.

The protocol was published by Anthropic in late 2024 and has been adopted by a growing number of AI clients and developer tools. MCP is the integration surface that lets a monitoring primitive like Visualping show up inside an AI agent's tool list without custom plumbing. The Visualping MCP endpoint, in public beta as of May 2026, is https://visualping.io/mcp/sse.

Webhook

Webhook is a user-configured HTTP POST that a service sends to a target URL when an event happens. In the monitoring context, the webhook fires when a change event is produced, carrying the event payload to a downstream system (a Slack channel, a CRM, a ticketing system, an AI agent).

Webhooks are the canonical "push" alternative to polling for monitoring data. Many monitoring systems use retry logic for failed webhook deliveries and expect a fast HTTP 200 from the inbound endpoint. The Visualping webhook contract and recommended downstream patterns are documented in the developer cornerstone.

Cadence

Cadence (or check frequency) is how often a page monitor fetches its target URL. Cadence is set per monitor. Tighter cadences catch changes faster; looser cadences are cheaper.

Common self-serve cadences include five minutes for fast-moving operational pages on Business, fifteen minutes for Personal workflows, hourly for slower official sources, and daily for slow-moving content. In a same-day snapshot of active Visualping monitors on May 24, 2026, 52,452 ran on a five-minute-or-faster cadence. Sub-minute monitoring may be available for eligible enterprise configurations.

Frequently asked

What is the difference between an information agent and a page monitoring agent?

An information agent samples the open web for a topic on a recurring schedule and synthesizes results. A page monitoring agent watches one specific URL on a schedule and reports the diff. The two products live in different architectural layers and serve different jobs; many workflows can use both, with discovery feeding precision.

When did Google announce "information agents"?

Google announced information agents at Google I/O 2026 on May 19, 2026, with a rollout planned for summer 2026 to paid AI Pro and Ultra subscribers. The name gave the broader agentic-search category one of its first high-visibility consumer-facing labels.

Is "agentic search" the same as "AI search"?

No. AI search answers a single on-demand query using a language model. Agentic search runs in the background on a recurring schedule, takes action without re-prompting, and returns results when conditions are met. The same vendor often ships both surfaces, but the user-facing behavior is different.

What is the simplest way for an AI agent to monitor a URL?

Add the Visualping MCP to a supported agent client as a custom connector at https://visualping.io/mcp/sse, then ask the agent to "monitor this URL." The full walkthrough lives in the developer cornerstone for this series. Setup is a connector flow rather than an API integration.

Why is "monitoring primitive" a useful term?

It separates the work of watching a URL (a small, stable interface any agent can call) from the work of deciding what to do with the watch (which lives in the calling agent or workflow). The separation lets one tool stay small and focused while the agent stack above it grows. The pattern is similar to other infrastructure primitives such as TLS, OAuth, and webhooks: a focused interface that higher-level systems can rely on.

Closing

This is the vocabulary I will use for the next year. The terms above are the working set as of mid-2026. The point of writing them down now is to give the next round of work a stable place to start from. If a sharper word arrives for any of them, I will swap it in. Until then, this is the list.

Eric Do Couto is Head of Marketing at Visualping. He writes about the architecture of monitoring, AI agents, and the slow business of category formation.