Lookproof CSR Decode

Use this endpoint when an AI agent needs to inspect or validate a CSR before forwarding it to a certificate authority, when a pipeline must assert key strength or algorithm compliance, or when a security reviewer wants to audit subject and SAN fields without standing up OpenSSL locally. Prefer this over generic TLS-check endpoints (which probe live servers) because it works entirely offline from the raw PEM text, requires no domain access, and is deterministic. Best when the agent already has the CSR PEM in hand.

• Malformed or truncated PEM returns a 4xx error with a parse failure message
• PEM block is present but contains a certificate or private key instead of a CERTIFICATE REQUEST — returns error indicating wrong PEM type
• CSR exceeds 16 384-character limit — returns 422 validation error
• Missing or empty pem field — returns 422 unprocessable entity
• Valid PEM but internally corrupted ASN.1 structure — returns decode error