https://x402.swaphunt.dev/v1/sanity/is-this-a-breakoutGET /v1/sanity/is-this-a-breakout · x402 API by x402
Is a breakout from a given level real or a fakeout? Checks volume confirmation, time held above/below, and fakeout probability. Use to validate a breakout before chasing it. Requires the level to test.
What does this x402 API do?
https://x402.swaphunt.dev/v1/sanity/is-this-a-breakout. This is an x402-gated GET API resource from x402. TOLL·402 confirmed a protocol-valid HTTP 402 quote 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
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21
- Resource ID
- 0e5bfcf17c959b192f439590
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402.swaphunt.dev/v1/sanity/is-this-a-breakout", {
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.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
OPTIONS https://x402.swaphunt.dev/ returned 405.
- 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.