
A budget your agentcannot exceed or reveal
Enforce an agent's spending cap on-chain while the cap, the balance and every settlement amount stay encrypted. The comparison happens inside the TEE; the chain only ever stores handles.
Built on
Every metered call leaves an operational diary.
Run a fleet of agents against metered APIs over x402 and the chain records it all in the open. Which agent is active, how often, against which vendor, for how much, and how much of its allowance is left. Anyone can read it. For a company that is a competitive leak before it is a privacy problem. The naive fix — don't enforce the budget on-chain — is worse: then the cap is a suggestion, and one compromised prompt drains the treasury.
Plain x402 settlement
Every field is public, and permanently linkable.
- from
- 0x91c4…7a20which agent
- to
- 0x5ef0…13bbwhich vendor
- value
- 1500 weiwhat it cost
- block
- 8421907exactly when
The same settlement on Kairos
One event. No addresses, no amount, only the epoch.
- event
- PrivateSettlementthat one occurred
- epoch
- 4which batch it joined
- amount
- sealednever emitted
- agent
- sealednever emitted
What is hidden, and what is not
Being precise about this matters more than any feature list.
Encrypted
Handles on-chain, decryptable only by permitted accounts.
- The treasury budget and what remains of it
- Each agent's per-call spending cap
- Each agent's cumulative spend
- The amount of any individual settlement
- Whether a settlement was authorized or rejected
Public
Visible to anyone reading the chain.
- That a settlement occurred, and in which epoch
- How many settlements a batch contained
- The relayer address that submitted the transaction
- The aggregate total of a closed epoch, once flushed
- The vault's existence and its owner
Known limitation, stated plainly
msg.sender is inherently public. Kairos routes every settlement through one gateway relayer, so on-chain all settlements share a sender and per-agent activity is not distinguishable — but the relayer itself is visible, and it learns what it relays.
How a payment moves
Individual debits never move funds on their own. That is what breaks the one-transaction-per-API-call trail.
Settle
The agent submits an encrypted amount. Two encrypted comparisons run inside the TEE: within cap, and within budget.
amount ≤ cap · budget ≥ amount
Authorize
An encrypted boolean cannot gate a require — reverting would leak the comparison. The contract debits the amount or debits zero, then publishes the outcome as an encrypted flag.
Nox.select(ok, amount, 0)
Accumulate
The debit joins an encrypted epoch total instead of moving money, so no single transaction corresponds to a single API call.
epochTotal += debited
Flush
The owner closes the epoch. One aggregate is released for public decryption and leaves the Safe as a single transfer covering every payment in the batch.
one number, N payments
Verify it yourself
GATEWAY=https://agentfabric-api.187.127.137.136.sslip.io
Every claim on this page is checkable from a terminal right now. Nothing here is a mock.
The gateway is on the real chain
curl -s $GATEWAY/chain/status
{ "configured": true,
"demoMode": false,
"network": "testnet",
"chainId": 11155111 }The vault is live, with its relayer and epoch
curl -s $GATEWAY/nox/status
{ "configured": true,
"vaultAddress": "0xe417e9e3…5123cc",
"relayer": "0xEEfbC8d6…Ba4eBa",
"network": 11155111,
"epoch": 1 }A closed epoch reveals one aggregate, never a payment
curl -s $GATEWAY/nox/epoch/0
{ "epoch": 0,
"closed": true,
"totalWei": "38500",
"count": 7 }count is how many settlements the batch absorbed. totalWei covers all of them, and cannot be decomposed back into the payments that produced it.