Skip to content

Give your agents a wallet they can’t misuse

Set the limits once. Every transaction is checked against them before anything is signed.

Session KeysUniswap Agent

Uniswap Agent

Session key which has allowance to spend maximum of $100 USDC

Networks and lifetime

Networks
Ethereum
Expires at
27 Sept 2026
Signatures
Messages and typed data allowed

Onchain permissions

Token spend limit

0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238

100 USDC per network

Wallets built for agents, not people

Every agent gets its own key with a spend cap, a network list and an end date. Nothing is signed without checking it.

FIG 0.1

Checked before signing

A request that breaks a rule returns an error instead of a transaction. Nothing reaches the network and no gas is spent.

FIG 0.2

Scoped to one job

Each key carries a spend cap, the chains it may touch and a date it stops working. It cannot reach anything you did not name.

FIG 0.3

You hold the keys

Your account is owned by your passkey and session keys stay on the machine that uses them. Namera never holds signing material.

Try to spend past the limit

Change the amount or the network, then run it. The same swap passes on Base and is refused on Ethereum.

Uniswap Agent

ETH

$24

You receive

24

USDC

1 ETH = 2400 USDC · sample quote

What this key may do

Set when the key was issued. The agent cannot change it.

Token listETH, USDC
Per transaction on Ethereum0.02 ETH
Left this period on Ethereum38 of 100 USDC
Expires27 Sept 2026

Every key is issued with limits

You set the account, chains, expiry and cap when you create it. The agent gets the key, never the policy.

Scope

One account. Nothing else in the workspace is reachable.

Lifetime

Every key has an end date. Forgotten agents stop working on their own.

Uniswap Agent

Issued 10 Sept 2026

AccountTrading Account
Networks
Expires27 Sept 2026
SignaturesOff

100 USDC per network

0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238

Reach

Named chains only. A request anywhere else fails.

Grants

Each grant names one contract. Limits apply per network.

Four things the policy stops

Every request is checked against the key it came from, before anything is signed.

Transfer 5 USDCPayouts AgentSigned
Approve USDC spendUniswap AgentSigned
Swap 120 USDC for ETHover the 100 USDC capRefused
Swap 40 USDC for ETHUniswap AgentSigned
Gas top-upUniswap AgentSigned

An agent spends past its cap

The transaction is refused before it is signed. Nothing reaches the network and no gas is spent.

$ namera login
waiting for approval…

Namera CLI is requesting access

Verification codeR77H-3L96
RejectApprove

A new device asks for access

Nothing runs until you approve the device, against a code shown in both places.

Research Agent

Payouts Agent

Uniswap Agent

Expires 27 Sept 2026

12d

A key reaches its expiry

The key stops signing on its end date. Renew it, or let it lapse and the agent simply stops.

Uniswap AgentTrading AccountActive
Payouts AgentTreasuryRevoked
Research AgentTrading AccountActive

You revoke a single agent

Revoke one key and the rest keep running, including the work already in flight.

Every client gets its own grant

Register Namera once in the client you already use. Each one authorizes separately, keeps its credentials in your OS keyring, and can be cut off on its own.

Claude Code claude mcp add --transport stdio --scope usernamera -- namera mcp serve --profile claude

Claude Code

Register once. The client starts Namera when it needs it, and every tool call runs inside the session key's limits.

Codex codex mcp add namera --namera mcp serve --profile codex

Codex

The same server under its own profile. Signing in to one client does not authorize another.

Any MCP client {
"command": "namera",
"args": ["mcp", "serve", "--profile", "agent"]
}

Any MCP client

Point any client at the namera binary. No hosted server, no port to open, and no secret to paste.

Each profile keeps its own grant in the OS keyring. namera mcp logout --profile codex revokes that one on the server and leaves your other profiles, and your signing keys, exactly as they were.

The life of one transaction

A swap on Uniswap, from the agent that asks to the block that confirms. Change what the agent wants and run it again. This is a walkthrough, not live data.

Intentwhat the agent wants
From
Swap
Amount
Chain
Swapon Uniswap
Sell100 USDC
BuyETH
ChainEthereum
Preparegetting the swap readysponsored
Gaswhat the swap costs to run
SponsorNamera covers that gas
Dry runthe swap is tried first
Policyyour rules, checked in ordersession key
Spend cap100 of 100 USDC
NetworksEthereum, Base
Expires27 Sept 2026
ContractsUniswap only
Signingmessages and typed data
Signon your own machine

the key never leaves it

Sendhanded to the network

gas already covered

Confirmedthe swap is on the chain
NetworkEthereum
Gas paidnot reached
Set what the agent wants, then run it. Cards can be dragged.

Questions worth asking first

  • No. A key is fixed once it is issued. Its end date, its networks, and every limit on it are locked in at that moment and cannot be edited by anything holding the key. Changing any of them means revoking it and issuing a new one, which takes a person with permission and an approval from their passkey.

Built for agents. Opening soon.

Set the limits once. They hold on every chain and in every client. Join the waitlist and we will write to you the day Namera opens.