Advisory, not autonomous
Treat Monolythium agents as advisory. Through the local exact-three profile, they may read connection status, search illustrative Stele data, report the unavailable agent-wallet boundary, and explain options. The live hosted OAuth profile can search and exposes a nonbinding booking-approval draft tool, but production currently has 0 published services, so that tool cannot return a successful booking-approval draft. The hosted profile’s authenticated tools/list response is authoritative for its runtime inventory. Neither MCP surface can list, read, update, delete, or publish an existing web Studio provider-listing draft. Agents must not be described as safely holding wallets, enforcing spending policy, signing, submitting, booking, paying, opening escrow, contacting a provider, or resolving disputes through a supported Stele path today.
Wallet authentication is only an off-chain login proof. It never authorizes a later transaction. The hosted Stele MCP remains keyless, and Stele keeps economic writes and hosted signing disabled.
A future local execution path requires a dedicated agent wallet, protocol-enforced policy, exact state rereads and simulation, stable intent-to-signature binding, explicit approval appropriate to the action, and receipt reconciliation. None of those requirements may be replaced with a model-generated confirmation string or a client-side cap.
Never give an agent a person’s primary-wallet seed, private key, mnemonic, passphrase, or unrestricted signing credential.