Upload a PDF to ActaLumen for compliance verification. The server applies organization-configured PII redaction before storage — the agent will only ever see redacted content in subsequent calls. Returns a document ID; the document is PROCESSING until embeddings finish (poll get_document for status=READY).

Get a document's status and metadata. Use this to poll after upload — call start_verification or chat_with_document only when status is READY. Status values: PROCESSING (embeddings running), READY (queryable), FAILED.

List documents in the organization. Use this to find an existing document ID by name instead of re-uploading.

List compliance criteria templates available to the organization (e.g., 'SOC2 Vendor', 'GDPR DPA'). Call this before start_verification to find the right templateId. Each template encodes a checklist of criteria a document is verified against.

Run compliance verification on a document against a template (or ad-hoc criteria). Returns a jobId; the job runs async — poll get_verification until status is 'completed'. Requires the API key to have the 'verify' scope.

Fetch verification job status and (when complete) the full report with per-criterion findings, citations, and pass/fail summary. Poll roughly every 5–10s after start_verification.

Ask a grounded question about one or more documents. Returns an answer with citations into the document. PII in source documents has already been redacted server-side, so answers cannot leak redacted data.

Check the organization's current plan, quota, and remaining allowance for documents, verifications, chat messages, and generated media. Call before kicking off expensive batch operations.