Overview
What Kalo is, the four actors, and how Sealed 402 Settlement works on Solana L1.
What Kalo does
Kalo is a Solana protocol for confidential agent commerce. It pairs shielded treasuries built on Solana Privacy Rings and versioned spending mandates with hardware-attested settlement over HTTP 402.
Balances, payment amounts, request payloads, and counterparty graphs stay encrypted on-chain. Sponsors and authorized auditors inspect activity locally with viewing keys, while service providers accumulate Sybil-resistant fulfillment history without exposing revenue or customer lists.
kalo_protocol is deployed at 7gvg3hFxPbtSkxjCoPHEXMPSen7X9H21y96JPVBbf47S on Solana. Every shielded lock, mandate check, and Ed25519 receipt verification executes on L1.Four actors
| Actor | Role | Primary surface |
|---|---|---|
| Sponsor | Creates Privacy Rings, shields and unshields funds, issues and revokes Authority Mandates, holds the master viewing key | `/app`, `/app/mandates` |
| Agent | Holds a delegated Ed25519 key bound to an active mandate and pays HTTP 402 endpoints through kalo.fetch() | `@kalo/sdk` |
| Provider | Runs an API, data feed, or private AI model inside Intel TDX or AMD SEV-SNP and gates routes with kaloGate() | `/app/providers`, `/docs/guides/gate-api-402` |
| Auditor | Holds a read-only viewing key attached to a Ring to decrypt balances and settlement amounts locally | `/docs/guides/auditor-keys` |
Sealed 402 Settlement
Every paid call runs through one four-stage atomic loop:
- 402 Challenge: The agent calls
kalo.fetch(url). The SDK strips PII headers in under6msp99 and sends the request. The provider returns HTTP402withrequestHash, a shieldedpriceCommitment,amountBaseUnits,providerAddress, andenclavePubkey. - Shielded Lock: The SDK builds and submits
lock_sealed_402. The program checks that theAuthorityMandateis active, unexpired, within per-call and epoch caps, and permits the provider's service category bit. It records the UTXO nullifier in aNullifierSetPDA and creates aSealedEscrowPDA inLockedstate. - TEE Receipt: The agent retries the request with the
X-Kalo-Escrowheader. The provider verifies the lockedSealedEscrow, runs the workload inside its Confidential Compute enclave, and signsSHA256(escrow_pda || request_hash || output_hash)with its registered Ed25519 enclave key. - Atomic Release:
settle_with_receiptverifies the Ed25519 precompile instruction againstEnclaveRegistry, releases the payout fromring_vaultto the provider and the protocol fee share to theKALOlaunch wallet, and updatesReputationAccumulator.
import { KaloClient } from '@kalo/sdk'
const kalo = new KaloClient({
apiUrl: 'https://api.kalo.local',
agentPubkey: 'Agnt8x...9kPq',
ringAddress: 'Ring4m...2vTz',
defaultMandate: 'Mndt7r...4wLp',
defaultViewingKey: 'sponsor-master-vk-01',
})
const res = await kalo.fetch<{ signal: string }>('https://infer.kalo.local/v1/demo/infer', {
method: 'POST',
body: JSON.stringify({ prompt: 'Evaluate SOL basis spread' }),
})Settlement assets and token
Privacy Rings accept SOL, USDC, and any SPL or Token-2022 mint. USDC is the default pricing asset in the web console and demo provider because API and inference services price calls in USD.
Protocol fees on settled escrows fund the KALO buyback-and-burn loop. Full token parameters, fixed supply, and fee routing live on the KALO Token & Fee Burn page.
Where to go next
- Follow the Quickstart to create a Ring, issue a mandate, and settle your first HTTP 402 call.
- Read Core Concepts for the objects and state transitions behind each step.
- Browse the On-Chain Program Reference and `@kalo/sdk` API Reference for exact account layouts, PDA seeds, and method signatures.
- Open the Sealed 402 Console to run a live call and compare Public Chain View against Viewing Key View.