ProdVerdict for AI agents

Verify billing, env vars, and migrations before your agent opens a PR. Deterministic checks — no LLM in the evaluation path. Billing secrets stay on your machine.

1. One-command setup

Scaffold prodverdict.yml, Cursor MCP, and an agent rule.

npx prodverdict init --stack nextjs-stripe --mcp --cursor-rule

2. Agent verify loop

Stable JSON with summary and next steps (schemaVersion: "1").

npx prodverdict doctor --format agent

npx prodverdict check all --format agent

3. Local MCP (billing secrets stay on your machine)

Tools: doctor, check_all_contracts, check_*_contract, validate_config, suggest_fix. Prompts: setup_prodverdict, verify_before_pr.

{
  "mcpServers": {
    "prodverdict": {
      "command": "npx",
      "args": ["-y", "@prodverdict/mcp"],
      "env": {
        "DATABASE_URL": "postgresql://readonly:...@host/db",
        "STRIPE_SECRET_KEY": "rk_live_..."
      }
    }
  }
}

Or paste the MCP block from your dashboard project setup.

4. Remote MCP (v0.7 — config & migration via GitHub)

No Stripe/DB on cloud. Pro: check_config_contract, check_migration_contract, get_recent_runs. Free: validate_config.

{
  "mcpServers": {
    "prodverdict-remote": {
      "url": "https://prodverdict.com/api/mcp",
      "headers": {
        "Authorization": "Bearer pv_...",
        "X-Prodverdict-Project-Id": "your-project-uuid"
      }
    }
  }
}

5. Fixture demo (no API keys)

npx prodverdict check access --fixtures --config examples/nextjs-stripe/prodverdict.yml --fixtures-dir examples/nextjs-stripe/scenarios/fail-revenue-leak

Create a project SDK on GitHub