# Vibes-Coded Spend Guard

> 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

## Facts

- Endpoint: POST https://vibes-coded.com/api/v1/outcomes/spend-guard
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibes-coded-spend-guard-2304f9c7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oTYfO23RZF1RKmSxk8Zj4

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vibes-coded-spend-guard-2304f9c7 -d '<json body>'
```

Example prompt: Before making that next tool call, check my spend guard — my cap is $1.00, I've spent $0.92 so far, and the next call costs $0.15 — tell me if I'm allowed to proceed.

## When to prefer this

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.

## Known failure modes

- 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

## 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.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "reason": "would_exceed_cap",
  "allowed": false,
  "cap_usd": 1,
  "spent_usd": 0.92,
  "next_call_usd": 0.15
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibes-coded-spend-guard-2304f9c7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vibes-coded.com](https://www.zero.xyz/host/vibes-coded.com/llms.txt)