For AI agents: read the documentation index. Documentation pages are available as Markdown by appending .md to their URL, or requesting Accept: text/markdown.

Namera Docs

Permissions and Policies

Understand the checks that determine what a session key can do.

Permissions define the authority you give a session key. API policies add restrictions to signature requests made through Namera. Transactions use onchain permissions.

What Allows an Operation

A client needs an active grant to an active session key. That key must have a confirmed installation on the requested network, and the operation must meet its permissions and every applicable API policy.

A valid login is not enough. Neither is a funded account or an active key on a different network.

Onchain Permissions

The account owner approves these permissions, and the smart account's contracts enforce them. Depending on the configuration, they govern:

  • Which recipients, contracts, and functions the key can use.
  • Which tokens it can transfer or approve and the available allowances.
  • How much native currency it can send and the gas budget it can use.
  • When execution authority starts and expires.
  • Whether it has signature authority.

These permissions belong to a specific network installation. Access on one network does not grant access on another. Choose the token or contract deployed on that network; the same name does not imply the same address.

For example, a key intended to send 0.001 ETH to one recipient needs both permission to call that recipient and a sufficient native-currency allowance. A gas budget is separate from the amount transferred.

Unrestricted account access is broad execution authority. It is not equivalent to a narrow transfer permission and does not implicitly enable signatures.

API Policies

API policies apply only to signing through Namera. They restrict signature types, typed-data domains, networks and time windows. Transaction limits live in the onchain installation, not a second API policy list.

All configured signing policies must pass. Adding a more permissive policy does not override another policy’s denial.

Different enforcement boundaries

API policies cannot expand onchain authority. They also do not restrict an operation submitted outside Namera. Use onchain permissions for restrictions that must be enforced by the account itself.

Amounts and Budgets

Native spending measures the currency sent with calls. Token allowances apply to the specified token, and gas budgets cover execution costs. These are not interchangeable limits.

Billing reserves execution and sponsorship allowance while an operation is pending. These usage holds are separate from onchain permission counters.

Signature Permissions

Signing requires explicit onchain signature authority and an API policy allowing the requested message or typed-data signature. Transaction access alone does not permit signing.

Typed-data policies can match a network, verifying contract, primary type, and domain. Matching those fields does not constrain amounts inside the message. A signature can authorize a later action even though signing it submits no transaction at that moment.

Signature authority has a separate lifetime

Onchain transaction spending limits and execution expiry do not constrain onchain signature authority. Remove the installed authority onchain to end it; revoking Namera access alone only blocks requests through Namera.

Simulation and Confirmation

Simulation previews the calls using the installed session without submitting the transaction. It is not a promise that execution will succeed: balances, budgets, and network state can change.

A successful submission is also not confirmation. Use the returned submission ID to follow its status rather than repeating the operation.