Perplexity's developer documentation and pricing tables detail the Monitor API (POST /v1/monitors) alongside its rate limits. While the official changelog has no standalone dated entry for Monitor API (and sample JSON timestamps in the overview are dated November 13, 2026 rather than indicating a same-day launch), the full documentation tree is publicly accessible.

Search vs. Page Monitoring & Governance Rules

Separate Search and Page Monitors: Monitor API checks the web on a schedule and stores results for retrieval via API or the API Console. Each monitor configures either a single Search target (to discover URLs for a query) or 1 to 10 Page targets (to track text changes at known URLs); the two types cannot be mixed in one monitor. Run history is retained for 90 days, optional HTTPS webhooks must respond with 2xx within ten seconds, and monitors auto-paused due to insufficient credits or failing webhooks require an explicit resume call.

Zero Data Retention Restriction: Per the error documentation, organizations requiring zero data retention cannot create, resume, or run monitors (returning HTTP 403).

Official Pricing & Tiered Rate Limits

$0.001 per Succeeded Run or Counted URL: Search monitors cost $0.001 per succeeded Search run ($1 per 1,000 runs, billed once per succeeded run regardless of underlying search count), and Page monitors cost $0.001 per counted fetched URL in a succeeded Page run ($1 per 1,000 counted URLs). Failed and skipped runs are free.

Organization Quotas by Tier: Standard organization rate limits (shared across all keys and separate from Agent API budgets) allow 1, 3, 8, 17, 33, and 33 requests per second across Tiers 0 through 5, with active monitor caps of 100 (Tiers 0–1), 200 (Tier 2), 300 (Tier 3), 400 (Tier 4), and 500 (Tier 5).