https://x402-deployer.x402-deployer.workers.dev/jwt-decode
JWT decoder / JWT parser / JSON Web Token inspector / Bearer token debugger / OAuth ID-token reader / Auth0 + Cognito + Firebase token inspector. Base64URL-decodes header and payload, parses standard claims (iss, aud, sub, exp, iat, nbf, jti), reports algorithm, key id (kid), token type (typ), TTL, and clock-validity (is_expired / is_not_yet_valid / is_currently_valid_by_clock). Does NOT verify signatures — for inspection only, never trust output for auth decisions.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402-deployer.x402-deployer.workers.dev/jwt-decode", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"jwt"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
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.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://x402-deployer.x402-deployer.workers.dev/ 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.
EVIDENCE
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.