{"uid":"cap_IrFJfd81S59gtsl0R9x5V","slug":"dns-doctor-watch-ping-441a983f","name":"DNS Doctor Watch Ping","description":"One DNS Doctor HTTP ping watch: a URL is checked from five regions on four continents on a 5- or 15-minute cadence for a paid window of up to 24 hours, polled by handle.","url":"https://dnsdoctor.dev/api/v1/watch/ping","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"url":{"type":"string"},"window_hours":{"type":"number","maximum":24,"minimum":1},"cadence_seconds":{"enum":[300,900],"type":"integer"}}},"responseSchema":{"type":"json","example":{"state":"running","poll_url":"https://dnsdoctor.dev/api/v1/watch/wid_example","watch_id":"wid_example","expires_at":"2026-09-06T12:00:00Z"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.004167","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.004167/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.004167","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.004167","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_AgHzg4MJ01GpVW0WosTKX","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.004167","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Starts a recurring DNS monitoring watch job for a URL, polling at configurable intervals to track DNS health changes over time.","exampleAgentPrompt":"Set up a DNS watch on example.com that checks every 5 minutes for the next 12 hours so I can track whether my DNS changes are propagating correctly.","exampleUseCases":[{"title":"Post-migration DNS propagation tracking","prompt":"I just moved example.com to a new DNS provider — start watching it every 15 minutes for the next 24 hours so I can see when the changes finish propagating globally."},{"title":"Email deliverability monitoring after SPF update","prompt":"I updated the SPF record on mycompany.com — can you set up a DNS watch polling every 5 minutes for 6 hours to make sure the change takes effect and email authentication stays valid?"},{"title":"Proactive domain health alerting for production site","prompt":"Start monitoring storefront.io's DNS every 15 minutes for the next 8 hours so I'll know immediately if anything breaks after today's deployment."}],"resultDescription":"Returns a JSON object containing a unique watch_id, the state of the watch job (e.g. 'running'), a poll_url to retrieve updates, and an expires_at timestamp indicating when the watch window ends.","failureModes":["Invalid or unreachable URL returns an error","window_hours outside the 1–24 range causes a validation error","cadence_seconds must be exactly 300 or 900; other values are rejected","Expired or duplicate watch IDs may result in conflicts","Payment failure (x402) prevents job creation"],"whenToPreferThis":"Use this endpoint when you need continuous, scheduled DNS monitoring over a defined window rather than a one-shot DNS scan. It is ideal after DNS record changes (SPF, DMARC, DKIM, A records) when you want to watch propagation in near-real-time at 5- or 15-minute intervals without manually re-triggering checks. Prefer it over single-scan endpoints when tracking temporal changes matters.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T18:30:26.690Z","isFirstParty":false}