You have an intent.
We do the rest.
Mint a link that carries an ask — “Buy $10 of AAPL”, “Stake ETH with Lido”, “DCA $25 weekly”. Whoever opens it connects their own wallet and Pantessa scans, funds across chains, builds, and guard-checks the whole path. They sign. Done. The transaction onboarding flow, nailed — for your dapp, or for the audience you teach.
🔗 /i/buy-aapl opened · funded cross-chain · signed · receipted
Watch a sentence become multiple transactions.
Almost nothing worth asking for is one transaction. Pick an ask and the same stages your users walk run right here — the wallet scan, the funding plan, the pinned builder, the guardrails that fail closed, the signatures that are only ever theirs. Four asks, four different endings. That difference is the whole product.
Buy $10 of AAPL
An empty wallet on the wrong chain. The ask still lands.
The sentence becomes a spec — no model writes calldata here.
> action buy
> spend $10.00 (dollar-denominated)
> asset AAPL → tokenized equity, Robinhood Chain (4663)
> settle USDG · 6 decimals
A link that moves money.
Mint a short link that carries an ask. Whoever opens it connects their own wallet and the path builds itself — guarded, signed only by them, receipted — then they’re handed back to wherever the link lives. Creators earn half of Pantessa’s 0.20% fee on the conversions their links produce.
The money moved. Nobody was at the keyboard.
Recurring buys, stop-loss protections and multi-step jobs keep working between your turns. Pantessa is the non-custodial back office for autonomous money: it builds, guard-checks and receipts every move — and holds nothing.
- Say it once “Every week,” “if it drops 8%,” “once the bridge settles.” The sentence becomes standing intent — not a reminder to come back and type it again.
- Guard-checked at fire time Nothing runs on stale math. Every step is rebuilt and re-checked the moment it’s due, so dead calldata never reaches a wallet.
- Your keys, your receipts You sign, or a scoped key you can revoke does. Either way the tx hash lands in your ledger before you wake up.
- 22:15DCA Autopilot pulled $25 and bought ETHone-shot Spend Permission · nothing else it can touch
- 00:38JOB 3/3 Bridge settled → bought $25 of NVDAeach step rebuilt and guard-checked at its own turn
- 02:47GUARDIAN ETH stop fired at $3,208 · position closeddelegated key · revocable · never custody
- 05:30SPOT GUARD 312th sweep · mark above the floor · no actionchecking is the job — most minutes it does nothing, loudly
The best screenshot is the one where nobody was at the keyboard.
DCA in one sentence
A sentence makes the schedule. Each buy compiles fresh on its day — no bot to host, no hot key to leak.
“Buy $10 of AAPL every week” →GUARDIANStop-losses that don’t sleep
Autonomous protection via a delegated agent key. It watches every minute and closes the position for you. Revoke any time.
“Set a stop-loss on my ETH position at −8%” →JOBSFund → wait → act
Multi-step work compiles as one job: bridge, wait for settlement, then swap, stake, send, or buy. Guard-checked step by step.
“Swap 1 USDC from Base to Arbitrum, then send it to nate.eth” →NFTSSell it in a sentence
Guarded Seaport listings: ownership verified on-chain, fees pulled from the collection’s live schedule, re-checked before submit.
“Sell my NFT #4172 for 0.8 ETH” →Why hosts embed it. Why users sign.
Two different people, two different worries. A host is deciding whether to put this on their page; a visitor is deciding whether to sign something a machine built. Both answers are the same architecture, read from opposite ends.
An agent that moves money for your users, without you ever touching a key.
- Five lines, and it signs with your page’s walletNo key custody to negotiate, no checkout to build. wallet: ‘auto’ uses the wallet your visitor already connected.
- You see the asks you couldn’t answerEvery turn on your site lands in your dashboard — funnels, dead ends, money moved, and which tool would have closed each gap.
- Kill switch and org capsPause an agent or freeze an account server-side, instantly and reversibly. Orgs get a daily cap above per-key budgets.
- Built on routes that earned itMCPs score on reliability, liveness, speed and settled history — so the set behind your chat isn’t a guess.
A machine that has to prove every step to you before you approve it.
- Nothing moves without your signaturePantessa holds no keys and never has. The wallet that pops is yours, and the transaction it shows is the one that gets sent.
- Guardrails, re-fired per stepRecipient, amount, selector, price and caps re-checked before every step, on fresh state, at your turn. Over-cap gets dropped, not built.
- Receipts, in the openEvery settled move carries a tx hash and lands in a public activity feed. There’s no dashboard you have to take our word for.
- Standing work stays revocableA schedule, a Spend Permission, a Guardian key — each scoped to one job, each cancellable from the chat or the dashboard.
Non-custodial by construction · your wallet signs · every move receipted
Stay up to date.
The agent can sign things this month it couldn’t sign last month. That’s the only thing this list is for.
- NEW DAPPS
- when a protocol becomes one sentence away
- STANDING WORK
- schedules, guards and jobs that run between turns
- NEW SIGNATURES
- what the agent can build and sign that it couldn’t last month
Double opt-in · no spam · unsubscribe from any email