For the companies that build agents

One call before your agent acts.


The Nuramem permission check. The person’s standing rules — said once, confirmed on their phone — answer allow, deny or ask in under a second, with a signed record of consent. Your agent inherits the rules of every household and every company it enters. You hold nothing.

What the check returns

Allow, deny or ask

Computed from the person’s rules by code, never by a model, in under a second. Inside the rules your agent just works, with a receipt.

The ask

Outside the rules, the person gets a push: yes · no · something else. “Fine, but $200 and only tonight” becomes a rule in the same gesture.

A signed record

Every ask and every answer, naming categories and amounts, never values. No card numbers, no addresses, nothing of the user’s to protect.

Nothing to hold

Nuramem never holds a card and never moves money. We hand the answer to any rail in its format, AP2 mandates included.

Household agents

Your agent inherits the rules of every household it enters.


“Leo can order DoorDash up to $30 an order.”

“No agent ever gets the kids’ data.”

“Peter can approve for me while I’m away.”

Work agents

Your agent inherits the customer’s rules.


“No agent spends over $500 without Peter’s approval.”

Asks go to the admins or a named approver; one signed record for the company, across every agent it runs.

The integration

Confirmed only on the person’s phone — never by email or inside a chat, because agents read both now.

One tool over MCP for agents that are MCP clients; one HTTP call for everything else.

The API reference →

Already asking today

Design partners