Competitor scan
What's a competitor using? Tech stack, HTTP headers, WHOIS, and page metadata in one call.
$0.15
per call · one payment for the whole workflow
POST /api/skill/competitor-scan
4 tools run server-side in one request. You pay once, settle once, and get a single response - no orchestration, no per-step payments, and a partial-success envelope if any step fails. USDC over x402 on any supported chain.
When to use this pack
Competitive intelligence - fingerprint their infrastructure, hosting, frameworks, and page metadata.
Tools in this pack
All 4 run inside the single $0.15 call above. Each is also callable on its own if you only need one part.
- Tech stack detection POST /api/tech-stack Detect the technology stack of a public website: CDN, web server, language/runtime, frontend framework (Next.js, Nuxt, SvelteKit, Remix, Astro, React, Vue, Angular), CMS (WordPress, Drupal, Ghost, Shopify, Wix, Squarespace, Webflow), analytics (GA, GTM, PostHog, Mixpanel, Segment, Hotjar, Plausible, Fathom), and payments (Stripe, PayPal). Signature-based; no third-party API.
- HTTP headers + security analysis POST /api/http-headers Fetch a URL and return every response header plus a security analysis: HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP/COEP. Scores 0–100 by presence, flags weak HSTS, and warns on Server/X-Powered-By identity leaks. SSRF-protected.
- Domain WHOIS (RDAP) POST /api/whois Domain registration data via RDAP (the structured WHOIS successor): registrar, creation/expiry dates, status, nameservers.
- Page metadata GET /api/meta Fetch page metadata for a URL: title, description, OpenGraph, Twitter cards, canonical URL, favicon.
Workflow
- Fingerprint the tech stack - CMS, framework, CDN, analytics, third-party scripts.
- Fetch HTTP headers for server info, caching strategy, and security posture.
- Pull WHOIS for domain age, registrar, and hosting provider.
- Get page metadata - title, description, OG tags for their positioning.
Call it directly
Any x402 client pays the 402 and gets the whole workflow back in one response:
npx agent402-client call competitor-scan {"url":"https://stripe.com"}
Run it in Claude
claude mcp add agent402 -s user -- npx -y agent402-mcp@latest
Then paste this prompt into Claude:
Scan the competitor at https://stripe.com using Agent402's competitor-scan skill pack. Get (1) tech stack, (2) HTTP headers, (3) WHOIS, (4) page metadata. Summarize their infrastructure and positioning.