Kalyx / technical field guide

How KALYX works

KALYX is a DEVNET candidate for paid, citation-backed context retrieval. A gateway can answer a free relevance probe or issue a bounded HTTP 402 quote; a client verifies the quote before it can fund an escrow.

01 /

The problem and the proposed boundary

An agent needs a small, attributable piece of context, not a human subscription flow.

KALYX separates discovery from payment. The gateway searches its indexed content and returns no relevant context without payment, or a 402 challenge that names a price, publisher wallet, content binding, and node address.

A relevant result is not an authorization to spend. The consumer supplies a price cap and may also supply a session budget. The reviewed SDK is designed to reject an invalid quote before it signs a funding transaction.

02 /

Lifecycle: probe, fund, retrieve, reconcile

Funding, delivery, and settlement are related but different states.

Kalyx retrieval and verification architectureA publisher supplies content and its source binding to the gateway. An AI agent queries that gateway and receives a quote or content. The SDK is designed to verify and fund a Solana escrow; the gateway checks chain state. Funded DEVNET integration is currently blocked.AI agentPython SDKGatewaymatch · quote · servePublishersource + content hashSolana escrowfund · settle · reconcilequeryquote / serveSDK funds01 / DISCOVERY & RETRIEVAL02 / STATE CHECKSDashed paths: intended funded flow · DEVNET gate unresolved
Intended lifecycle. Dashed payment paths remain gated; this diagram is not a record of a live transaction.
  1. Agent -> Gateway: POST /v1/query
  2. Gateway -> Agent: free no_context_found OR HTTP 402 quote
  3. Agent -> Solana DEVNET: signed create_and_fund after local checks
  4. Agent -> Gateway: POST /v1/retrieve with signature and escrow address
  5. Gateway -> Agent: persisted answer, provenance, and pending/confirmed settlement state
  6. Trusted settlement authority -> Solana DEVNET: later settlement instruction

The gateway is responsible for relevance, delivery, and evidence checks. The chain program is intended to own escrow state transitions and transfer rules. The client is responsible for protecting its key and refusing a quote that exceeds its configured limits.

After an ambiguous network or retrieval failure, preserve the original transaction signature and escrow address. Do not create a second payment blindly; reconcile the actual chain state and use the authorized recovery path.

03 /

Trust boundaries

A receipt, a gateway answer, and an on-chain transaction prove different things.

Trust boundaries
BoundaryWhat is checkedWhat is not established
Gateway relevance and deliveryThe gateway can return a quote, content, and provenance fields.Relevance scoring and retrieved text are not independently trusted facts.
Consumer authorizationThe client can verify cluster, program, node, price, budgets, and confirmation before retrieval.A local SDK check does not prove a deployed program matches the reviewed source.
Escrow and settlementA confirmed, program-scoped funding or settlement instruction can be independently inspected.A submitted transaction, closed escrow, or receipt alone does not prove payout.
Receipt signatureEd25519 verification binds the signed receipt message to a trusted gateway key.It does not prove factual accuracy, publisher rights, or recipient balance change.
04 /

DEVNET status and limits

The fresh DEVNET deployment has demonstrated real funding, verified delivery and publisher settlement.

The current program is BqM4pbj21g6SfXrt8Tkae1E4hmctN7jDmPyRctPcPaWg. Its owner and distinct dedicated settler are verified on devnet; every displayed live transaction can be checked independently. The historical GKaQ7L program and its recorded funding/refund evidence remain separate.

The gateway uses real devnet RPC verification. Isolated tests remain implementation evidence, while live funding and EscrowSettled instruction, event and recipient balances provide payment evidence. Devnet test money only; unaudited protocol, trusted gateway/settler and single admin arbiter.

THE JUDGE PATH / FOLLOW THE CONTEXT

From the idea to the evidence.

Continue to evidence

The demo uses real devnet transactions. Content integrity and a receipt signature do not establish payout. Live availability and blocked steps are shown explicitly.