# SafeCommit

Protection for risky deploys. SafeCommit takes a change (a Vercel deployment,
a Supabase migration, or both), checkpoints production, applies it, watches
your health checks, and rolls back automatically if production breaks.

Humans: https://safecommit.vercel.app/ (accounts and dashboard). Docs: https://safecommit.vercel.app/docs

## Agents: buy one protected run over HTTP 402, no account

POST https://safecommit.vercel.app/api/agent/run
content-type: application/json

  {
    "kind": "vercel_deployment | supabase_migration | combined_release",
    "repository": "owner/repo",
    "target": "production | staging | preview",
    "summary": "one line describing the change",
    "payload": "the unified diff or migration SQL",
    "vercel_project_id": "for a real deploy, with deployment_id",
    "deployment_id": "the deployment to promote",
    "vercel_token": "your own Vercel token; the run acts as you",
    "database_url": "postgresql://..., for a real migration",
    "health_checks": [ { "path": "/", "expect_status": 200, "expect_body": "optional" } ],
    "max_price_cents": "optional guard against a price change"
  }

Price is computed from the change itself (risk based, from a $2 base; a
one-file production deploy is about $6), so the same body always gets the
same price. With no payment the call answers 402 with the exact price.
Pay, then send the identical body again with the payment header.

An empty POST returns sample terms for a one-file deploy, so you can read
the price before building a request.

## Rails

- x402: USDC on base-mainnet (eip155:8453), paid to 0x5f2dAbA9EA8B95d86195412A24F3Ab0168791696. Terms in the PAYMENT-REQUIRED header; retry the identical request with PAYMENT-SIGNATURE.
- MPP (Stripe machine payments): challenge in WWW-Authenticate; retry with Authorization: Payment.

## More agent-payable services by the same maker

https://the-wall-lime.vercel.app/agents