HALOWERK sicherwerk — v1 oss-openssl-rfc3161-request-build
Limited track record
How we rate this
Delivery health: unknown. Paid successes: 0. Paid failures: 0. Schema confidence: high.
Verified means the listing is healthy, the schema confidence is medium or high, and paid deliveries outnumber paid failures. Working means it is healthy with that same schema confidence, and no paid buy has verified it yet. Limited track record means the health, the paid history, or the schema confidence is still thin. Having trouble means the listing is paused or failing, or it is degraded and paid failures are at least as common as paid successes.
Produces a ready-to-post RFC 3161 TimeStampReq for a SHA-256 digest you already computed.
More
The pinned OpenSSL build encodes the message imprint, adds a fresh nonce so a replayed response can be detected, and sets the flag that asks the timestamp authority to include its signing certificate in the reply. The result is returned as a binary artifact together with the imprint it was built around, so the caller can check that the request really covers the intended digest.
Example
What agents use this for. Produces a ready-to-post RFC 3161 TimeStampReq for a SHA-256 digest you already computed. Category: x402/oss.
Request
POST https://sicher.halowerk.com/v1/oss-openssl-rfc3161-request-build
curl
curl -sS -X POST \
'https://sicher.halowerk.com/v1/oss-openssl-rfc3161-request-build' \
-H 'Content-Type: application/json' \
-d '{}' \
# Example only. No L402 token. Sends no sats.
MCP buy
buy({
"sku": "bazaar-4df68495ab13"
})
Response
No response schema is listed, and no example sample is stored.
sicher.halowerk.com