Smart Budget

Monad agent payment control

Automated execution, human takeover available

Agent-native payment system on Monad Testnet

SmartBudget

Smart Budget gives AI agents controlled payment capability. Funds remain in the user's vault, agents pay through scoped session keys, and every execution stays bounded by policy rules and human pause controls.

Open Console Explore The System

Control model

Human takeover ready

Payment path

Vault -> session key -> x402 request

Deployment network

Monad Testnet / 10143

Operator brief

Control

Even during agent execution, the owner can pause the vault and stop subsequent payments at any time.

Operator brief

Scope

Session keys define expiry, per-tx caps, daily budgets, and access boundaries together.

Operator brief

Settlement

x402 requests settle through a clear and traceable machine-payment path.

System status

Vault state

Funds stay centralized while execution rights are granted as needed.

System status

Policy rules

Limits, categories, and recipient constraints stay active inside the system.

System status

Recovery

Pause, revoke, and rotate paths remain clear and always available.

Runtime status

Authorized execution, end-to-end control

Active

Control status

Enabled

Vault available / human takeover active

Vault

Agent

Policy

x402

Authority

Owner -> session key

Scoped signing path

Spend scope

Per-tx cap + daily budget

Constrained by policy rules

Recovery

Pause / revoke / rotate

Human takeover always available

Owner

Approval window

Policy

Validation rules

Agent

Payment request

Primary route

Vault -> session key -> x402 request

Vault

0xcE19...C059

Network

Monad 10143

Control mode

Delegated spend

Emergency pause

Manual pause

Event lane

00.02Vault funded

00.07Session key created

00.13x402 request settled

FundDelegateObserveThrottleRevokeRecoverx402Monad

Capabilities

A controlled, auditable execution environment for agent payments

Smart Budget is an agent-native payment system built for Monad. Users retain control of the vault, agents execute payments through scoped session keys, and every action stays inside limits, timing rules, and policy boundaries.

Control overview

Control rights, authorization scope, and takeover paths stay visible

Asset control

Funds remain inside the user's deployed vault contract, and agents never receive unrestricted primary control.

Session keys

Each agent permission includes expiry, per-tx caps, daily budgets, and whitelist constraints.

Audit and recovery

Payment history, policy hits, and manual intervention paths remain traceable, with pause, revoke, and rotate always available.

Product structure

The page is organized around four core objects: the vault, session keys, policy validation, and human takeover, helping users understand how agent payments are safely authorized and executed.

Scoped authority

Session keys define payment duration, spending ceilings, and accessible scope.

Machine payment rail

Supports x402 and agent-to-service automated settlement flows.

Continuous visibility

Vault state, authorization state, and payment results stay readable in one place.

The lower section connects funding, policy checks, session authorization, and payment execution into one readable flow so operators can quickly judge whether the system is safe, executable, and recoverable.

Vault funds

Funds stay concentrated in the user's controlled vault address

Policy checks

Limits, categories, and recipient rules are validated before execution

Session authority

Expiry and spend boundaries remain active for every agent permission

Machine settlement

x402 payment requests can be executed directly by scoped agents

Per-tx limit

Limit active

Daily budget

Budget active

Emergency pause

Manual control available

Runtime overview

Key events and execution state stay up to date

The page uses event feeds and state modules to show vault funding, session key issuance, x402 settlement, and human takeover status so operators can quickly confirm the current runtime condition.

Event log

Monitoring

00.02

Vault funded

Working capital has been deposited into the user-controlled vault address

00.07

Session key issued

Agent execution authority is now active with explicit spending constraints

00.13

x402 request settled

The machine-payment request has been executed on Monad Testnet

00.19

Human takeover available

Pause and recovery paths remain available throughout execution

Product entry

The home page explains the system. `/vault` runs the operations.

The home page focuses on product capabilities, control model, and payment flow, while the console handles deposits, session key management, policy configuration, and payment review.

Open Console View Capabilities

Home page

Route `/` explains system capabilities, control boundaries, and machine-payment scenarios.

Console operations

`/vault` handles deposits, session key management, policy review, and payment approval flows.

Human override

Pause and recovery paths stay explicit instead of requiring extra navigation to find.

Page /

Product entry page

Explains the control model, machine-settlement capabilities, and recovery mechanisms so users can quickly understand how Smart Budget works.

Page /vault

Operator console

Concentrates deposits, session keys, pause controls, and payment review into one surface built for execution.

Human takeover active

Human takeover paths remain explicit

The system consistently reinforces that automation is delegated and bounded, never unchecked, and that pause and recovery remain visible throughout.

SmartBudget

Automation always runs inside explicit boundaries

Authorized execution, end-to-end control

A controlled, auditable execution environment for agent payments

Control rights, authorization scope, and takeover paths stay visible

Funds, policy, and settlement states move together in real time

Key events and execution state stay up to date

The home page explains the system. `/vault` runs the operations.

Product entry page

Operator console

Human takeover paths remain explicit