https://api.hyperd.ai/api/budget/guardianGET /api/budget/guardian · x402 API by hyperd
Agent spend visibility: aggregates recent outbound USDC transfers from a wallet over a configurable window (1h/24h/7d/30d). Returns total spend, by-destination breakdown, projected-24h rate, and an optional under_cap flag if cap_usd is provided. Use to enforce a self-imposed budget before initiating the next paid x402 call.
What does this x402 API do?
https://api.hyperd.ai/api/budget/guardian. This is an x402-gated GET API resource from hyperd. The latest safe exact-route check returned HTTP 400 on 2026-07-21. No normalized USD price is recorded; the listing names Base. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Base
- Latest evidence
- The latest safe exact-route check returned HTTP 400 on 2026-07-21
- Resource ID
- 69c5a5993f511bb2f80a41ad
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://api.hyperd.ai/api/budget/guardian", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Exact route checked
non 402
- Origin reachable
HEAD https://api.hyperd.ai/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.