Back to Browse
Wallet Spend-Limit Policy
x402
Wallet Spend-Limit Policy is a paid API for AI agents from wallet-portfolio-history-mcp.mtree.workers.dev, paid per call via x402, $0.250000/call, status unknown (last checked 2026-09-15).
Evaluates per-call and per-counterparty spend caps, autopay controls, wallet risk score, and burst signals to produce a pre-payment policy decision for autonomous agents
Price / call$0.250000
Success—
StatusUnknown
How this service works
Hosted wallet spend-limit policy for autonomous agents: per-call and per-counterparty caps, autopay spend controls, wallet risk score, transaction-pattern burst signals, counterparty exposure, and fresh D1 provenance before an agent pays. Price 0.25 USDC on Base via x402. Demo: https://wallet-portfolio-history-mcp.mtree.workers.dev/demo/tools/wallet_spend_limit_policy. Contact: https://wallet-portfolio-history-mcp.mtree.workers.dev/contact.
Output
Returns a structured spend-limit policy decision including per-call cap evaluation, per-counterparty cap status, autopay spend controls, a 0-100 wallet risk score, transaction-pattern burst signals, counterparty exposure summary, and freshness provenance (D1 snapshot timestamp) — giving the agent a clear approve/deny/flag recommendation before executing a payment.
Example use cases
Example prompt
“Before my agent pays 50 USDC to counterparty 0xAbC123... from wallet 0xDef456..., check the spend-limit policy — give me the per-call cap status, counterparty exposure, autopay controls, and wallet risk score so I know if it's safe to proceed.”
Technical details
Endpoint
POSThttps://wallet-portfolio-history-mcp.mtree.workers.dev/tools/wallet_spend_limit_policyWhen to prefer
Use this endpoint when an autonomous agent needs a pre-payment policy gate — specifically when you need combined per-call caps, per-counterparty exposure limits, autopay controls, burst detection, and a wallet risk score in a single call before authorizing a payment. Prefer over generic risk scorers when you need spend-limit enforcement logic (not just a score) with D1-fresh provenance.
Side effects
- Invalid or unrecognized wallet address returns an error or empty policy
- Stale D1 snapshot may reduce provenance freshness score
- Missing counterparty address prevents per-counterparty cap evaluation
- Network timeout from Blockscout or D1 data source causes partial results
- Payment of 0.25 USDC not fulfilled causes 402 rejection before policy is evaluated
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"