Namera is a programmable wallet infrastructure that lets agents execute onchain transactions within rules you define. Instead of giving full wallet access, you define permissions upfront and let agents operate within those boundaries.

How do agents access wallets?

Agents don't access your wallet directly. They use session keys — secondary keys with limited permissions — that you issue and control.

Are funds safe if agents can execute transactions?

Yes. Agents can only act within the limits you define — like which contracts they can call, how much they can spend, and how often. They never have unrestricted access to your funds.

What are onchain policies?

Policies are rules attached to a session key that define what an agent is allowed to do. They're enforced directly onchain, so they can't be bypassed or modified by the agent.

What happens if an agent is compromised?

Its access is already restricted by policies. You can revoke the session key instantly without affecting your main wallet or other agents.

Do I need to run infrastructure?

No. Namera is local-first and can run directly in your environment via CLI or MCP server. You don't need to manage backend infrastructure to get started.

How do I integrate Namera?

You can use the SDK for full integration, the CLI for local workflows, or connect directly to agents through the MCP server. It's designed to plug into existing developer tools and agent environments.

What is the MCP server?

The MCP server lets AI agents connect to Namera and execute actions safely. It acts as the bridge between your agent and the wallet, enforcing permissions during execution.

Can I use multiple agents with different permissions?

Yes. You can create multiple session keys, each with its own policies, and assign them to different agents or roles.

Which chains does Namera support?

Namera supports multi-chain execution through a unified interface, so you can operate across networks without managing separate wallets.

MCP Commands

The mcp command group controls the local MCP server used by agents. It wires a smart account and one or more session keys into an MCP-compatible interface.

Command group

Group: namera mcp

Subcommands:

start: Start the local MCP server

Interaction modes

Namera CLI is agent-first and supports two modes on every command:

Interactive (default). If required fields are missing, the CLI prompts you.
Params mode. Pass raw JSON using --params for agent-driven execution.

Get the JSON schema for any command:

namera schema mcp.<command>

Example:

namera schema mcp.start

Common output control

mcp start does not print output by default. Global output flags still apply but are typically unused.

--output, -o: pretty (default), json, or ndjson
--quiet, -q: suppress output entirely

MCP Commands

MCP Commands

Command group

Interaction modes

Common output control

On this page