Getting Started

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.

NOTEThe on-chain program kalo_protocol is deployed at 7gvg3hFxPbtSkxjCoPHEXMPSen7X9H21y96JPVBbf47S on Solana. Every shielded lock, mandate check, and Ed25519 receipt verification executes on L1.

Four actors

ActorRolePrimary surface
SponsorCreates Privacy Rings, shields and unshields funds, issues and revokes Authority Mandates, holds the master viewing key`/app`, `/app/mandates`
AgentHolds a delegated Ed25519 key bound to an active mandate and pays HTTP 402 endpoints through kalo.fetch()`@kalo/sdk`
ProviderRuns 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`
AuditorHolds 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:

  1. 402 Challenge: The agent calls kalo.fetch(url). The SDK strips PII headers in under 6ms p99 and sends the request. The provider returns HTTP 402 with requestHash, a shielded priceCommitment, amountBaseUnits, providerAddress, and enclavePubkey.
  2. Shielded Lock: The SDK builds and submits lock_sealed_402. The program checks that the AuthorityMandate is active, unexpired, within per-call and epoch caps, and permits the provider's service category bit. It records the UTXO nullifier in a NullifierSet PDA and creates a SealedEscrow PDA in Locked state.
  3. TEE Receipt: The agent retries the request with the X-Kalo-Escrow header. The provider verifies the locked SealedEscrow, runs the workload inside its Confidential Compute enclave, and signs SHA256(escrow_pda || request_hash || output_hash) with its registered Ed25519 enclave key.
  4. Atomic Release: settle_with_receipt verifies the Ed25519 precompile instruction against EnclaveRegistry, releases the payout from ring_vault to the provider and the protocol fee share to the KALO launch wallet, and updates ReputationAccumulator.
ts
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

Confidential commerce infrastructure for autonomous software.

Shielded treasuries, scoped mandates, and receipt-bound HTTP 402 settlement on Solana L1.

Open consoleRead the docs