OWS Hackathon 2026Base Mainnet

Self-hosted, policy-gated
wallet layer for
AI agents

Lexon runs as a Telegram-based agent interface, uses OWS for delegated wallet access under user-defined rules, and executes actions on Base.

Explore Open Wallet
$ cat HOW_IT_WORKS.md
Natural input
Send a message via Telegram, voice, or call the Lexon API as an agent.
Intent to capability routing
Lexon interprets the request and routes it to an execution action or a capability endpoint.
OWS delegated access
OWS gives the agent delegated wallet access and evaluates policy-defined limits and constraints before signing.
Payment (x402)
Lexon can sell its own capabilities or pay remote agent endpoints over x402.
On-chain execution
If approved, the transaction is signed via OWS, broadcast to Base, and a receipt is returned.
Audit and transparency
Every action produces decision logs, denial reasons when relevant, and usage summaries.
$ lexon --list-features
Send USDC
> send
Send to an address or saved contact.
Swap
> swap
ETH ↔ USDC on Base.
Bridge
> bridge
Bridge from Base to 10+ chains.
Wallet Intelligence
> portfolio
Balances, wallet score, and recent patterns.
OWS Delegated Access
> policy
Delegated wallet access with policy-defined limits before signing.
Policy Trace
> audit
Visible decisions, denial reasons, and usage logs.
Voice Interface
> voice
Speak instead of typing.
Memory
> memory
Saved contacts and habits.
MoonPay
> on-ramp
Fund the wallet on Base.
x402 Capabilities
> catalog
Monetizable capabilities over x402.
Live x402 Capability
Lexon can expose paid capabilities for other agents and buy remote capabilities when it needs external intelligence.
seller · evaluate_bridge
endpoint
/api/x402/paid/evaluate-bridge
input
fromChain · toChain · fromToken · amount
output
allow/deny · matched rules · route · fee
payment
paid via x402 · 0.01
* more capabilities coming soon
buyer · paid market research
command
/research <query>
flow
call remote endpoint · pay via x402 · return normalized result
use case
paid deep market research from remote agent endpoints
extensible
different remote endpoint URLs can unlock different capabilities
$ cat package.json | jq .dependencies
stack — lexon v2.0
modulerolenotes
@open-wallet-standard/coreWallet · Agent Access · Policy · SigningLocal wallet management, scoped agent access, policy validation, and transaction signing
Li.Fi REST APIBridgeCross-chain routing from Base
Zerion REST APIPortfolioBalances, positions, and wallet overview
Allium Realtime APIWallet IntelligenceBase wallet activity, scoring, and behavior patterns
OpenRouter · Anthropic · OpenAIIntent ParsingNatural language to action
OpenAI WhisperVoice InputVoice note transcription
grammyTelegram BotWebhook + bot command handling
@x402/next · @x402/fetchx402 Commerce LayerMonetizable capabilities and agent payments
lexon@base:~$ ./launch --now

Run your own policy-gated wallet operator.

Type or speak via Telegram, or call it via API.
Lexon executes on Base — fully self-hosted, policy-controlled, and transparent.

github