Extract a single public HTTPS webpage into structured JSON with clean text, Markdown, title, headings and normalized links for AI-agent research. Stateless, no account or API key. No JavaScript rendering, paywall bypass or private data access. One page per call; 512 KB input cap, 50,000 output characters, 8-second fetch timeout and four redirects. A failed or invalid extraction is not charged.
Pay-per-call public DNS record lookup via Google DNS-over-HTTPS. Returns A, AAAA, MX, TXT, NS, CNAME, SOA or CAA records, DNS status, answers, authority and check timestamp. No private-domain or credential access.
Batch-check 1-20 public domains for DMARC policy, subdomain policy, pct, DKIM/SPF alignment, reporting URIs, raw TXT evidence, and validation warnings. Point-in-time DNS evidence; private/local targets are not relevant because inputs are public domains.
Deterministic technical and on-page SEO audit for one public HTTPS page, with transparent score/checks and unscored machine-accessibility signals. Informational only; no ranking guarantee.
Stateful public HTTPS page monitor. First paid call stores a payer-isolated baseline; later calls report deterministic visible-text changes and bounded diffs.
Ops Control HQ has 8 live APIs on PayAPI Market with 8 endpoints in total, in Data, Intelligence, Tools, Verification: Ops Control HQ Page Extraction, Ops Control HQ DNS Lookup, Bulk DMARC Lookup, Technical SEO Audit, Page Change Monitor, and 3 more.
Are Ops Control HQ's APIs verified?
8 of 8 have at least one settlement-verified route: PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC payment on-chain. Each listing page shows which routes were paid and links the receipt.
How do I pay for Ops Control HQ's APIs?
Per request, in USDC, over the x402 protocol. An agent calls the endpoint, receives HTTP 402 with the price and wallet, pays and retries. There is no API key, account or subscription. Free to list. PayAPI takes 0% of each job, and Ops Control HQ is paid directly.