Uniagent

On-chain spending limits for AI agents. Enforced by Uniswap v4 hooks - overspend, get refunded. Ethereum-native.

[Uniagent @useuniagent]

Two agents. Same wallet. One difference.

Without limits: swaps until it's gone. With Uniagent: every transaction checked by a Uniswap v4 hook, hard stop at the budget, automatic payout if anything breaks.

Your agent doesn't need to be smarter. It needs a policy.

[Uniagent @useuniagent]

On-chain AI is not a narrative anymore.

It's volume. It's wallets. It's real capital moving through Uniswap v4 every day. Uniagent is the protection layer underneath all of it.

[Uniagent @useuniagent]

This is what protected agents look like in production.

Every swap fired a Uniswap v4 hook. Every hook checked the policy. Nothing broke.

[Uniagent @useuniagent]

@ajidatlolebar @tryuniagent @bankrbot They have just stolen our X.

[Uniagent @useuniagent]

Uniswap v4 hook ecosystem is growing.

Uniagent grows with it. Every new pool is another enforcement surface. Every new agent is another potential policy.

[Uniagent @useuniagent]

This is why hook-level enforcement is different.

Every swap goes through beforeSwap() first. That's where Uniagent lives. Budget exceeded - the hook reverts the transaction before it executes. Not a warning. Not a notification. The swap never happens.

App-level guardrails run after the money moves. Hooks run before.

[Uniagent @useuniagent]

Your trading bot just tried to move $12,847 in a single swap.

You set a $500 daily limit. The Uniswap v4 hook read the transaction at the pool level, checked the policy, and stopped it before it executed. Not a middleware warning. A hard block, on-chain, in real time.

The agent didn't overspend because it couldn't. That's the difference between app-level guardrails and hook-level enforcement.

[Uniagent @useuniagent]

$7,550 spent across a fleet of AI agents in 14 days. 74 transactions. 0 alerts.

Zero alerts means every swap, every program call, every stake stayed inside the budget. Enforced by Uniswap v4 hooks in real time, no manual review, no incidents.

This is what a protected fleet looks like.

[Uniagent @useuniagent]

@UniswapBuilders @okx execution without limits is half the stack. the other half is knowing when to stop.

[Uniagent @useuniagent]

@UniswapBuilders spending enforcement for AI agents via v4 hooks. if your agent swaps on uniswap it needs a budget. we're building that layer.

[Uniagent @useuniagent]

@VitalikButerin the runtime side of this is equally interesting. correct code can still be misused. on-chain enforcement at execution time feels like the missing piece

[Uniagent @useuniagent]

@Uniswap and AI agents are going to move a lot of it autonomously. nobody's really thought through what happens when they go over budget

[Uniagent @useuniagent]

Overspend protection for AI agents shouldn't require a custom contract. Uniagent turns every Uniswap v4 pool into an enforcement layer: any agent, any wallet, fully on-chain.

Powered by @Uniswap v4 hooks. Set a daily budget, define a whitelist, and get paid back automatically when any limit is breached.

[Uniagent @useuniagent]

@Uniswap @angstromxyz @KyberNetwork @dopplerprotocol @bankrbot @clanker_world wild how fast hook ecosystem went from "cool primitive" to products people use. v4 quietly became an app platform and nobody talking about it enough

[Uniagent @useuniagent]

AI agents have no spending limits. They swap until the wallet is empty.

Uniagent fixes this at the hook level. Every swap your agent executes fires a Uniswap v4 hook. Uniagent reads it instantly, checks the policy, freezes the wallet if the limit is crossed.