Keep the spending rules outside the agent.
Start from a ready policy pack, test a proposed payment for free, then save the rules as a protected server-side policy with separate administrator and agent keys.
This tool stays free.
SpendGuard never receives a wallet key and never moves funds. Your signer or payment service must enforce every returned decision.
No wallet or payment is requested.
Separate administrator control from agent use.
Create a 30-day policy from the rules above. Only the admin key can read or change the policy; the agent key can request decisions but cannot change limits.
The agent sends payment facts, not the budget or allowlist.
A request ID cannot be reused with different payment data.
Copy or download each verifiable fingerprint locally.
POST /api/spendguard/evaluate Policy is supplied in the request. Advisory only.
POST /api/spendguard/decisions Authorization: Bearer <agentKey> Returns APPROVE, BLOCK or HUMAN_APPROVAL.
Support for an existing SpendGuard workflow.
Describe the workflow and the help you need. Any additional work requires an agreed scope and price; this form does not create a paid engagement.
Per-call KushBitx checks remain separately priced and authorized. An enquiry does not authorize an API charge, wallet signature, transfer, or recurring commitment.