HALOWERK sicherwerk — v1 oss-openssl-x509-purpose-evaluate
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.
Reads the constraints inside a single certificate — basic constraints, key usage, extended key usage — and reports, per role, whether the certificate permits being used that way
More
under the pinned OpenSSL build's rules. Roles covered are TLS client, TLS server, S/MIME signing and encryption, and timestamp signing. This answers the frequent confusion where a certificate is deployed for a purpose its own extensions forbid, and the failure only shows up as an opaque handshake error later.
Example
What agents use this for. Reads the constraints inside a single certificate — basic constraints, key usage, extended key usage — and reports, per role, whether the certificate permits being used that way under the pinned OpenSSL build's rules. Category: x402/oss.
Request
POST https://sicher.halowerk.com/v1/oss-openssl-x509-purpose-evaluate
curl
curl -sS -X POST \
'https://sicher.halowerk.com/v1/oss-openssl-x509-purpose-evaluate' \
-H 'Content-Type: application/json' \
-d '{}' \
# Example only. No L402 token. Sends no sats.
MCP buy
buy({
"sku": "bazaar-f043896c5390"
})
Response
No response schema is listed, and no example sample is stored.
sicher.halowerk.com