Automated Safety Checks

Every transaction screened.
Every counterparty verified.

Oris runs automated safety checks on every transaction before execution. The screening evaluates counterparty risk, sanctions exposure, and transaction patterns. If a check fails, the transaction is blocked. Your application receives a clear error code. No unsafe payment reaches the provider.

Pre-Transaction Pipeline
check Policy evaluation 3.2ms
check Counterparty screening 18ms
check Behavioral analysis 24ms
check Entity verification 31ms
CLEAR Total: 76ms
< 100ms
Screening Latency
Fail-Closed
Architecture
Pre-Tx
Screening
Veris
Powered By
Transaction Flow

Three steps. Sub-100ms.

01

Agent Calls Pay

Your agent calls agent.pay(). Oris receives the transaction request with the destination address, amount, and chain identifier.

agent.pay(
  to="0xA1b2...C3d4",
  amount=25.00,
  chain="base"
)
02

Safety Evaluation

The safety engine evaluates the counterparty address, the transaction amount, and the behavioral context against the agent's history. This evaluation completes in under 100 milliseconds.

check Counterparty screening
check Sanctions list check
check Behavioral baseline match
check Pattern analysis
03

Pass or Block

If the check passes, the transaction proceeds to your payment provider. If the check fails, Oris returns a structured error with the failure reason. The transaction never reaches the provider.

check_circle PASS: Forwarded to provider
block FAIL: Blocked with error code
shield Screening Results
Last 24h
1,847
Total Checks
1,841
Passed
6
Blocked
0x7a3f...9e21
Sanctions match (OFAC SDN)
BLOCKED
0xb2c1...4d8a
High-risk mixer interaction
BLOCKED
0xe4f9...2b7c
All checks passed
CLEAR
Avg latency: 76ms 99.7% pass rate
Transparency

Every screening result is visible

The Oris dashboard displays every screening decision in real time. Blocked transactions include the specific reason code, the matched risk indicator, and the counterparty address that triggered the block.

Pass rates, average latencies, and block reasons are aggregated over configurable time windows. Developers can drill into any individual screening result to see the full evaluation chain.

Architecture Principle

Fail-closed by default

The safety engine operates on a fail-closed principle. If the screening service is unavailable, transactions are blocked. If the evaluation times out, transactions are blocked. If any component in the safety pipeline returns an ambiguous result, the transaction is blocked.

This architecture guarantees that system failures produce safety rather than exposure. A degraded system will refuse transactions until full service is restored.

Failure Mode Responses
Screening service down BLOCKED
Evaluation timeout (>100ms) BLOCKED
Ambiguous risk result BLOCKED
Database connection lost BLOCKED
All systems operational, clean check ALLOWED
Coverage

What gets screened

person_search

Counterparty Risk

The destination address is checked against known risk indicators, sanctions lists, and behavioral patterns. Addresses associated with illicit activity are flagged before the transaction reaches your provider.

monitoring

Transaction Patterns

Unusual amounts, frequencies, or destinations trigger additional review based on the agent's behavioral baseline. The system compares each transaction against the agent's established norms.

hub

Cross-Chain Context

The screening engine considers the agent's activity across all 10 supported blockchains, providing a complete risk picture. A single-chain view is insufficient for modern threat detection.

security

Powered by Veris

The safety screening engine is powered by Veris, the stablecoin compliance infrastructure built by the same team. Veris indexes 10 blockchains in real time, maintains 70,000+ labeled addresses, and runs 15 ML models for pattern detection.

This infrastructure runs silently behind every Oris transaction. Your agents benefit from enterprise-grade compliance without any configuration.

Powered by Veris arrow_forward
10
Blockchains
70K+
Labels
15
ML Models

Safety built into every transaction

Automated safety checks are included in every Oris plan. No configuration required. Every agent payment passes through the screening pipeline from the first API call.