Say Ur Intent

JUST SAY "CONNECT WALLET."

Say Ur Intent is a local-first Sui review and evidence layer for AI clients.

It turns a supported Sui action into an internal Review card where you inspect verified transaction facts and a PTB graph, then request approval in your own wallet. The backend builds or verifies the material, binds the reviewed account and digest, and uses WalletConnect for a sign-only request. It verifies the wallet's returned bytes and signature before one submission to Sui mainnet.

The AI and card never receive executable transaction bytes or signatures. Neither a review nor a wallet connection is standing transaction permission. Only an explicit user action and that transaction's wallet approval authorize the request. Lost replies are resolved by reading the known digest; they do not cause another signing or submission request. Request failures and unknown outcomes are separate from independently observed chain success/failure.

Account, Receipt and Chart cards provide read-only evidence independently of signing. Connect and Review also run inside the MCP host. Settings currently uses a local token page. Human-readable review is not a guarantee of safety or of complete interpretation of every transaction detail; the raw PTB structure and addresses remain inspectable.

Users can ask ordinary questions:

• "Can I cover a 1000 dollar payment with my assets?"
• "How much are my USD-denominated assets together?"
• "What is the shortfall?"

The broader product direction does not stop at pre-execution review. From verified evidence, Say Ur Intent aims to carry an AI client's or MCP server's Sui payment or action request through a human-readable local review and on to user-controlled wallet signing and execution receipt evidence — only after Say Ur Intent independently builds or verifies the transaction material. The three layers below state what is implemented today, what is deliberately sequenced next, and what stays permanently out of scope. For any such request, Say Ur Intent explains what current verified evidence supports, what choices remain with the user, and what claims are unsupported.

Product Scope in Two Layers

Say Ur Intent is one product, but it must be read at two distinct layers. Do not collapse them:

• Implemented: Sui mainnet read evidence, non-signable external proposal review, and account-bound DeepBook swap review using protocol-agnostic adapters. Five internal cards use the same SQLite state and permission model. The backend verifies stored material, ownership, quote/policy provenance, human-readable facts, simulation and PTB evidence before an explicit user request. WalletConnect carries bytes only between the backend and wallet; ordinary MCP responses expose facts, request status and observed execution results. Settings remains a local token page; its card and the next package release are sequenced separately.
• Never (permanently unsupported at every layer): no private-key custody, no MCP or AI autonomous execution, no forwarding of opaque external transaction bytes to a wallet, no silent settlement-token or route choice, no fiat cash-out, no P&L, no peg guarantee.

In one sentence: Say Ur Intent is a local-first Sui intent evidence and review layer that progresses from verified evidence to user-controlled wallet signing only after Say Ur Intent independently builds or verifies the transaction material and shows a human-readable local review.

DeepBook provides the current scoped Sui conversion, price, and orderbook evidence through the shared protocol adapter contracts. Wallet and Sui balance reads describe held assets. They do not define the whole product.

Say Ur Intent does not custody funds, hold private keys, or autonomously trade on behalf of users. By current design, it does not rank venues, choose routes, make best-price recommendations, or silently choose settlement tokens for users.

Account-bound transaction building, signing requests and chain observation stay in the local backend. The Review card displays evidence and current permitted actions. Public review JSON, card metadata and backups never contain transaction bytes, signatures, SDK keys or signing permission. Reopening a card reads its stored state and never replays a financial request.

The current release flow is:

The user states an intent in natural language.
Say Ur Intent resolves the supported Sui mainnet evidence surface.
The AI answers only from returned evidence and boundaries.
Supported swap transaction material build is an account-bound review step, not
part of the natural-language intent evidence answer.

The current release implements intent evidence for supported Sui mainnet reads. It can also create a read-only, non-signable local review session from a structured external payment or Sui action proposal. External proposal ingestion does not trust external transaction material or send anything for wallet signing.

For setup, see docs/MCP_SETUP.md. For the MCP API reference, see docs/MCP_TOOLS.md. For the AI-client answer playbook, see docs/AGENT_BEHAVIOR.md. For manual maintainer and developer utilities, see docs/UTILITY_INDEX.md.

User-question flows for USD-denominated coverage, balance totals, and shortfall answers live in docs/AGENT_BEHAVIOR.md. The response fields for those answers live in docs/MCP_TOOLS.md.

What Works Today

The current release can run as a local stdio MCP server and expose mainnet Sui DeFi evidence:

• wallet balances with verified display units;
• coin-balance classification;
• USD-denominated settlement asset groups derived from pinned DeepBook SDK registry metadata;
• intent evidence with response summaries for natural-language USD-denominated payment coverage, balance-total, and shortfall questions;
• DeepBook pools, tokens, mid price, orderbook context, raw quotes, display-amount quotes, and account inventory;
• user-requested bounded Sui transaction digest lookup, account activity scans, sent-function activity scans with known-wallet-only persistence, and stored normalized activity summaries;
• read-only external proposal review sessions that display proposed action, asset flow, recipient or target, freshness, missing evidence, user choices, unsupported claims, and non-signable reason;
• local Say Ur Intent review evidence and review-session status reads;
• account-bound DeepBook review with verified material, digest, ownership, policy, human-readable facts, simulation and PTB visualization, followed by explicit card selection and wallet approval through the backend;
• separately recorded request state and chain success/failure, shown in the Review card and available through ordinary reads;
• a Receipt card for server-read facts about any transaction digest, independent of signing.

It also includes:

• a local review server bound to 127.0.0.1;
• a local SQLite store for active account read context and review evidence;
• MCP output checks that reject forbidden executable, signing, token, seed, and key-material field names from responses.

Screens

Review and result. The internal Review card shows verified facts before wallet approval and independently read chain facts afterward. A PTB graph shows transaction structure alongside readable amounts and raw addresses. Missing receipt or display details are explicitly marked unavailable.

DeepBook USDC chart. ui.open_chart opens an internal MCP Apps card with official DeepBookV3 Indexer candles and volume for one selected USDC pool. The saved result shows the selected pair, interval, UTC period and source time. Limited and empty results are identified.

Current Limits

Not Implemented

External proposal execution is not implemented. Further local analysis views beyond the current inline review receipt and internal Receipt card are not implemented. Transaction material review, backend WalletConnect requests under user control, signature verification, single submission and independent receipt observation are implemented for the account-bound DeepBook swap review through a plan-factory registry.

External proposal ingestion is implemented only for read-only local review sessions. It accepts structured proposal facts, rejects forbidden executable or signing fields, recognized Sui private-key strings, valid English BIP39 mnemonic phrases, obvious sensitive markers, and suspicious raw secret-like payloads before storage, and records why the review is non-signable.

A blocked review lacks required evidence for that session. Only a complete TransactionReviewData binds human-readable facts and simulation to the exact reviewed digest. This is pre-signing evidence, not authority or guaranteed execution. The backend checks returned bytes and the selected account's signature before submitting. See the adapter contract.

Fiat cash-out, P&L, tax, and cost-basis support are not part of the current release.

Permanent Safety and Correctness Boundaries

These are product boundaries and must not be relaxed by ordinary feature work:

• Say Ur Intent does not custody funds, hold private keys, or autonomously trade.
• It does not treat USDC, USDT, or any USD-denominated settlement asset as fiat USD, a bank cash-out amount, or a USDC/USD peg guarantee.
• It does not turn quote-only conversion candidates into payment coverage, shortfall evidence, funding readiness, payment execution readiness, or signing readiness.

Out of Scope by Current Design

These product behaviors are out of scope in the current release by design: