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.
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.
Validate one real agent-payment workflow.
Have a production payment flow beyond the free proof? KushBitx offers a one-time 49 USDC integration and validation pilot for one bounded workflow. We map your payment intent into SpendGuard, test fail-closed policy handling and duplicate-intent protection, and add unsigned Base transaction preflight when your workflow exposes one.
49 USDC one-time · no subscription
The 49 USDC fee covers integration and validation work. It does not authorize any x402 API charge, wallet signature, transfer, or recurring commitment. Per-call AgentProof services remain separately authorized.