Metadata-Version: 2.4
Name: veto-cli
Version: 0.1.1
Summary: Veto CLI — one-command MCP setup for AI agent payment authorization.
Home-page: https://veto-ai.com
Author: Veto
Author-email: Veto <tomer@veto-ai.com>
License: MIT License
        
        Copyright (c) 2026 Investech Global LLC (operating the Veto brand)
        
        Permission is hereby granted, free of charge, to any person obtaining a copy
        of this software and associated documentation files (the "Software"), to deal
        in the Software without restriction, including without limitation the rights
        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
        copies of the Software, and to permit persons to whom the Software is
        furnished to do so, subject to the following conditions:
        
        The above copyright notice and this permission notice shall be included in all
        copies or substantial portions of the Software.
        
        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
        SOFTWARE.
        
Project-URL: Homepage, https://veto-ai.com
Project-URL: Documentation, https://veto-ai.com/docs
Project-URL: Repository, https://github.com/veto-protocol/veto-cli
Project-URL: Issues, https://github.com/veto-protocol/veto-cli/issues
Keywords: ai-agents,mcp,model-context-protocol,x402,payments,authorization,agent-policy,claude,anthropic
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Topic :: System :: Systems Administration :: Authentication/Directory
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Dynamic: author
Dynamic: home-page
Dynamic: license-file
Dynamic: requires-python

# Veto CLI

> One-command setup for the Veto authorization layer — protect every payment your AI agent makes.

Veto is the policy and approval layer for AI agents that take real actions: x402 payments, Stripe Issuing transactions, on-chain transfers. The Veto CLI auto-configures Veto for any MCP-compatible client (Claude Desktop, Claude Code, Cursor, Zed, Continue) so your agent calls Veto before every transaction — and the transaction is allowed, denied, or escalated for human approval based on policies you define.

## Install

```bash
pip install veto-cli
```

Requires Python 3.9+. No third-party dependencies — stdlib only.

## Quickstart

```bash
# 1. Sign up at https://veto-ai.com to get an API key.
# 2. Auto-configure your MCP client:
veto init --api-key veto_test_xxxxxxxxxxxx

# 3. Verify the integration:
veto test
```

`veto init` detects which MCP clients you have installed (Claude Desktop, Cursor, etc.) and writes the Veto MCP server into their config. Restart the client and your agent now routes every payment through Veto.

## Commands

| Command | What it does |
|---|---|
| `veto init` | Auto-detect MCP clients on your machine and add Veto to each one's config |
| `veto status [agent_id]` | Show your agent's current reputation tier and recent decision history |
| `veto test [agent_id]` | Fire a synthetic test transaction to confirm the integration works |
| `veto list` | List all agents linked to your Veto account |
| `veto uninstall` | Remove Veto from MCP client configs (does not delete your account) |
| `veto mcp` | Run the Veto MCP server in foreground (for debugging) |

## What Veto evaluates on every authorize call

Each transaction passes through an 8-step pipeline before approval:

1. **Pre-checks** — agent suspended? amount sane?
2. **Policy enforcement** — per-tx limit, daily/monthly caps, merchant allowlist/blocklist
3. **Prompt injection detection** — 40 regex patterns over the action description
4. **Merchant fraud screening** — known-fraud database, typosquatting (SequenceMatcher), suspicious TLDs
5. **Intent verification** — does the action match the agent's stated purpose?
6. **Anomaly detection** — amount spike (>3× rolling avg), velocity, merchant diversity
7. **LLM final verdict** — Claude Sonnet reviews the case
8. **Reputation weighting** — agent trust tier modulates final risk score

Output: `approve` | `deny` | `escalate` (with risk score 0.0–1.0 and a human-readable reason).

## Configuration

The CLI stores state in `~/.veto/config.json` (mode `0o600`). It contains your API key and known agent IDs. No transaction data is stored locally.

By default the CLI talks to `https://veto-ai.com`. To point at a self-hosted Veto:

```bash
veto init --api-key XXX --base-url https://veto.your-company.com
```

## Links

- **Sign up:** https://veto-ai.com
- **Docs:** https://veto-ai.com/docs
- **Discord:** https://discord.gg/veto-ai
- **GitHub:** https://github.com/veto-protocol

## License

MIT. See [LICENSE](LICENSE).
