HALOWERK td-befund bronze
detect.halowerk.com
we checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 11 Jan 2027 as of our check on 25 Oct 2026.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA384, issued via YE1 under ISRG Root X2 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
detect.halowerk.com. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 25 Oct 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txt— “HALOWERK Website Findings” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 25 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇩🇪 DE · Hetzner Online GmbH (AS24940)
- Last checked
- 21d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of detect.halowerk.com controls every word below.
/v1/inquiry/cta-commitment-conflict
An agent that resolves conflicting calls to action needs shared destinations with both order and nonbinding inquiry labels.
/v1/trade/shk/shk-emergency-channel-alignment
An agent that routes SHK emergencies needs emergency-labelled entries compared with the declared emergency wording at linked targets without reading contact values.
/v1/api/schema-reference-cycles
An agent that generates a finite schema model needs evidence of local reference cycles and their downstream dependencies.
/v1/events/job-state-reachability
An agent that implements asynchronous jobs needs evidence of unreachable terminal states and outgoing transitions from declared final states.
/v1/events/retry-schedule-window
An agent that configures event retries needs a finite schedule and evidence of retry attempts beyond the supplied retention window.
/v1/events/event-replay-window
An agent that designs webhook replay handling needs counts of events outside its explicit time window and repeated identifiers.
/v1/events/event-correlation-lineage
An agent that traces a job across synthetic events needs evidence of missing parents and changed correlation identifiers.
/v1/cms/cms-field-mapping-loss
An agent that plans a CMS migration needs evidence of unmapped source fields, duplicate destinations and incompatible declared scalar types.
/v1/cms/route-normalization-collisions
An agent that imports site routes needs counts of distinct supplied URLs that collapse under its declared case and trailing slash policy.
/v1/relaunch/relaunch-successor-inventory
An agent that plans a relaunch needs counts of old inventory items with no declared successor or a successor of a different declared function kind.
/v1/relaunch/relaunch-redirect-plan
An agent that reviews a supplied relaunch redirect plan needs counts of redirect sources that cycle or end outside the supplied target inventory.
/v1/commerce/shipping-interval-coverage
An agent that publishes shipping rules needs measured uncovered and multiply covered ranges within an explicit numeric domain.
/v1/feed/feed-timestamp-order
An agent that consumes structured feed updates needs counts of updated timestamps preceding their declared publication times.
/v1/mcp/mcp-annotation-consistency
An agent that catalogs MCP tools needs evidence of contradictory explicit read-only and destructive annotation declarations.
/v1/events/event-sequence-continuity
An agent that consumes a sequenced event stream needs counts of missing sequence numbers and inversions within an explicit delivered interval.
/v1/events/profile
An agent that validates an offline event workflow needs state reachability, retry-window bounds, replay timing, correlation lineage and sequence continuity in one supplied artifact.
/v1/relaunch/profile
An agent that prepares a relaunch needs declared URL normalization collisions, successor inventory coverage and redirect-plan resolution in one supplied artifact.
/v1/full
An agent that evaluates a website needs every independently accepted URL finding from one shared bounded raw-HTML measurement.
/v1/api/openapi-status-coverage
An agent that replays API test responses needs counts of statuses absent from the supplied OpenAPI response map.
/v1/api/http-conditional-exchange
An agent that tests conditional HTTP fetching needs evidence of returned statuses that disagree with a supplied entity-tag comparison.
/v1/api/http-byte-range-consistency
An agent that validates a supplied download transcript needs evidence that range boundaries status and delivered byte count disagree.
/v1/api/http-cache-current-age
An agent that replays a cache decision needs computed RFC age and evidence that a response was served fresh after its explicit freshness lifetime.
/v1/api/http-redirect-method-trace
An agent that replays HTTP redirects needs evidence of method or body changes forbidden by supplied 303 307 and 308 responses.
/v1/events/webhook-ack-partition
An agent that builds a webhook batch consumer needs counts of lost duplicate conflicting or foreign acknowledgements.
/v1/mcp/jsonrpc-response-correlation
An agent that consumes an offline JSON-RPC batch needs counts of missing duplicate foreign or malformed response envelopes.
/v1/mcp/mcp-initialization-lifecycle
An agent that implements an MCP peer needs evidence of operations issued before the supplied initialization handshake completes.
/v1/mcp/mcp-progress-token-lifecycle
An agent that consumes MCP progress needs counts of unknown reused completed or non-increasing progress tokens.
/v1/api/http-multipart-framing
An agent that constructs an HTTP multipart request needs evidence of incomplete boundaries malformed header framing and missing part disposition.
/v1/api/http-chunked-framing
An agent that constructs a chunked HTTP message needs evidence of truncated chunks incorrect byte counts and data after the terminating trailer section.
/v1/api/http2-flow-control-trace
An agent that replays HTTP2 DATA and WINDOW_UPDATE events needs counts of window exhaustion invalid increments and overflow.
/v1/api/oauth-pkce-flow-correspondence
An agent that reproduces an OAuth authorization-code exchange needs evidence that callback state code redirect binding or S256 challenge disagree.
/v1/commerce/variant-combination-completeness
An agent that imports a configurable catalog needs missing Cartesian option combinations counted without publishing variant identifiers.
/v1/inventory/inventory-movement-balance
An agent that closes a stock period needs opening balance, signed movements, and closing balance reconciled including transient negative stock.
/v1/inventory/inventory-expiry-picking-order
An agent that applies a declared first-expiry-first-out policy needs pick steps that bypass still-available earlier-expiry lots measured.
/v1/inventory/packaging-conversion-consistency
An agent that merges packaging definitions needs contradictory conversion equations across indirect unit paths detected.
/v1/commerce/coupon-selection-conflict
An agent that applies a supplied promotion policy needs selected coupon pairs and exclusive groups that violate that policy counted.
/v1/commerce/promotion-threshold-order
An agent that configures sequential promotions needs rules whose minimum-spend eligibility changes between original and running subtotal measured.
/v1/inventory/inventory-kit-substitution-feasibility
An agent that accepts substitutable component demand needs a maximum-flow allocation proving whether all demanded units can be fulfilled together.
/v1/shipping/shipping-zone-prefix-resolution
An agent that imports a textual routing table needs destinations with no longest-prefix zone or conflicting tied zones measured.
/v1/calendar/calendar-exception-reconciliation
An agent that exports a recurring calendar needs the published finite occurrence set reconciled after explicit exclusions and single-occurrence replacements.
/v1/calendar/calendar-offset-duration
An agent that imports appointment spans needs declared elapsed duration reconciled against offset-aware instants and wall-clock duration differences measured.
/v1/calendar/calendar-resource-capacity
An agent that publishes a shared-resource calendar needs weighted concurrent booking demand compared with a declared capacity using half-open intervals.
/v1/calendar/calendar-recurrence-set-position
An agent that expands positional recurrence rules needs each supplied period selection checked against positive and negative BYSETPOS indexes.
/v1/workflow/workflow-compensation-coverage
An agent that audits an aborted saga trace needs successful effects lacking one matching compensation and compensation-order deviations measured.
/v1/workflow/workflow-definite-assignment
An agent that publishes a finite branching workflow needs variable reads that lack a definition on all reachable incoming paths identified by fixed-point-free DAG dataflow.
/v1/workflow/workflow-exclusive-join-deadlock
An agent that imports a workflow needs all-of joins requiring members from distinct arms of an explicit exclusive fork detected.
/v1/workflow/workflow-fanout-amplification
An agent that caps workflow execution counts needs propagated invocation counts across multiplicative all-fire edges compared with per-node limits.
/v1/inquiry/offer-inquiry-handoff
An agent that preserves a boiler or HVAC quote promise needs to know which service-labelled inquiry links end at a static inquiry form.
/v1/trade/shk/shk-intent-route-separation
An agent that separates SHK maintenance, breakdown and installation requests needs declared intent routes compared with the static intent selector at shared targets.
/v1/site/site-canonical-graph
An agent that repairs canonical relations needs non-self canonical cycles and failed targets inside one bounded retrieved page set.
/v1/cms/cms-fractional-rank-insertion
An agent that inserts sibling content needs the finite variable-length rank namespace between two supplied ranks counted before writing new keys.
/v1/cms/cms-publish-tree-gating
An agent that publishes hierarchical content needs supplied visibility claims reconciled with all ancestor publication flags and explicit time windows.
/v1/cms/cms-permission-inheritance
An agent that exports role policies needs claimed resource permissions reconciled with transitive role inheritance and a caller-declared deny-overrides rule.
/v1/cms/cms-plural-case-coverage
An agent that exports pluralized message contracts needs witness counts using category fallback rather than an explicit numeric or plural-category case.
/v1/cms/cms-richtext-mark-crossing
An agent that migrates range-based rich text needs strictly crossing annotation pairs counted before converting them to nested markup.
/v1/cms/cms-edit-delta-consumption
An agent that imports a content edit delta needs source cursor consumption and claimed resulting code-unit length reconciled without exposing inserted text.
/v1/cms/cms-nested-set-adjacency
An agent that imports a nested-set content tree needs integer boundary nesting and nearest-enclosing parent indexes reconciled with the supplied adjacency representation.
/v1/feeds/feed-atom-tombstone-reconciliation
An agent that merges supplied Atom entries and tombstones needs the visible identifier set reconciled after comparing update and deletion instants.
/v1/feeds/feed-paged-archive-consistency
An agent that publishes an archived feed needs its explicit oldest-to-newest archive inventory reconciled with prev-archive next-archive and current pointers.
/v1/workflow/workflow-bisimulation
An agent that replaces a finite labelled workflow needs whether the old and new initial states remain related under greatest branching-step matching with final-state observations.
/v1/workflow/workflow-language-inclusion
An agent that changes a deterministic event contract needs whether every accepted old trace is still accepted by the new contract and the shortest counterexample length.
/v1/workflow/workflow-petri-capacity
An agent that models a concurrent token workflow needs an explicit reachable marking that exceeds a declared place capacity or exhaustive confirmation within a finite exploration budget.
/v1/workflow/workflow-join-semilattice-laws
An agent that publishes a finite merge policy needs exhaustive associativity commutativity and idempotence counts over its explicit binary operation table.
/v1/workflow/workflow-monotone-transform
An agent that uses an explicit information order needs a supplied transfer table checked for order reversals before applying iterative dataflow.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://detect.halowerk.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.