AI Jurisdiction Demo

⚠️ Demo Mode - Do Not Use Real Personal Information

This is a public demo. Never enter real names, addresses, SSNs, or any actual personal data. Use the example test data provided below to copy and paste.
 
 💡 What you're seeing: Different US states have different data protection laws. Maryland's MODPA requires "strict necessity" - blocking SSNs and precise addresses for general chat. Colorado's AI Act requires transparency disclosures. SASI automatically applies the right rules based on user location.

SASKI Jurisdiction Demo
Sends user text to SASKI Hosted API and shows what would be forwarded to an LLM (message_for_llm), plus evidence metadata. Developer demo only.
Demo is rate-limited (10 requests/hour/IP). For production access, contact [email protected].
Message
Tip: use the pre-filled tests below to quickly validate redaction behavior.
Mode (optional override)
If set, the gateway will only honor it when it is permitted by the tenant’s allowed_modes.
Jurisdiction (demo selector)
This demo sends the selection in the JSON request body under metadata.userJurisdiction.
Action
Jurisdiction Applied
Mode Used
Mode Source
message_for_llm
Evidence block (JSON)
Evidence is designed to be verifiable (hashes + signature). This demo renders what the API returns.
Compliance Decisions (Why each field was blocked/redacted)
Pulled from evidence.compliance_decisions. Jurisdiction blocks take priority over mode redaction.
Field Type Action Reason
Jurisdiction comparison (what is blocked / required)
This is a UI summary of the resolver rules. The authoritative source is the evidence returned by SASKI API under evidence.jurisdiction_decision.
Jurisdiction Blocks SSN Blocks Govt ID Blocks Insurance Blocks Precise Location Transparency Disclosure Strict Necessity Crisis Hotline Bias Monitoring Right to Explanation

🚀 For Developers: Integration Overview

REST API:

5 minutes minutes of programmin for first call

  → Production integration: 1-8 hours (depending on logging, auth, evidence storage)
  → No installation. Call our endpoint with your API key.

Python SDK:

10 minutes of programming for basic setup

  → Production deployment: 2-4 hours (air-gapped option for HIPAA/enterprise)
 → pip install sasi-sdk (one command, then configure enforcement path)

MCP Integration (Agentic AI):

Coming Q2 2026

  → Governed tool surface for multi-step AI agents

  • SASI runs as a pre-model enforcement layer. When properly integrated, bypass becomes
  • detectable and non-compliant. Includes automatic jurisdiction compliance for 50+ US
  • states + EU, cryptographic evidence for audits, and fail-closed safety.