Resource access. Identity. Compliance.
The independent Resource Access Gate handles resource access. AI-IAM returns ALLOW / DENY / STEP_UP within a scoped enterprise deployment. The Compliance Engine returns PASS / WARN / FLAG / BLOCK.
Evaluate resource access, supported identity context, and query or content compliance through explicit, ordered runtime stages.
The independent Resource Access Gate handles resource access. AI-IAM returns ALLOW / DENY / STEP_UP within a scoped enterprise deployment. The Compliance Engine returns PASS / WARN / FLAG / BLOCK.
Accept query or content, jurisdiction, agent identity, PII or data classification, and supported agent_role / resource_tags.
Independently evaluate resource_tags with agent_role at the resource-access boundary, before any identity or content evaluation.
Check agent identity, status, jurisdiction, clearance, and rate budget; return ALLOW, DENY, or STEP_UP. Available only within a scoped enterprise deployment.
Classify query or content, match shipped rules, and return PASS, WARN, FLAG, or BLOCK with the judge result.
Write request_id, query hash, optional IAM effect, classification, results, prev hash, and chain hash.
Evaluate resource_tags with agent_role as an independent resource-access boundary. This stage runs first.
Check agent identity, status, jurisdiction, clearance, and rate budget; return ALLOW, DENY, or STEP_UP. This is a reference implementation available within a scoped enterprise deployment, not the default path of the current public API.
Evaluate query or content and policy matches; return PASS, WARN, FLAG, or BLOCK with classification and judge result.
Link each record with prev hash and chain hash for cryptographic continuity after the compliance decision resolves.
Activate pre-built packs by regulation, jurisdiction, and industry, then layer organization-specific requirements without changing application code.
HIPAA-aware, GDPR, APPI, LGPD, PIPA, PIPEDA, and cross-border data handling profiles.
EU AI Act, NIST AI RMF, model-use restrictions, human oversight, disclosure, and risk-class controls.
Healthcare, financial services, legal, telecommunications, and enterprise data-handling profiles.
Managed control plane and runtime endpoints for the fastest path to production.
Keep processing within your cloud account and approved regional boundary.
Run the enforcement plane inside your private network alongside regulated workloads.
Operate without external network dependency for restricted and high-assurance environments.
Each stored record is tamper-evident and hash-chained through the delivered evidence fields.
request_id and query hash identify the stored request without claiming additional context fields.
IAM effect when agent_id is provided, classification, compliance result, and judge result.
prev hash links the prior record; chain hash records the current chain value.
Submit supported query or content and consume the separate runtime results.
Submit supported query or content and runtime context from Python services.
Submit supported query or content and runtime context from JavaScript services.
Connect existing model traffic through the documented integration path.
Choose one production workflow. We will help map the supported inputs, integrate enforcement, and validate the delivered evidence fields.