Competitive Intelligence Snapshot

What it runs

1. 1
   Tech Stack Detection

   Source: HTTP response analysis (headers, JavaScript libraries, meta tags)

2. 2
   SEO Audit

   Source: HTTP response analysis (meta tags, heading structure, performance metrics)

3. 3
   Landing Page Roast

   Source: HTTP fetch + Claude API (conversion analysis)

4. 4
   Developer Registry Name Check

   Source: npm registry API, PyPI JSON API, GitHub REST API (organisations)

The answer returns every step’s result, so your agent can show or check each one.

Inputs

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/competitor-snapshot/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "brand_username": "stripe",
      "competitor_url": "https://stripe.com"
    },
    "max_price_cents": 154
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/competitor-snapshot \
  -H 'Content-Type: application/json' \
  -d '{
    "brand_username": "stripe",
    "competitor_url": "https://stripe.com"
  }'

The bundle’s published example input.

Limitations

• Trustpilot, Glassdoor, LinkedIn, Google Search, Google Patents, Reddit and the major social platforms (Facebook, Instagram, X) are not supported and return a policy error before the page is read. Repeating the same request does not return content.

  From step: Tech Stack Detection

• Database covers 1,000+ technologies — niche or custom-built tools may not be identified

  From step: Tech Stack Detection

  What to do instead: Check the raw HTTP headers in the response for custom X-Powered-By or Server values that indicate unlisted technology

• Detection based on HTTP headers, JavaScript libraries, and HTML signatures — technologies loaded conditionally or server-side only may not be detected

  From step: Tech Stack Detection

  What to do instead: Complement with dns-lookup and ssl-check results to infer infrastructure choices not visible in the HTML

• Pages with more than 16 MiB of HTML are refused with a caller_input error naming the input field. The call is not charged, and the page is not retried through another fetch or rendering route.

  From step: Tech Stack Detection

• Analyses on-page SEO factors only — does not assess backlink profile, domain authority, or content quality

  From step: SEO Audit

  What to do instead: Combine with domain-reputation for authority signals and google-search to check actual SERP positioning

• Only the first 500 KiB of robots.txt is parsed. Directives beyond that limit do not appear in the result.

  From step: SEO Audit

• AI-generated critique based on conversion best practices — subjective elements like brand tone are not assessed

  From step: Landing Page Roast

  What to do instead: Use the structural and CTA recommendations directly, but validate brand-voice feedback against your own style guide

• Pages whose viewport screenshot exceeds 4 MiB are refused with a caller_input error. The call is not charged.

  From step: Landing Page Roast

• Checks npm packages, PyPI projects and GitHub organisations through their official APIs. Social platforms and personal accounts, including personal GitHub, npm and PyPI profiles, are not checked.

  From step: Developer Registry Name Check

  What to do instead: To check a social handle, use that platform's official API, or ask the account owner to confirm it.

• Each call checks only HTTP status through the npm, PyPI and GitHub organisation APIs, with one request per registry. It does not inspect page content or look up personal accounts.

  From step: Developer Registry Name Check

• GitHub organisations and personal accounts share one namespace. A 404 from the organisations API means no organisation has the name; a personal account may still hold it, so GitHub is never listed in available_platforms.

  From step: Developer Registry Name Check

  What to do instead: Try registering the organisation on GitHub to confirm availability.

• A 404 means no package, project or organisation was found, but does not guarantee the name can be registered. npm and PyPI can reject prohibited or similar names, and PyPI can return 404 for registered projects without releases.

  From step: Developer Registry Name Check

  What to do instead: Confirm by attempting the registration before relying on the name.

• When a registry rate-limits or refuses the request (HTTP 401/403/429) or cannot be reached, that registry's entry has exists null and a note, and is counted in unknown_count rather than treated as available.

  From step: Developer Registry Name Check

  What to do instead: Retry later for the registries reported as unknown.