Skip to main content
Industry verticals

One Agentic Gateway. Domain-specific workflows.

ClawQL modularization v2.1 defines opt-in vertical packages that share security, memory, audit, and the IDP pipeline. Lending and real estate have shipped reference workflows today; surveillance and government audit/outcome surfaces are available with domain packages progressing; healthcare, legal, and insurance follow.

Read modularization v2.1

Explore by industry

clawql-lending

Partial — samples shipping

Lending

Agent-native lending and mortgage operations

Mortgage, auto, BNPL, payday, and commercial lending share the same document-heavy intake problem: borrowers submit heterogeneous PDFs, underwriters re-ask for the same conditions, and API integrations sprawl across LOS, credit, and document vendors. Modularization v2.1 defines clawql-lending as five sub-verticals on one gateway — MortgagePlugin, AutoPlugin, BNPLPlugin, PaydayPlugin, and CommercialPlugin — plus shared UnderwritingPlugin and CompliancePlugin for Reg Z, ECOA, and fair-lending guardrails. Today you can run the lending Docker Compose stack and the shipped W-2 reference pack; full LOS tool registration ships with the vertical package.

View use cases

real-estate transaction samples

Title + PSA + FSBO offer workflows · CRM-agnostic

Real estate

The intelligent document layer for brokerages and FSBO sellers.

Residential transactions generate dozens of PDFs per deal — purchase agreements, buyer offers, title commitments, appraisals, HOA disclosures — often split across a brokerage CRM (pipeline), cloud storage (folders), and a transaction platform (e-sign). FSBO sellers get the same PDFs without a coordinator. ClawQL is the intelligent document layer: shipped reference packs for title commitments, PSAs, and FSBO buyer offers demonstrate parse → classify → extract → HITL → vault threading with deal_id metadata. Financed purchases can reuse clawql-lending mortgage tools; Coneshare VDR closes the loop when external parties access sensitive files.

View use cases

clawql-surveillance

Audit infrastructure available · hardware attestation per vendor

Surveillance

The audit layer that makes camera footage trustworthy as evidence.

Courts are beginning to ask a question that no major surveillance camera vendor can currently answer: how do you know this footage is what the camera originally recorded, unaltered? The authentication gap is structural. No major vendor publicly documents cryptographic hashing of footage within camera hardware at capture, Merkle-chained audit logs, external immutable anchoring of chain of custody records, or mandatory case number enforcement on queries. This means footage authentication depends on vendor assertion rather than independently verifiable mathematical proof — a standard that FRE 901(b)(9) and Daubert scrutiny are beginning to expose. The practical consequences are compounding. Active federal litigation is establishing authentication standards at the circuit level. Public defenders equipped with Daubert motions citing the industry's documented ~10% misidentification error rate are challenging footage reliability in volume. Cities are writing cryptographic integrity requirements into new RFPs after reviewing the model contract language published at github.com/danielsmithdevelopment/surveillance-evidence-integrity. Contracts are being lost not on price or features but on the inability to answer a chain of custody question that the market is now asking. clawql-surveillance gives camera vendors the audit infrastructure to answer that question — and to sign the contract language that wins the next procurement cycle. The framing that works: body cameras became a trust multiplier for law enforcement not because they surveilled officers, but because they made evidence trustworthy and protected good officers from false accusations. The same logic applies here. Cryptographic chain of custody serves defendants who need to challenge unreliable evidence, officers who need their legitimate work to be unimpeachable in court, and agencies that need to demonstrate their surveillance programs meet the standards courts and cities are moving toward. The audit layer protects everyone except the people misusing access — and that is the point.

View use cases

clawql-government

Outcome audit infrastructure available · domain package planned

Government

Outcome accountability for the programs voters fund.

California has issued about $196 billion in general obligation bonds since 2000, with roughly $81.8 billion still outstanding and nearly $8.6 billion in debt service this fiscal year alone. Schools, water systems, climate programs, housing — voters approved them all. The state can track how bond dollars are spent. It cannot consistently answer whether those investments achieved the outcomes voters were promised. Spending accountability and outcome accountability are not the same thing. Governments have built robust infrastructure for the first and almost nothing for the second. That is not a California problem. It is a government technology problem with a precise technical solution: define measurable outcomes at authorization, record immutable baselines before programs begin, and maintain append-only, externally anchored outcome records that any qualified party can verify without trusting the program being measured. clawql-government composes ClawQL's WORM audit, Merkle chaining, and Arweave anchoring into that outcome layer — the same architecture used for AI agent trails and surveillance evidence integrity, under a different authorization surface. The framing that works: financial audit has required immutable baseline records for decades. Outcome measurement deserves the same standard. Programs that cannot be measured cannot be found to have failed — and that incentive is why the infrastructure must push integrity outside the control of the party being measured.

View use cases

clawql-healthcare

Planned

Healthcare

HIPAA-aware clinical document processing.

Health systems and digital health vendors juggle unstructured clinical PDFs, HL7 v2 feeds, FHIR R4 bundles, and imaging studies — often with separate OCR pipelines, manual de-identification, and brittle point-to-point integrations. clawql-healthcare (modularization v2.1) registers domain tools — fhir_parse, hl7_extract, dicom_analyze, ehr_structure, deidentify, medical_image_analyze, clinical_note_structure — on the same Agentic Gateway as search, execute, memory, and audit. PHI never enters vault notes or Onyx indexes without passing Stirling redaction in run_idp_pipeline; hitl_enqueue_label_studio routes ambiguous coding or medication extractions to clinical reviewers before downstream persistence.

Notify me when it ships

clawql-legal

Planned

Legal

Contract intelligence with privilege-aware automation.

Law firms and in-house teams drown in PDF data rooms, discovery productions, and contract versions — while ethical walls and privilege rules forbid casual indexing of client material. clawql-legal registers clause_extract, risk_flag, precedent_search, redact_privilege, timeline_generate, brief_draft, motion_draft, and filing_validate on the shared Agentic Gateway. Documents pass Stirling and redact_privilege before archive or knowledge_search_onyx; memory_recall with graph depth surfaces prior matter notes without cross-contaminating walled teams. Human attorneys remain in the loop — agents handle retrieval, first-pass organization, and citation gathering.

Notify me when it ships

clawql-insurance

Planned

Insurance

Claims and policy intelligence on one MCP surface.

Insurance operations span FNOL intake, adjuster reports, policy endorsements, loss runs, and SIU referrals — often across legacy policy admin systems, document portals, and Slack war rooms. clawql-insurance registers claim_extract, policy_analyze, loss_run_reconcile, fraud_flag, payout_validate, and coverage_check on the ClawQL gateway. The same IDP pipeline parses unstructured claim packets; extract_document returns grounded policy limits and injury fields; fraud_flag composes with memory_recall of prior claim patterns. Merkle audit trails (modularization v2.1) anchor claim-processing provenance for carrier compliance teams.

Notify me when it ships

clawql-education

Planned

Education

Faculty productivity and LMS-connected agents.

Faculty and instructional designers repeat the same semester setup — syllabi, rubrics, module scaffolding, and LMS publishing — while FERPA constraints limit what can live in chat logs or third-party SaaS. clawql-education registers syllabus_generate, rubric_create, assignment_generate, progress_analyze, lms_sync, and content_scaffold with connectors for Canvas, Moodle, and Blackboard. Approved content lands in the vault via memory_ingest; student PII is redacted before persistence; search discovers LMS REST operations instead of pasting entire OpenAPI exports. Role-scoped ATR (planned) separates faculty-facing tools from student-facing agents.

Notify me when it ships