webschutz.halowerk.com
Paid API · webschutz.halowerk.com · found in a public list · checked since 2026-11-04
Live, payment required · latest check
Checks a site's Content-Security-Policy default-src directive against a stated threshold.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means
Placed in Scan websites and domains: Scan live sites, apps and domains for exposed data, headers, TLS and attack surface.
POST https://webschutz.halowerk.com/v1/csp-default-src-decision$0.001 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Payment terms
- Price per call
- $0.001
- Protocols
- x402
- Networks
- eip155:8453
- Terms changes, 90 days
- 0 in 1 day tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-11-04; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 1
- Paid calls, 30 days
- 1
The registry's own figures, not our measurements.
Access
- Our latest check
- Asked for payment (x402)
- Stated
- not stated
- Payment model
- Per call (asked for payment for our request)
- Currency
- USD (USDC, in its payment terms)since
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Calls it declares
POST target context
From the payment request it sent our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Identity, security and compliance / Security / Scan websites and domains (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-05. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Purpose tags: none in the registry
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 93 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_2dc3116a95abcd02