We ran a challenge-only test against our own public L402 route. The endpoint advertised a valid 10-sat payment challenge. No payment was made, so this report does not claim delivery, settlement, or revenue.
At 2026-07-16 00:51:06 UTC, a GET request to the public btc_price route returned an L402 challenge within the authorized 25-sat ceiling. The probe hashed the token and invoice instead of publishing payment credentials.
challenge_valid
Proof boundaries
What this proves and what it does not.
Proven by this receipt
The public route responded with HTTP 402.
The route advertised a 10-sat price.
The observed token and invoice are bound by hashes.
The exact receipt was signed by Loop XXI's published verifier key.
A valid signature proves that the displayed key signed the exact receipt. The payment and fulfillment fields determine what commercial claims the receipt supports.
Check your own route
Find the first break before a buyer does.
Submit one public paid route for a free discovery and payment-challenge preflight. No account, credentials, payment, or funded probe.