Company Tech Stack

Analyse the technology behind a domain from its headers, HTML, scripts, DNS and meta tags: frontend, analytics, CDN, hosting, CMS and more.

Pay by wallet (x402) AI-generated company-tech-stack

Example

Example answer
{
  "cdn": "Cloudflare",
  "cms": null,
  "domain": "example.com",
  "analytics": [],
  "chat_widget": null,
  "dns_records": {
    "a": [
      "104.18.27.120",
      "104.18.26.120"
    ],
    "mx": [
      {
        "exchange": "",
        "priority": 0
      }
    ],
    "txt": [
      "_k2n1y4vw3qtb4skdx9e7dxt97qrmmq9",
      "v=spf1 -all"
    ],
    "cname": []
  },
  "css_framework": null,
  "email_provider": null,
  "meta_framework": null,
  "hosting_provider": "Cloudflare",
  "payment_processor": null,
  "frontend_framework": null,
  "detected_technologies": [
    {
      "name": "Cloudflare",
      "category": "CDN/Hosting",
      "confidence": "high"
    },
    {
      "name": "SPF",
      "category": "Email Security",
      "confidence": "high"
    }
  ],
  "http_headers_analyzed": []
}

Inputs

FieldTypeRequiredWhat it is
domainstringYesDomain to analyze (e.g. stripe.com)

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
cdnstringAlways (present in every successful answer)
analyticsarrayAlways (present in every successful answer)
hosting_providerstringAlways (present in every successful answer)
frontend_frameworkstringAlways (present in every successful answer)
detected_technologiesarrayAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "company-tech-stack",
    "inputs": {
      "domain": "https://stripe.com"
    },
    "max_price_cents": 30
  }'

Limitations

  • Only publicly visible technologies are detected

    Detects technologies visible in public-facing web properties — internal tools and backend infrastructure are not visible

    What to do instead: Cross-reference with job postings (job-board-search) to infer backend technologies from required skills