KAMIYO

What is KAMIYO?

KAMIYO is trust infrastructure for autonomous agents. When AI agents pay for services, funds are held in escrow until the service is delivered. If there's a dispute about quality, multi-oracle consensus determines a fair settlement. Agents build on-chain reputation through successful transactions.

How does escrow protection work?

When an agent requests a service, payment is locked in a Solana escrow PDA. The provider delivers the service, and the agent can release funds on success or trigger a dispute. Escrows have configurable time-locks and support SOL, USDC, and USDT.

What happens during a dispute?

Oracle panels score service quality from 0-100. The median score determines the refund percentage: 80-100% quality means full payment to provider, 65-79% means 35% refund, 50-64% means 75% refund, below 50% means full refund to agent. Settlement is automatic and on-chain.

How do I integrate KAMIYO?

Install @kamiyo/sdk from npm. Create an agent identity with stake collateral, then use createAgreement() to lock funds before requesting services. Call release() on success or dispute() to trigger oracle arbitration. The SDK handles all Solana transaction building.

What's the agent identity system?

Agents have PDA-based identities on Solana with stake collateral. Reputation scores update based on transaction outcomes and dispute history. Agents with poor track records can be slashed. This creates accountability for autonomous systems.

Is this compatible with x402?

Yes. KAMIYO provides escrow protection for x402 payments. Use @kamiyo/x402-client to wrap standard x402 requests with escrow creation and automatic dispute triggering based on SLA violations.

Which networks are supported?

The core protocol runs on Solana mainnet. The escrow program handles SOL and SPL tokens (USDC, USDT). For payment verification across other chains, KAMIYO integrates with x402 facilitators on Base, Ethereum, Polygon, Arbitrum, and Optimism.

How are oracles selected?

Oracle panels are drawn from a registered pool with stake requirements. Oracles must stake SOL as collateral against malicious voting. Consistent outlier votes result in slashing. Panel size is configurable per dispute.