Perplexity's developer account released the Monitor API on November 16. It runs checks on the web on a schedule and saves the results, which you can read through the API or receive as webhook notifications. There are two types: Search runs a query on a schedule and keeps only new, relevant results, while Page tracks 1 to 10 known URLs, sets a baseline on the first fetch and then returns meaningful text changes. The official pricing page lists $0.001 per succeeded Search run or per counted fetched URL in a succeeded Page run, which is $1 per 1,000, and failed or skipped runs are free. It is supported in the Python and TypeScript SDKs and the API Console.
Key Takeaways
- ✓Two monitor types: Search (runs a query on a schedule and keeps new, relevant results) and Page (tracks text changes at 1 to 10 known URLs); one monitor cannot mix the two
- ✓Flow: the first run starts asynchronously right after creation, later runs follow the schedule (for example weekly) until you pause or delete the monitor; an optional goal describes the results you want
- ✓Each run stores kept findings in changes and fetch errors in target_errors; read them by polling the API or configure a public HTTPS webhook for notifications
- ✓Pricing: $0.001 per succeeded Search run and $0.001 per counted fetched URL in a Page run, or $1 per 1,000; failed and skipped runs are free
- ✓Perplexity CEO Aravind Srinivas promoted it on X as a way to track any event, topic or webpage change and get webhook updates
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background
Many agents and apps need to watch the web for changes: competitor news, policy pages, price lists, documentation updates. Until now that usually meant writing your own scheduled scraper, storing snapshots and diffing them. Perplexity's Monitor API, released on November 16, turns that work into a hosted service.
How it works
There are two monitor types. Search runs a query on a schedule and keeps new, relevant results since the last run; Page tracks 1 to 10 known URLs, sets a baseline on the first fetch and then returns meaningful text changes. Monitors keep state between runs, and an optional goal describes the results you want. Findings are stored in each run's changes field and can also be pushed to a webhook.
Numbers that matter
Perplexity has not published accuracy or latency figures. Pricing is public: $0.001 per succeeded Search run and per counted fetched URL in a Page run, or $1 per 1,000, with failed and skipped runs free.
What it means for developers
With a Perplexity API key, call client.monitors.create in the official Python or TypeScript SDK with your targets and a schedule such as weekly; configure an HTTPS webhook if you do not want to poll. It is an easy way to give agents a scheduled intelligence feed with costs tied to run counts.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.