Mandate
The boundary within which an agent may spend — typically a per-payment cap, a daily cumulative cap, a payee allowlist and a stated purpose. It has to be enforced by a system outside the agent: a limit written into a prompt is not a mandate, because an agent's reasoning can be poisoned. Our gateway checks each of these before settlement and compares the intent of the payment against the original mandate.
In plainer words
A mandate is the boundary within which an agent may spend. It usually has four parts: the most it can spend in one payment, the most per day, which addresses it may pay (an allowlist), and what purpose is allowed. Think of it as an allowance's rules — but for an agent. The key: these rules must be enforced by a system outside the agent. A limit written only into the agent's prompt isn't a real mandate, because an agent's "mind" can be poisoned by text and talked into going around it (see "prompt injection"). Letting an agent enforce its own limit is letting a possibly-hijacked guard watch itself. Before every settlement, OceanAlt's gateway checks the mandate line by line: over the cap? Blocked. Paying an off-allowlist address? Blocked. Purpose doesn't match? Blocked. It also compares this payment's intent against the original mandate — even if the agent insists "this is fine," a mismatch doesn't pass. In one line: a mandate turns "how much, to whom" from a sentence in a prompt into a hard constraint the money can't get past.
RELATED TERMS
- KYA (Know Your Agent)Attributing identity to an AI agent that initiates payments:…
- Prompt injectionHiding malicious instructions inside content an agent will r…

