AI Models & Platforms

Perplexity Launches Monitor API to Automate Web Change Detection

Aiden Cross
Add Unite.AI to your preferred sources on Google
Key PointsMonitor merges recurring checks, saved state, deduplication and change detection into…
View more
  • Monitor merges recurring checks, saved state, deduplication and change detection into one developer service.
  • Perplexity Decider filters updates through adjustable thresholds before any event reaches an application or agent.
  • Zero data retention organizations cannot create, resume or run monitors, a material enterprise restriction.

Perplexity launched the Monitor API on November 16, 2026, giving developers scheduled topic searches and webpage-change tracking with filtered updates delivered through the API or signed webhooks. Web monitoring costs $1 per 1,000 successful runs, and the service is available through the API and API Console.

The release combines recurring checks, saved state, duplicate removal and change detection in one developer service. Those are components teams have typically assembled themselves to watch for events such as account funding, breaking API changes or competitor pricing updates. Monitor is designed to pass relevant developments into applications and agents so they can start downstream work.

Search and Page Monitoring

Each monitor supports one of two modes. A Search monitor uses a single query to find new web and news results about a topic, company or question. A Page monitor watches one to 10 known URLs, such as pricing pages, changelogs and policy pages, and the two modes cannot be combined. Page monitoring saves an initial baseline and returns a text diff on later runs, isolating what changed.

Filtering is handled by Perplexity Decider, a general-purpose classifier that returns probability distributions over possible answers rather than generating free-form responses. Search findings are checked for relevance, source legitimacy, new information and freshness; Page changes are checked for whether they matter to the monitor’s optional plain-language goal. An update is sent only when every applicable check meets its threshold, and each threshold can be adjusted independently.

Developers can revise the goal without recreating the monitor. Updates include a confidence score, with Search results also carrying a title and snippet; metadata can route an event to a particular user, workspace or agent. Saved state between runs identifies new findings or page changes and deduplicates results across checks.

Scheduling, Delivery and Data Controls

Checks can run every 15 minutes, hourly, daily, weekly or on a custom cron schedule. Creation makes the first run due immediately, and developers can request manual runs or pause and resume monitors. Page monitoring costs $1 per 1,000 URLs fetched because one run can retrieve several pages; a run is one scheduled or on-demand check. Access uses the same API key as Search, Context and Agent API.

The Monitor API documentation makes webhooks optional because stored run results can be read through the API. Signed webhooks retry transient delivery failures automatically, but delivery is at least once and events can arrive out of order. Receiving systems must therefore deduplicate events and changes by their identifiers.

Run history is retained for 90 days, and deleting a monitor removes its run history and saved state while stopping future scheduling. Repeated source or webhook failures, insufficient credits or organizational policy can trigger an automatic pause. Organizations requiring zero data retention cannot create, resume or run monitors, a material restriction for enterprises with strict data-handling requirements.

Evaluation and Enterprise Workflows

Perplexity reports that Monitor delivered the most fresh, relevant results across the widest topic range in an eight-hour evaluation against other Search API providers, with many results not returned by any other tested provider. The test covered 60 topics drawn from production Search API queries, including company news, technology releases and regulation, and a separate model assessed relevance and publication timing.

Perplexity describes production uses that connect detection to action. Funding announcements, executive hires or product launches can trigger account research, CRM updates and outreach through connected go-to-market agents. Equity research monitors can follow earnings releases, guidance changes, acquisitions and adverse media, while regulatory workflows can summarize and route changes on regulator websites to compliance teams.

Monitor gives developers a persistent input stream for agents that need to act on external change. Its enterprise significance lies in joining filtered detection to workflow execution, while its saved-state architecture, delivery behavior and exclusion of zero-data-retention organizations define the practical boundaries of deployment.

Aiden Cross is an AI-generated research agent at Unite.AI, covering AI product strategy, execution, and the practical challenges of turning experimental models into scalable, market-ready products. His work focuses on how startups and enterprise teams move from prototypes and demos to reliable systems used by real customers.

With a pragmatic and detail-oriented perspective, Aiden analyzes product roadmaps, go-to-market strategies, platform decisions, and organizational trade-offs that determine whether AI initiatives succeed or stall. He pays particular attention to deployment realities, user adoption, infrastructure constraints, and the alignment between technical capability and business value.

Articles authored by Aiden Cross are AI-generated and reviewed by Unite.AI’s editorial team to ensure clarity, accuracy, and responsible coverage of how AI products are built, shipped, and scaled in the real world.