# HTTP Success Decision

> HTTP Success Decision is a paid API for AI agents from webtechnik.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-17).

Passively fetches a public URL and evaluates whether it returns an HTTP success response, returning a verdict, observed evidence, threshold, evidence source, and limitations.

## Facts

- Endpoint: POST https://webtechnik.halowerk.com/v1/http-success-decision?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/http-success-decision-9c8fd259
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nq9H_hC46yooe3aVt8Jrq

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 http-success-decision-9c8fd259 -d '<json body>'
```

Example prompt: Can you passively check whether https://example.com is returning a successful HTTP response right now — I want to know the verdict, what status code was observed, and any limitations of the check?

## When to prefer this

Use this endpoint when you need a quick, passive, read-only verdict on whether a public URL is returning HTTP success, without any authentication, form submission, or payload injection. Prefer it over general HTTP client calls when you need a structured verdict with evidence source and limitations documented. It is ideal for uptime checks, pre-deployment validation, or alert triage on public-facing endpoints.

## Known failure modes

- Target URL is unreachable or DNS resolution fails — returns observation of connection error with a fail verdict
- Target returns a redirect loop — may not resolve to a final success status
- Rate limiting or firewall on target blocks the passive fetch — observation reflects blocked response
- Malformed or non-HTTP URL provided — validation error returned
- Target requires authentication — passive check cannot log in and will likely observe a 401 or 403 non-success response

## How this service works

HTTP Success decision fetches current public evidence from the supplied target and evaluates the documented criterion. It returns the observation, threshold, verdict, exact evidence source, limitations and a mode-specific action. The check is passive: no login attempt, payload injection, exploit, purchase, form submission or load test is performed.

## Output

Returns a structured response containing the observed HTTP status, the success threshold being evaluated, a pass/fail verdict, the exact evidence source (URL fetched), any limitations of the passive check, and a mode-specific recommended action.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "target": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 3,
   "description": "Public HTTP(S) URL or domain to inspect. A bare domain is normalized to HTTPS."
  },
  "context": {
   "type": "object",
   "description": "Optional non-secret correlation labels returned unchanged only in the request lifecycle.",
   "maxProperties": 12,
   "additionalProperties": {
    "type": [
     "string",
     "number",
     "boolean",
     "null"
    ]
   }
  },
  "baseline": {
   "type": [
    "object",
    "null"
   ],
   "description": "Optional baseline returned by a previous snapshot call.",
   "additionalProperties": true
  },
  "compare_url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 3,
   "description": "Optional public comparison URL. Used by change and monitoring services."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/http-success-decision-9c8fd259/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from webtechnik.halowerk.com](https://www.zero.xyz/host/webtechnik.halowerk.com/llms.txt)
