Protocol

Agent Protocol

Autonomous agents with KYA-scoped authorization — origination agents, monitoring agents, settlement agents — operating under EIP-7702 ephemeral delegation with hierarchical governance.

Key figures


Agent types
3
Authorization model
Hierarchical
Execution
EIP-7702
Transaction throughput
1000+/day

How it works

From authorization to autonomous execution.

1

KYA credential issuance

Agent receives scoped authorization via KYA credential — defining corridor, instrument type, ticket size limit, and counterparty whitelist.

2

Oracle data ingestion

Agent pulls real-time oracle data — commodity prices, collateral verification, KYC status — to evaluate financing opportunities autonomously.

3

Ephemeral delegation

EIP-7702 grants single-transaction execution authority. Agent computes advance rate, verifies credentials, and executes the receivable purchase atomically.

4

Monitoring and settlement

Post-origination agents continuously survey collateral, trigger margin calls on covenant breach, and execute atomic DvP settlement on maturity.

Capabilities

Autonomous agents with institutional-grade controls.

KYA-scoped authorization

Every agent operates within a cryptographically enforced scope — corridor, instrument, size limit, counterparty list. No out-of-scope execution possible.

Hierarchical governance

Caviar governance → corridor entity → instrument desk → transaction agent. Each level delegates downward with narrowing scope and increasing specificity.

Ephemeral delegation

EIP-7702 grants single-transaction authority that expires after execution. No persistent private key exposure. No standing authorization to exploit.

Persistent smart accounts

ERC-4337 accounts for automated programs — recurring monitoring, scheduled settlements, continuous collateral surveillance — with account abstraction.

Agent slashing for misconduct

Agents post stake bonds. Misconduct — executing outside scope, submitting false data, front-running — results in automatic slashing and credential revocation.

Multi-corridor deployment

Same agent architecture deployed across Singapore, DIFC, East Africa, and Latin America corridors. Corridor-specific configuration, universal execution layer.

Comparison

Traditional vs. Caviar

TraditionalCaviar
Execution modelHuman traders with manual approvalsAutonomous agents with KYA-scoped delegation
AuthorizationRole-based access, static permissionsHierarchical, cryptographically enforced, per-transaction
SettlementT+2 to T+5 manual reconciliationAtomic DvP in seconds via settlement agents
MonitoringPeriodic manual reviewsContinuous autonomous collateral surveillance

Use cases

Real-world applications

Electronics APF origination

Origination agents autonomously evaluate Tier-2 PCB suppliers against Foxconn confirmed payables — pulling ERP oracle data, verifying KYA credentials, executing purchase in seconds.

Singapore–VietnamOriginationAPF

Commodity collateral monitoring

Monitoring agents poll AIS vessel tracking, warehouse cert oracles, and spot price feeds. Automatic margin call when LTV covenant breached, liquidation if cure period expires.

West AfricaMonitoringPXF

Cross-corridor settlement

Settlement agents execute atomic DvP across corridors — USDC disbursement against tokenized receivable transfer, with ZK-DvP for high-value transactions.

Multi-corridorSettlementDvP

Deploy autonomous agents.

Start with origination agents in a single corridor. Scale to multi-agent coordination as trust builds.