Mandate Check

Mandate Check is live. Before your agent acts, check its mandate. One call returns a pass or fail decision plus a hash-chained receipt. 1 credit per check call. 100 starter credits on signup.

Sign up with POST https://forgingstack-mandate-check.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. A signed-up human creates agent sub-keys with POST /v1/keys, capped from the primary balance and revocable, with unused credits returned on revoke.

It checks, in order, that the mandate agent matches, the principal matches, the mandate expiry is parseable and in the future, and the action is in the allowed actions. A failed decision still costs 1 credit, because the check was performed; an idempotency-key replay is free and returns the original receipt.

Limits, stated plainly: mandate fit only. Not legal advice, not a safety judgement, not a wisdom judgement. Do not use it to decide if an action is wise, legal, or safe, and do not invent a mandate to pass a check.

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 checks 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-mandate-check, version 0.2.1. Tools: check_mandate, get_credits, get_receipt. The service code itself is private; the public client and docs are at github.com/jdkabattles/forgingstack-mandate-check.

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-mandate-check.jkbattles.workers.dev/v1/check-mandate \
  -H "X-API-Key: $FORGINGSTACK_API_KEY" -H "Content-Type: application/json" \
  -d '{"agent_id": "proof-bot", "principal": "jonathan", "action": "read", "mandate": {"agent_id": "proof-bot", "principal": "jonathan", "allowed_actions": ["read"], "expires_at": "2027-01-01T00:00:00Z"}}'

{
  "receipt_id": 35,
  "decision": "pass",
  "reason": "action_within_mandate",
  "receipt_hash": "fbf5b56efdee83867b7519930f5b5acc12ce42daaffae17b7b93ad737a947bd9",
  "created_at": "2026-11-07T17:57:50Z"
}