# Halowerk Stack Detector

> Halowerk Stack Detector is a paid API for AI agents from stack.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Detects the technology stack of a given hostname using signature matching against headers, cookies, asset paths, meta tags, and DNS/ASN records, returning confidence-scored hits with supporting evidence.

## Facts

- Endpoint: POST https://stack.halowerk.com/stack
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-stack-detector-0308a5ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vKFhag6FTzJceLgyQzCfd

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability halowerk-stack-detector-0308a5ff -d '<json body>'
```

Example prompt: Can you detect what technology stack shopify.com is running on and show me the confidence scores and evidence for each hit?

## When to prefer this

Choose this endpoint when you need fast, single-request technology fingerprinting of a public hostname with structured, confidence-scored evidence. It is ideal for competitive research, pre-engagement security recon, or enriching domain records with stack information. The 24-hour cache makes it efficient for repeated lookups. Prefer alternatives if you need full recursive crawling or real-time uncached detection.

## Known failure modes

- Unknown or unresolvable hostname returns no hits or an error
- Heavily obfuscated sites with no detectable signatures return empty or low-confidence results
- Results may be stale up to 24 hours due to caching
- Private or localhost domains are unlikely to yield useful results
- High-confidence detections may be absent if the site strips identifying headers

## How this service works

One HTTP request per host, matched against an in-house signature set. Every hit carries a confidence value from 0 to 100 and the evidence it rests on: response header, asset path, cookie name, meta generator, DNS or ASN record. Results are cached for 24 hours per host, so a repeat lookup of the same domain answers from cache.

## Output

Returns a list of detected technology hits for the queried hostname, each with a confidence value from 0 to 100 and the evidence type that produced the hit (e.g. response header, asset path, cookie name, meta generator tag, DNS record, or ASN record). Results may be served from a 24-hour cache if the same host was queried recently.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "description": "Absolute http or https URL. Only the host matters for the cache; a path is followed but never probed separately."
  },
  "render": {
   "type": "boolean",
   "default": false,
   "description": "Render the page in a headless browser before matching. Off by default: plain delivery is faster, cheaper on the origin and enough for almost every site. Turn it on for pages that build their markup entirely in JavaScript."
  },
  "refresh": {
   "type": "boolean",
   "default": false,
   "description": "Bypass the 24 hour cache and fetch the origin again. Same price."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-stack-detector-0308a5ff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stack.halowerk.com](https://www.zero.xyz/host/stack.halowerk.com/llms.txt)