AlphaOS verified operator reputation (0-1000) with rank, tier, XP, level, streak and on-chain quest proofGET /api/x402/reputation · x402 API by alphaos
AlphaOS verified operator reputation (0-1000) with rank, tier, XP, level, streak and on-chain quest proof.
What does this x402 API do?
AlphaOS verified operator reputation (0-1000) with rank, tier, XP, level, streak and on-chain quest proof. This is an x402-gated GET API resource from alphaos. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21. The listing records $0.01 USD-denominated per request on Base. No settled paid call has been verified.
- Published price
- $0.01 USD-denominated per request
- Networks
- Base
- Latest evidence
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21
- Resource ID
- de50c1e7605ac57c8740fb64
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://www.alphaos.site/api/x402/reputation", {
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
HEAD https://www.alphaos.site/ 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 $0.01 USD-denominated per request. Raw protocol requirements remain visible below for implementation and audit use.