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.

Schema Commands

Prints a JSON Schema document for a supported CLI command. This is the canonical way for agents to discover the --params shape.

Usage

namera schema <command>

Command paths

Supported command paths:

keystore.create
keystore.decrypt
keystore.info
keystore.list
keystore.import
keystore.remove
smart-account.create
smart-account.list
smart-account.info
smart-account.remove
smart-account.status
smart-account.import
session-key.create
session-key.list
session-key.info
session-key.status
session-key.remove
mcp.start

If a command is not listed, it does not currently expose a schema.

Output

The command prints a JSON Schema document to stdout.

Examples

Keystore create schema:

namera schema keystore.create

Smart account status schema:

namera schema smart-account.status

Session key create schema:

namera schema session-key.create

MCP start schema:

namera schema mcp.start

Schema Commands

Schema Commands

Usage

Command paths

Output

Examples

On this page