Policies
Policy primitives that scope what a Namera session key can do.
For the complete documentation index, see llms.txt.
Policies define the boundaries for delegated wallet access. A session key can only execute actions that satisfy every policy attached to it, so each key can be scoped to a specific chain, contract, function, gas budget, time window, or rate limit.
Use policies when an app, automation, or agent needs limited authority instead of full account control. The account owner approves the policy set once, then the session key can operate within those constraints until it expires or is revoked.
Common policy types
- Call policy: allow specific target contracts and function selectors.
- Gas policy: cap transaction gas usage.
- Rate limit policy: limit how often a key can act.
- Timestamp policy: set valid start and expiry times.
- Signature caller policy: require calls from an expected signer.
- Sudo policy: grant broad authority when a session key intentionally needs it.
For a complete setup flow, start with Create Session Key or Create Passkey Session Key.