Produce an EU AI Act Article 50 transparency record for a piece of AI-generated content and register it with LedgerProof. Provide EXACTLY ONE of artifact (the raw content; hashed locally, never uploaded) or precomputed_sha256 (a SHA-256 hex you computed yourself), plus the AI-system and deployer metadata. Mirrors the SDK's publishAiArticle50. Returns {sequence, entry_hash, verify_url, anchor_status}. anchor_status is ALWAYS 'pending' on issuance because Bitcoin anchoring is asynchronous (a daily Merkle root is written to an OP_RETURN, which costs a Bitcoin tx fee) — poll ledgerproof_check_anchor until it becomes 'anchored'. Do not issue on loose triggers.

Verify a LedgerProof receipt. Provide EITHER {sequence} (looks up the chain entry from the public verifier) OR {transparent_statement} (a SCITT Transparent Statement bundle, verified with the trust-minimized §7 algorithm: issuer COSE_Sign1 signature, RFC 9162 inclusion proof, Transparency-Service receipt signature, and an independent Bitcoin OP_RETURN check). For a Transparent Statement, returns {issuerSignatureValid, inclusionProofValid, receiptSignatureValid, bitcoinConfirmed, valid, recomputedRoot}. The Transparency-Service PUBLIC key (for the receipt signature) is loaded from LEDGERPROOF_TS_PUBLIC_KEY_HEX or fetched from {apiBase}/v1/scitt/ts-key; the Bitcoin txid is taken from the statement wrapper, the txid arg, or a /v1/scitt anchor lookup. SCITT verification requires the SDK's scitt module to be present in the installed build.

Check whether a receipt's daily Merkle root has been anchored to Bitcoin yet. Returns anchor_status ('pending' or 'anchored') and, when anchored, the Bitcoin txid, block height/hash, and Merkle inclusion proof. Agents should poll this with the receipt's sequence after issuance until anchor_status becomes 'anchored' (the anchor is batched daily, so this can take time).

Compute the SHA-256 (hex) of a payload using the SDK's hashing. PRIVACY: use this to obtain a precomputed hash so raw payloads never leave the machine — then pass the hash to ledgerproof_issue_receipt as precomputed_sha256. Over Streamable HTTP, issue_receipt REQUIRES precomputed_sha256 and rejects raw payloads, so hash locally first.