ProdVerdict v0.6: verify billing before your Cursor agent opens a PR

#saas #github #opensource #ai

AI agents ship fast. Tests pass. The PR looks fine. Then Stripe says active and Postgres says has_paid_access = false.

ProdVerdict v0.6 adds an agent-first workflow: diagnose credentials, run all contracts, get stable JSON back — for Cursor MCP or CLI.

Agent loop (new in v0.6)

npx prodverdict init --stack nextjs-stripe --mcp --cursor-rule
npx prodverdict doctor --format agent
npx prodverdict check all --format agent

--format agent returns schemaVersion: "1" JSON with summary and nextSteps — no LLM in evaluation.

Cursor MCP

Add @prodverdict/mcp to .cursor/mcp.json. Tools: doctor, check_all_contracts, check_access_contract, check_config_contract, check_migration_contract, validate_config, suggest_fix.

Prompts: setup_prodverdict, verify_before_pr.

Full guide: prodverdict.com/agents

Three contracts

Access — Stripe/Paddle vs Postgres billing drift
Config — env var references vs .env.example
Migration — unsafe Postgres DDL in agent-generated SQL

Try without API keys

git clone --depth=1 https://github.com/prodv-dev/prodverdict-sdk.git
cd prodverdict-sdk
npx prodverdict check access \
  --config examples/nextjs-stripe/prodverdict.yml \
  --fixtures \
  --fixtures-dir examples/nextjs-stripe/scenarios/fail-revenue-leak

CI enforcement

- uses: prodv-dev/prodverdict-action@v0.6.0
  with:
    config: ./prodverdict.yml
    contract: access
  env:
    STRIPE_SECRET_KEY: ${{ secrets.STRIPE_SECRET_KEY }}
    DATABASE_URL: ${{ secrets.DATABASE_URL }}