Meow Gateway
Delegated-authority control plane for agentic money movement. Signed spend capsules, drift checks, decision receipts, HITL approvals, in front of Meow's write-MCP.
The Meow Gateway sits between an AI agent and Meow's write MCP. Every payment goes through a signed Spend Capsule that binds the agent's intent to an exact beneficiary, amount, rail, and policy. At consume time the gateway drift-checks the capsule against the request, forwards to Meow on allow, and writes a Decision Receipt to a per-entity hash chain. Auditors verify the chain locally, no Veto-hosted service required.
Prototype status: this MEOW material documents a demo surface, not the primary financial-agent trust-kernel path. Receipt terminology here follows the current platform veto.receipt/1 docs; older spend-capsule receipt helpers and anchoring claims are intentionally not presented as product guarantees.
For agents: one prompt, one URL
Tell your AI agent this and it's done:
I want to get started with Meow for my AI agent with safety.
Read the docs at https://veto.so/meow-skills.md and then set it up.veto.so/meow-skills.md is an openclaw-compatible skill file that drops in where meow.com/skills.md used to sit. Same tool surface, same CLI ergonomics, plus policy-as-code, real HITL (not a "please confirm" string), and a hash-chained audit trail. The agent gets through setup with a free Veto API key.
Why not build this myself?
An honest answer: you'd need to maintain Ed25519 + JCS + JWKS rotation, a YAML policy compiler, a HITL approval surface, a drift-check pipeline, a receipt chain, and the evidence trail that keeps it reviewable.
The gateway is Apache-2.0. Fork it, run it offline, never talk to us if you don't want to. The offline demo works without a Meow sandbox token AND without a veto.so account.
30-second demo
npx @veto/meow-gateway demoMints an Ed25519-signed capsule, consumes it through a mock Meow upstream, and records a decision receipt. Exits 0. No network calls, no accounts.
What's in the box
Self-host first
Single Docker image or npx binary. Stores to SQLite + NDJSON on local disk. Connects to veto.so only if you opt in.
Spend Capsule protocol
Ed25519 + JCS canonical JSON. Every capsule is single-use, TTL-bounded, and binds to an exact beneficiary hash.
Decision Receipt chain
Prototype receipt flow aligned to the platform veto.receipt/1 model.
Policy packs
Three bundled packs, ap_strict_v1, crypto_fund_v1, fund_admin_v1. Fork or override via YAML.
What lives where
@veto/meow-gateway, the self-host binary + Docker image@veto/spend-capsule-protocol, Apache-2.0 prototype package for capsule signing and verification@veto/meow, typed TypeScript MCP clientveto-platform/apps/meow-gateway, the source (in this monorepo)
Where to go next
- Quickstart, 3 minutes from
brew installto a signed capsule - Self-host runbook, signing keys, storage backup, key rotation
- Protocol reference, canonical JSON, schemas, golden vectors
- API reference, every REST endpoint + error code