At I/O 2026, Google gave consumer language to a pattern Visualping has worked on for years.

On May 19 at I/O 2026, Liz Reid stood on stage and announced "information agents." Google described them as agents that would run in the background, monitor the open web, synthesize updates, and notify users when something changes. Google said the feature would roll out this summer to paid AI Pro and Ultra subscribers.

For Visualping, that announcement was one of the most relevant parts of the week, even though much of the coverage focused elsewhere. WIRED led with "Search goes agentic". TechCrunch wrote three different posts on Spark, Halo, and Daily Brief. Antigravity and the new model launches ate the keynote chatter. The architectural story, the one that matters to anyone building or buying in this space, sat in a single product slide and a four-paragraph blog section.

I want to write the architectural story down.

Google named information agents. Visualping has been monitoring web pages since 2017.

The lineage Google did not draw

Watching information agents become a named consumer category took twenty-three years. Here is the timeline most coverage skipped.

For two decades the work of watching the web sat inside scattered subscription tools, internal corporate platforms, and a few stubborn consumer products. The category had no shared consumer name. I/O 2026 gave it one.

Naming a category is a real act. It tells reporters what to write about. It tells buyers what to budget for. It tells engineers what to ask their CTO for. A named category is a market.

What Google named is the demand side of the problem. What Google did not draw is the supply side.

Two architectures, not one

Some commentary frames page monitoring agents like Visualping as sitting underneath Google's information agents in a hierarchy. The right picture is two architectures next to each other, both serving the same job, both load-bearing.

Discovery agents scan the open web for a topic. You hand them a question or a theme. They roam, synthesize, and surface what looks relevant. Google's announced information agents and ChatGPT Pulse are clear examples of this discovery layer; search and research products such as Exa and Perplexity can play a similar role when they are used for topic-level discovery.

Page monitors verify state on a specific URL. You hand them a page. They check it on a schedule, capture a visual or structural diff, classify the change, and route an alert. Visualping has sat in this layer since 2017. Their input is a URL. Their freshness budget is narrow and deep.

These layers do different things, and both are needed.

A discovery agent is the right tool when you do not yet know where the answer lives. It is usually the wrong tool when you already know the page that matters and need to be notified soon after a scheduled check detects a change. A discovery agent that broadly samples the web is not typically designed to watch thousands of specified pages on five-minute cadences with visual diffing, AI-driven importance classification, and a timestamped audit trail. That is a different system.

In a same-day snapshot on May 24, 2026, 52,452 active Visualping monitors ran on a five-minute-or-faster cadence. That is one concrete sign of the precision layer: SEC filings, regulatory dockets, tender boards, pricing pages, and status pages where minutes matter.

The architecture story is simple. Discovery agents find the page. Page monitors verify the page. Both feed downstream agents that take action on what changed.

Two architectures: discovery scans the web, precision verifies the page.

What a sample of 1.87 million monitors knows

The precision layer has been doing quieter work while the rest of the press caught up.

In a same-day snapshot on May 24, 2026, the sample of active Visualping monitors reached 1,874,911 jobs. In that same snapshot, 58.8 percent were owned by a team or workspace rather than a personal account. In this snapshot, a majority of active monitors were team- or workspace-owned.

In a separate profiled sample of 152,221 accounts, 11.4 percent come from companies with ten thousand or more employees. Some accounts in the profiled sample were associated with very large companies before Google's announcement.

In a thirty-day sample of 19.6 million completed checks, roughly one in ten returned a change. That is one measure of how often scheduled checks produce a new change signal. It is also one way to estimate how often downstream workflows could receive a timestamped change signal, when alerts or integrations are configured.

I will share the more telling number from the customer side, not the platform side. One customer, talking with our team in May, described what happened when their company tried to run broad LLM-based change detection on their own:

"When we've done this with, like, ChatGPT, it doesn't not give us answers. It will give us a change of changes, and it will say, oh, this was changed to this, from this to this. But then when we go and manually look it up, it's wrong."

That sentence is the substrate thesis in plain English. A general-purpose LLM running a broad scan can produce a story about what changed. Verifying that story, on a specific page, on a defensible schedule, with a screenshot and a timestamp, is a different system.

Another customer, an engineering services firm, put the economics in one line:

"Right now we've got multiple project managers all spending time looking at these sites when we could have one person doing that."

Information agents and page monitors can reduce the amount of manual checking required. The precision layer supplies the page-level evidence that automation needs.

The same gap is opening for coding agents

Consumer information agents are not the only place this architecture matters. Developers using coding agents such as Claude Code, OpenAI Codex, or Google Antigravity can run into a similar wall.

You ask the coding agent to "watch this dashboard and tell me when the build status changes," or "page me when the pricing on this competitor's docs page moves," or "trigger this workflow when the regulator updates the docket." The agent reasons well. The agent writes code well. Without a persistent monitoring tool, the agent often has to rely on temporary code or an external scheduler for the actual watching. It needs a monitoring primitive it can call.

Visualping can serve as that primitive. The Visualping MCP is in public beta and can be added as a remote custom connector in agent clients and workspaces that support MCP.

Add Visualping to your AI agent.

In Claude: use the custom connector flow under Connectors and paste https://visualping.io/mcp/sse. In ChatGPT: use the custom MCP connector flow when Developer mode or workspace connectors are enabled, then paste https://visualping.io/mcp/sse.

The agent can then use supported beta tools to create monitors, list monitors, and read recent changes. The REST API remains available on every plan, including Free, for webhook and code-first patterns.

Once that connector is wired, the architecture becomes practical. The discovery layer finds the page. The agent asks Visualping to watch the page. Visualping returns verified changes. The agent takes action.

I keep writing the word "primitive" on purpose. Information agents need monitoring primitives the same way browsers need TLS, databases need indexes, and search needs a crawler. The category is real. The substrate has to be real too.

The category formed in private notebooks long before Google named it.

What comes next for Visualping

Three commitments worth writing down in public.

We hold the precision layer. We keep building the things that make per-page monitoring durable: visual diffing on JavaScript-rendered pages, AI-classified importance, short cadences, including sub-minute options for eligible enterprise use cases, and timestamped evidence for customers who need to defend a finding in compliance, legal, or internal review.

We make Visualping callable from any agent stack worth caring about. The MCP endpoint is public beta this week. The REST API is on every plan. We will keep adding to both.

We publish the architectural framework openly so the category forms with shared vocabulary. This piece builds on earlier work like agent search optimization and opens a short series: a definition of open-web agents versus page monitoring agents, a comparison of the named players, a glossary for the information-agent era, a developer cornerstone on calling Visualping from coding agents. If the category Google named is going to mean anything in two years, the language has to be sharp before the marketing departments water it down.

Naming a category is not the same as owning it. The work of watching the web at the precision a real customer needs has been happening for nine years. It will keep happening.

The only thing that changes is that we no longer have to explain what the category is called.

If you think the substrate frame is wrong, I want to hear it. The vocabulary is still soft enough that one sharp counterargument could move it.

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.