What Katara does not do

Three rules shape the system. They are enforced in code and covered by tests that must keep passing.

Katara never holds your funds. USDC stays in an account only your passkey controls, and the prepaid balance in the settlement contract can only ever be debited for replies you received or paid back to you. Nobody at Katara can move it anywhere else. Withdrawals pay out after a one-hour delay so replies in flight are charged first; nothing is ever served against money that is not already in the contract.

Katara never stores your prompts or replies. The chat app keeps your conversations for you, under your account. The marketplace itself records tokens, price, timing, and who served the request, never the content. Providers see the request they serve and nothing about who sent it.

Providers never learn who you are. Requests reach a provider under a job ticket, not an account. The provider is paid from the settlement contract, not by you.

What is verified

Every reply is backed by a receipt the provider signs. The router checks the receipt against what it observed, token by token, before anything is settled. A receipt that does not match is not paid, and the provider is struck.

Security work

The contracts and services were reviewed against adversarial scenarios before the public test, with every high-severity finding fixed. Summaries will be published here as they are prepared for outside readers. Report a vulnerability to [email protected].