Agent Payment Budget Check
● Livemoneytools.dev
Ask "is this within my agent's budget?" before it signs an x402 payment — 0.005 USDC per check, no API key. Advisory: complements your wallet's own hard limits. Advisory pre-sign check (your wallet's own hard limits still apply; we cannot block a payment): 'would this payment exceed my cap?'. Pass the 402 PAYMENT-REQUIRED (header or body) or amountUsd, plus payer and optional sessionId/host. Returns allow|deny with reasons and remaining budget; reserve:true also logs it as pe
- Price
- $0.005
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 6 of 6 checks
Endpoint
$0.005 asked in its payment challenge on 17 Nov 2026
curl -i -X POST 'https://settle.moneytools.dev/v1/spend/check' \
-H 'Content-Type: application/json' \
-d '{"host":"api.example.com","payer":"0x000000000000000000000000000000000000dEaD","amountUsd":"0.25"}'Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/settle.moneytools.dev
Recent checks
- Median response
- 117 ms
- Last checked
- 17 Nov, 21:21 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 6 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Nov, 21:21 UTC | Live | 402 | 612ms |
| 16 Nov, 09:22 UTC | Live | 402 | 66ms |
| 14 Nov, 21:23 UTC | Live | 402 | 368ms |
| 13 Nov, 09:23 UTC | Live | 402 | 53ms |
| 11 Nov, 21:23 UTC | Live | 402 | 151ms |
| 10 Nov, 06:26 UTC | Live | 402 | 82ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 17 Nov, 21:21 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does MoneyTools Settle advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.