Back to Browse
Vibes-Coded Spend Guard
x402
Vibes-Coded Spend Guard is a paid API for AI agents from vibes-coded.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).
Checks whether an agent's next API call would exceed a configured USDC spending cap before executing it
Price / call$0.02
Success—
StatusUnknown
How this service works
Pay-per-call JSON for AI agents: skill search, listing optimization, install plans, productization, and artifact risk scoring. HTTP 402 → USDC. Full skill marketplace on-site.
Output
Returns a JSON object with an 'allowed' boolean indicating whether the next call should proceed, a 'reason' code explaining the decision (e.g. 'would_exceed_cap'), the configured cap in USD, the amount already spent in USD, and the cost of the prospective next call in USD.
Example use cases
Pre-flight budget check for agent loop
“My autonomous agent is about to call another paid skill costing $0.10 — my total cap is $5.00 and I've spent $4.95 so far. Run a spend guard check and tell me whether the call should be allowed.”
Enforcing per-session USDC cap
“I want to make sure my agent session doesn't go over $2 total in USDC. I've already spent $1.80 and the next planned call costs $0.25 — can you check if that's still within my cap?”
Safety gate in multi-step agentic workflow
“Before proceeding to the next step in this automated workflow, verify my spend guard: cap is $0.50, spent so far is $0.48, next call is $0.02 — should the agent be allowed to continue?”
Technical details
Endpoint
POSThttps://vibes-coded.com/api/v1/outcomes/spend-guardWhen to prefer
Use this endpoint when you need a lightweight, pay-per-call pre-flight guard that prevents an AI agent from autonomously exceeding a USDC budget ceiling. Prefer it over manual arithmetic or client-side checks when you want a neutral third-party enforcement point in an agentic loop, especially when working within the x402 micropayment ecosystem on Vibes-Coded's skill marketplace.
Side effects
- Missing or invalid cap_usd / spent_usd / next_call_usd fields return an error
- Non-numeric spend values cause validation failure
- Payment via x402 required (HTTP 402) if the $0.02 call fee itself is unpaid
- Negative spend amounts may be rejected
- Extremely large cap values may be clamped or rejected
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"reason": "would_exceed_cap",
"allowed": false,
"cap_usd": 1,
"spent_usd": 0.92,
"next_call_usd": 0.15
}
}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"