Overview

Parse absolute URL components and query parameters into machine-readable JSON. Low-price deterministic x402 utility bench with CSV, JSON Schema, timestamp, JWT, URL, hash, and text tools at the current $0.001 CDP-compatible floor. Start buyer evaluation at https://x402-utils.558686.xyz/x402/buyer-use-cases or machine JSON https://x402-utils.558686.xyz/x402/buyer-use-cases.json; checkout contract JSON is https://x402-utils.558686.xyz/x402/checkout.json. Route payment activation JSON is https://x402-utils.558686.xyz/x402/route/url-parse/payment-activation.json. Browsers can inspect the quote, but payment requires a buyer-owned runtime that signs and retries the same request with X-PAYMENT. Buyers can download the route-specific first-payment client at https://x402-utils.558686.xyz/x402/route/url-parse/first-payment-client.mjs, run node first-payment-client.mjs for quote-only checks, then opt into a buyer-owned x402 payment with PAY_REAL_X402=1. Copy-ready first paid request: curl -fsSL https://x402-utils.558686.xyz/x402/route/url-parse/first-payment-client.mjs -o first-payment-client.mjs && npm install @x402/fetch @x402/core @x402/evm @x402/svm viem @solana/kit @scure/base && PAY_REAL_X402=1 EVM_PRIVATE_KEY=$EVM_PRIVATE_KEY node first-payment-client.mjs. Generic clients can also discover it from the live 402 response headers: the standard Payment-Required header includes firstPaymentClient, paymentClientUrl, and sameRequestRetryRequired pointers; X-First-Payment-Client, X-Download-Install-Then-Pay-Command, and Link rel=payment-client mirror the same handoff.

Protocol x402 (POST)
Price
Payment Asset
Payment Network
Category developer-tool
Provider x402-utility-tools
Source self-registered
Indexed 2026-07-02 10:03:48

Health

Status healthy
Latency (p50) 873ms
Uptime (30d) 100.0%
Reliability Score 90/100
Last Checked 2026-08-19 22:32:16
Last Healthy 2026-08-19 22:32:16
Consecutive Failures 0

x402 Payment Validation

Payment Requirements Valid
Asset Verified Known USDC
Facilitator

Recent Health Checks

Time Status HTTP Latency Error
2026-08-19 22:32:16 healthy 402 873ms
2026-08-19 17:59:51 healthy 402 743ms
2026-08-19 09:52:33 healthy 402 859ms
2026-08-19 03:04:16 healthy 402 1137ms
2026-08-18 21:19:09 healthy 402 907ms
2026-08-18 17:40:19 healthy 402 732ms
2026-08-18 11:08:24 healthy 402 2711ms
2026-08-18 05:11:23 healthy 402 1176ms
2026-08-18 01:02:11 healthy 402 841ms
2026-08-17 19:30:39 healthy 402 719ms
2026-08-17 08:12:18 healthy 402 896ms
2026-08-17 06:29:30 healthy 402 827ms