What is PolicyVault?

A non-custodial policy and covenant-enforcement layer for delegated Kaspa spending — for people and AI agents.

PolicyVault is a non-custodial delegated-spending layer for Kaspa L1. A vault owner defines a spending policy — who may spend, how much, how often, and to whom — and that policy is enforced by Kaspa consensus itself, through a covenant (a constrained smart-contract-like spending condition compiled in SilverScript), not by PolicyVault's servers.

The core idea: an owner can hand a spending key to an agent — a person, an automated service, or an AI agent — without handing over control of the funds. Even if that agent bypasses the PolicyVault application entirely and hand-builds a transaction straight against a Kaspa node, the covenant still enforces the owner's limits. This is what "covenant-enforced" means throughout this documentation: the rule holds against a malicious or careless actor who legitimately holds the delegate's private key.

#The authority model

AI MAY REQUEST. POLICYVAULT DETERMINISTICALLY DECIDES. THE COVENANT ENFORCES. SIGNERS RETAIN CUSTODY.

Read literally:

• An AI agent (or any automated caller) can ask PolicyVault to build a transaction.
• PolicyVault's deterministic core decides whether that request is even well-formed and within the vault's declared policy — no LLM output is ever trusted as a decision.
• The covenant — Kaspa L1 consensus — is the actual enforcement mechanism. It rejects any transaction that violates the vault's policy, regardless of who signed it or what any server said.
• Signers (the owner's or agent's wallet — KasWare today) retain sole custody. PolicyVault never holds, requests, or has access to a private key or seed phrase.

#What PolicyVault enforces on-chain (via the covenant)

• Owner-controlled vaults: create, manage, pause, recover, close.
• Delegated spending for up to 10 independent agents per vault, each with its own policy.
• Per-transaction spending caps and cumulative periodic budgets.
• Recipient allowlists (Merkle-committed): an agent can pay only owner-approved destinations.
• M-of-N approvals above an owner-set threshold.
• A covenant-controlled fee reserve, so agents can spend without needing a separate "gas wallet."
• A break-glass owner pause and terminal recovery path that is never gated by any hosted workflow.

#What the hosted platform adds (coordination, not authority)

Above the covenant, the PolicyVault platform adds convenience and safety tooling that never gains independent financial authority: intent manifests with independent browser verification before every signature, an optional governance ceremony for policy changes, a pluggable restrictive-only risk pipeline, audit trails, webhooks, and agent-facing surfaces (REST API, MCP server, Python/JavaScript SDKs, x402/AP2 adapters). None of this machinery can move funds on its own — see What the hosted server can and cannot do.

Next: What PolicyVault is NOT.