Sisih
Sui Mainnet proof verified

Spending controls for an AI agent that pays for services

Your money has a purpose.
Your agent has a limit.

You let an agent buy data and APIs from the same wallet that pays your bills and savings. A balance or a daily cap does not know which money is already promised. Sisih does: it reserves your commitments first, lets the agent spend only what is left, and remembers your decisions for the next session.

See the Mainnet proof Connect your agent

Completed proof on Sui Mainnet · Walrus Memory Mainnet. Two x402 purchases, one recalled approval, reserves protected. Public endpoint is read-only; agent permission revoked.

CAPABILITIES

What Sisih can do

Concrete guardrails combining Sui Move smart contracts with Walrus Memory so your AI agent pays for what it needs without risking your reserved funds.

Onchain Commitment Reserves

Ring-fences funds for hosting, inference bills, and savings directly in a Move contract on Sui. Hard contract invariants prevent any agent or prompt from touching committed funds.

Sui Move Contract

Autonomous x402 Micropayments

Allows your AI agent to pay for on-demand data feeds and API services via x402 invoices in real time, settled onchain on Sui and verified through Tatum.

x402 Protocol

Cross-Session Memory

Stores owner approvals and merchant preferences in Walrus Memory. In the verified run, one recalled preference allowed the next purchase without another review.

Walrus Mainnet

Hard Spending Caps

Enforces strict per-request limits, 24-hour daily caps, and permission expiration. Even with a remembered preference, hard limits cannot be bypassed.

Policy Engine

Separate Agent and Owner Roles

Connect an external MCP client with a role-scoped bearer credential. The model receives no wallet keys or signing authority. In the completed Mainnet proof, Codex performed the task and permission was subsequently revoked.

Model Context Protocol

Terminal & Assistant Control

Review purchases and control permission through the companion CLI or owner MCP. Mainnet owner actions require a local signature. The recorded proof ends with permission revoked.

Owner Companion

The failure Sisih prevents

Illustrative example

A spending cap alone

You start with 20.00 USDC. 16.50 is due this week for inference, hosting and savings. Your agent has a 5.00 daily cap, has already spent 1.70, and asks for a 3.00 report.

The cap allows it. Your bills are now 1.20 short.

With Sisih

The 16.50 is reserved in the vault before the agent can spend. Only 1.80 is free, so the 3.00 report would cut into a reserve.

Refused by the contract. No preference or approval can unlock reserved money.

This example is illustrative. Proof records real Mainnet purchases and a labeled reserve-refusal simulation.

How it works

  1. Your agent asks

    Over one MCP endpoint, the spending agent checks its budget, picks a service and requests one purchase for its task.

  2. Hard rules decide first

    The Move vault on Sui holds your reserves, per-request and daily caps, expiry, pause and revoke. The agent is paid only from free funds.

  3. You decide the new cases

    Unfamiliar purchases wait for you. You answer from your own owner session or your terminal; the agent can never approve itself.

  4. Your decision carries forward

    Approve and remember: the preference is stored in Walrus Memory and recalled next session. It only chooses among payments the vault already allows.

Why not a separate agent wallet?

A separately funded wallet with a static budget is the strongest simple alternative, and it works if you keep refilling it by hand. Sisih's claim is narrower: the agent spends from the money you already hold, and the amount it can reach changes with your actual commitments. A remembered preference can remove a repeated review when the purchase still fits every hard limit. The recorded run shows one such decision.