signal.halowerk.com

● Live

Copies a prompt for your agent.

Scores the links of the start page by path (karriere, jobs, stellen, stellenangebote, careers, join-us, ausbildung …), link text and links into known applicant tracking systems; falls back to /karriere, /jobs and /careers. The careers page is then fetched (robots.txt respected, at most 5 page fetches) to report HTTP status and redirects, and open positions are counted from schema.org JobPosting markup, from the documented public board API (Greenhouse, Lever, Personio, Recruitee, Ashby…

Claim this service

Price: $0.005; Asked in its payment challenge
Chain: Base
Paid in: USDC
Live: 2 of 2 checks

Endpoint

POSThttps://signal.halowerk.com/v1/careers-page-detect

$0.005 asked in its payment challenge on 14 Nov 2026

curl -i -X POST 'https://signal.halowerk.com/v1/careers-page-detect' \
  -H 'Content-Type: application/json' \
  -d '{"html":"<html><body><a href=\"https://jobs.lever.co/beispielfirma\">Jobs</a><a href=\"/kontakt\">Kontakt</a></body></html>","base_url":"https://www.beispiel.de/"}'

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/signal.halowerk.com

Recent checks

13 Nov 2026Taller is slower; grey is not live.14 Nov 2026

Median response: 669 ms
Last checked: 14 Nov, 15:25 UTC

Our probes look for a payment challenge. They don't test payment or delivery.

All 2 checks

When (UTC)	Result	HTTP	Response
14 Nov, 15:25 UTC	Live	402	898ms
13 Nov, 00:24 UTC	Live	402	439ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 14 Nov, 15:25 UTC, it returned HTTP 402 or another detected payment-challenge signal.

What payment terms does signal.halowerk.com advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Something wrong on this page? Tell us.