Quorum

Quorum is live. Before an agent acts alone, get the quorum. One proposal names the action, the approvers, how many approvals it needs, and when it expires. Each approver gets a one-time link by email; when approvals reach the number required, the proposal is approved and a hash-chained receipt is issued.

Sign up with POST https://forgingstack-quorum.jkbattles.workers.dev/v1/signup and an email address. The API key is shown once, and it does not work until the verification link in the email is clicked. 100 starter credits on signup; creating a proposal costs 1 credit, approvals are free.

A proposal that runs out of time with too few approvals expires. A rejected proposal stays rejected. An approval link works once — reusing it is refused.

Limits, stated plainly: approval fit only. Quorum proves the right people said yes; it does not prove the action is wise, legal, or safe.

Before you pay, two honest frictions: the verification email can land in Junk — it did for an Outlook mailbox in our own testing, so check there first. And credits land within the hour after payment, not instantly: the payment is stored first and credited once the hourly check verifies it against Stripe.

Billing is live: 1,000 credits for $10. Sign up, click the email verification link, then buy a credit pack with POST /v1/billing/checkout using your primary key — it returns a Stripe payment link. Use the same email at checkout that you signed up with.

Install the MCP client from PyPI: forgingstack-quorum, version 0.1.0. Tools: create_proposal, get_proposal, get_credits, get_receipt. The service code itself is private; the public client and docs are at github.com/jdkabattles/forgingstack-quorum.

The same rule holds on every page here: the work leaves a receipt you can verify, the price is $10 for 1,000 credits with 100 free to start, and the limits are stated on the page. What cannot be checked is not claimed.

curl -s -X POST https://forgingstack-quorum.jkbattles.workers.dev/v1/proposals \
  -H "X-API-Key: $FORGINGSTACK_API_KEY" -H "Content-Type: application/json" \
  -d '{"action": "deploy to production", "approvers": ["[email protected]", "[email protected]"], "required_approvals": 2, "expires_at": "2027-01-01T00:00:00Z"}'

{
  "receipt_id": 1,
  "decision": "approved",
  "reason": "quorum_reached",
  "receipt_hash": "cee98e71a28ae661e5d11290847ab4cf8d9bb95717222e2e96f8ea74df3fed97",
  "created_at": "2026-11-05T23:00:31Z"
}