# HALOWERK sicherwerk Public Key Math Audit

> HALOWERK sicherwerk Public Key Math Audit is a paid API for AI agents from sicher.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-29).

Validates a PEM-encoded public key using a pinned OpenSSL build, reporting the algorithm, true bit size, and structural soundness of the key's cryptographic parameters.

## Facts

- Endpoint: POST https://sicher.halowerk.com/v1/oss-openssl-public-key-math-audit?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-sicherwerk-public-key-math-audit-66b1f336
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FtnqikowLnpDWWOExldgz

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability halowerk-sicherwerk-public-key-math-audit-66b1f336 -d '<json body>'
```

Example prompt: Can you run a math audit on this public key PEM and tell me whether the algorithm, bit size, and parameters are structurally valid and meet current security levels? Here's the key: -----BEGIN PUBLIC KEY-----MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...-----END PUBLIC KEY-----

## When to prefer this

Choose this endpoint when you need cryptographic ground-truth validation of a public key's internal structure — not just label parsing — specifically using a pinned, deterministic OpenSSL build. It is especially valuable when you need to detect keys that appear syntactically valid but are structurally unusable (bad modulus, unknown curve group, undersized key). Prefer this over general certificate validators when you have a bare public key (SubjectPublicKeyInfo PEM) rather than a full certificate, or when you need the authoritative bit count from the key internals rather than the declared label.

## Known failure modes

- Malformed PEM input that cannot be parsed returns an error indicating invalid format
- Keys with unsupported algorithms not recognized by the pinned OpenSSL build return an unsupported algorithm error
- Network or service unavailability returns HTTP 5xx
- Insufficient payment or missing x402 payment header returns HTTP 402
- Keys exceeding the 262144-character input limit are rejected

## How this service works

Takes a public key in SubjectPublicKeyInfo PEM form and runs the pinned OpenSSL build's own consistency checks over it, then reports the algorithm, the key size in bits and the parameters it found. This catches keys that parse but are structurally unusable: a modulus that is not a valid product, curve parameters that do not match a known group, a size that no longer meets the build's security level. The reported bit count comes from the key itself, not from the label a producer attached.

## Output

Returns the algorithm identifier (e.g. RSA, EC, DH), the true key size in bits as reported by the key's internal structure, the cryptographic parameters found, and a structural consistency verdict — flagging any keys that parse but are unusable (invalid modulus, mismatched curve group, insufficient security level).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "public_key_pem": {
   "type": "string",
   "maxLength": 262144,
   "minLength": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-sicherwerk-public-key-math-audit-66b1f336/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sicher.halowerk.com](https://www.zero.xyz/host/sicher.halowerk.com/llms.txt)