# Give AI agents permissions, not your private key > Source: > Published: 2026-10-07 16:38:43+00:00 # Wallets for AI agents with permissions built in Give agents the power to transact. You set what they can spend and do. ## Wallets built for agents. Give each agent its own key with scoped permissions. You decide what it can spend, where it can transact, and for how long. ### Checked before signing Every action is checked against your rules first. If it’s outside the agent’s permissions, it doesn’t execute. ### Scoped to one job Give each agent only the access it needs - spending limits, allowed contracts and networks, and an expiration date. ### 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 for the default amount but fails when increased. Uniswap Agent $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. ## Every agent operates within 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. Expiry Set an expiration date. Access automatically ends when time runs out. Uniswap Agent Issued 10 Sept 2026 100 USDC per network 0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238 Networks Choose which networks the agent can use. Everything else is blocked. Spending Set spending limits for each token, contract, or network. ## The life of a transaction A swap on Uniswap, from agent intent to onchain execution. See how Namera prepares, checks, signs, and submits every transaction. the key never leaves it gas already covered ## Every agent gets its own permissions Connect Namera to Claude, Codex, or any MCP client. Each gets its own credentials and permissions, and can be revoked independently. `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. ## Every agent, its own fence A trading desk, a checkout bot, a steward inside a game. The wallet never changes - the budget, the networks and the expiry do. [Try one against its limit](#playground) Industries - Trading desks - AI agent platforms - Agentic commerce - Wallets & fintech - Onchain games ## Questions, answered. - 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. ## Launching soon! Smart accounts, session keys, and onchain policies - all in one place, ready for agents.