Docs · Start here

How requests are understood

The kinds of requests Proxen understands, short follow-ups, and how missing details are handled.

2 min read

Each request becomes exactly one action: a swap, a site scan or a task. The interpretation is shown to you before anything runs.

Examples

RequestUnderstood asNext step
swap 2,000 USDG to ETHSwapCompares every open route
buy $750 of TSLA with USDGSwapWorks out the USDG amount, then compares routes
swap 0.8 ETH to USDG privatelySwap, privatePuts the private route first
is free-hood-drop.xyz safe?Site scanTests the site in a clean-room browser
swap 500 USDGSwapAsks which asset you want
stake my ETHLendingTells you it is coming next

Short follow-ups

Proxen keeps track of the link and the trade currently on screen, so a follow-up as short as check it or make it private is enough.

Missing details

If the amount or an asset is missing, Proxen asks for that detail only, with the most likely answers as buttons. It never picks an amount or an asset on your behalf.

Where your words go

Your request is read on Proxen’s server. Short, common requests are read by rules. When it is turned on, longer requests can be read by Claude, Anthropic’s model, on our servers. Your chat history stays in your own browser.

Try it

Tell Proxen what you want

Opens the app with your request typed in. Nothing moves until you sign.